on 01-11-2008 10:02 AM
Has anyone come across a problem with Partner Identification/ Password when using Seeburger OFTP_TCP adapter ? Having used the same values as a previous example which worked I am experiencing an error when the message is passed to the JCA Adapter - does anyone have any tips & tricks to determine the root cause ?
Turns out the receiver password supplied was incorrect.....
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tony,
can you specify the error message you get?
Regards
Dominic
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It looks like it may be a Header Mapping issue as the Sender Party is mapped as part of the Comm. Channel (as prescribed by Seeburger Adapter setup)
/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/SEEBURGER/OFTP_TCP##com.seeburger.oftp.error.DtOftpException.logAndThrowInternalException()#J2EE_GUEST#0####b8ae95d0c8fe11dcb6cb00145e67633b#SAPEngine_Application_Thread[impl:3]_18##0#0#Error#1#com.seeburger.oftp.error.DtOftpException#Plain###LOCATION [OFTP-TCP, SESSION_12010157252001, 5ea9c43d45df30bca7f7a2cba39fdc00-b813b560c8fe11dca9dc00145e67633b] >> ERROR TYPE [, COMMUNICATION_ERROR, not retryable, not fatal]] >> DESCRIPTION [Invalid partner identification: Invalid partner password. Session is aborted. >> null] [SESSION_12010157252001, initator: 5013546181572 (ID: 5013546181572), responder: INS LTD (ID: INS LTD), channel: CC_ASN_toSOM_OFTP]#
However, this has previously worked - have done all of the usual Cache refreshes etc....
Any thoughts?
Cheers
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.