mendelson opensource OFTP2

Hi, I am trying to establish a communication link with partner and get following error mendelson-opensource-AS4-170824162201-3802877@3802878: [Inbound data processing] A problem occured during processing of inbound AS4 data (Module Processing ... [More] , FailedAuthentication: EBMS:0101 [The certificate with the issuer "C=US, O=Entrust, Inc., OU=See www.entrust.net/legal-terms, OU=(c) 2012 Entrust, Inc. - for authorized use only, CN=Entrust Certification Authority - L1K" and the serial "1356075869 (dec), 50d4135d (hex)" is requested but does not exist in the system ([Security verification], signature verification)]) My partners certificate in Sign/Crypt store is imported as Issuer: C=US,O=Entrust\, Inc.,OU=See www.entrust.net/legal-terms,OU=(c) 2012 Entrust\, Inc. - for authorized use only,CN=Entrust Certification Authority - L1K Serial (dec): 1356075869 Serial (hex): 50D4135D Mendelson opensource AS4 1.0 b21. What am I doing wrong? Forum:  AS4 [Less]

In reply to Inbound Virtual Filename Hello, please contact the mendelson support as this is the forum for the community edition of the mendelson software. Regards Log in or register to post comments

Hi Support Team, i need to move all inbound OFTP2 data from a partner into a special sub directory. The virtual filename that the partner uses changes with every transmission. Can i set some kind of placeholder under "Inbound virtual filenames" in ... [More] the partner profile so that every inbound data will be stored in the defined sub-folder no matter which virtual filename the partner is sending ? I have tried to use a * as virtual filename but that does not work regards Forum:  OFTP2 [Less]

In reply to Local side emergency close down Also when partner is trying to send me a file they receive an error: Session aborted by remote entity... I have tried all different settings, but I do not understand why this error is happening. Log in or register to post comments

Hello, I am testing OFTP2 1.0 build 31 When I try exchanging documents with partner (no SSL, port 3305, only SSIDPSWD) I receive an error Local side emergency close down - internal code 5. If I test connection I see everything OK (Running OFTP ... [More] service found and connection established), but when I try to send a test file there is this error: [ :41 AM] [Connection test to .com/xxx.xxx.xxx.xxx:3305] Start connection check to .com/xxx.xxx.xxx.xxx:3305 using PLAIN connection... [ :41 AM] [Connection test to .com/xxx.xxx.xxx.xxx:3305] Setting timeout to 2000ms [ :41 AM] [Connection test to .com/xxx.xxx.xxx.xxx:3305] Connection to .com/xxx.xxx.xxx.xxx:3305 established successfully [ :41 AM] [Connection test to .com/xxx.xxx.xxx.xxx:3305] Check for running OFTP service... [ :41 AM] [Connection test to .com/xxx.xxx.xxx.xxx:3305] Start connection check to .com/xxx.xxx.xxx.xxx:3305 using PLAIN connection... [ :41 AM] [Connection test to .com/xxx.xxx.xxx.xxx:3305] Setting timeout to 2000ms [ :41 AM] [Connection test to .com/xxx.xxx.xxx.xxx:3305] Connection to .com/xxx.xxx.xxx.xxx:3305 established successfully [ :41 AM] [Connection test to .com/xxx.xxx.xxx.xxx:3305] Check for running OFTP service... [ :42 AM] [Connection test to .com/xxx.xxx.xxx.xxx:3305] Remote service identification: "IODETTE FTP READY" [ :42 AM] [Connection test to .com/xxx.xxx.xxx.xxx:3305] Success: Running OFTP service found at .com/xxx.xxx.xxx.xxx:3305 [ :33 AM] [Transmission 8043] [Directory poll manager] The file "c:\oftp2\messages\XXX\outbox\TEST.txt" has been scheduled for preprocessing. Final receiver: "XXX", virtual filename: "NOT-CATEGORIZED" [ :36 AM] [Transmission 8043] Starting data preprocessing [c:\oftp2\messages\XXX\outbox\pending\NOT-CATEGORIZED201708211040330018], size: 4 bytes [ :36 AM] [Transmission 8043] The user defined transmission id is set to "--" [ :36 AM] [Transmission 8043] Record format of the transmission: U [ :36 AM] [Transmission 8043] Signing transfer data [c:\oftp2\messages\XXX\outbox\pending\NOT-CATEGORIZED201708211040330018] [ :36 AM] [Transmission 8043] The transfer data has been signed using SHA1 by the key "www.XXX.net" [ :36 AM] [Transmission 8043] Compressing transfer data [c:\oftp2\messages\XXX\outbox\pending\NOT-CATEGORIZED201708211040330018] [ :36 AM] [Transmission 8043] Compressing transfer data finished. Old size: 568 bytes, new size: 584 bytes, ratio: 1.0 [ :36 AM] [Transmission 8043] Moved preprocessed data to [c:\oftp2\messages\XXX\outbox\pending\NOT-CATEGORIZED201708211040330018] [ :36 AM] [Transmission 8043] Data preprocessing finished successfully, waiting for outbound transmission [ :47 AM] Initializing outgoing connection to XXX [.com/xxx.xxx.xxx.xxx:3305] [ :48 AM] [Session 15033055135604] Connection established [.com/xxx.xxx.xxx.xxx:3305] ............................ ------------------------------------------------------------------------------ | SSID Start Session o------------------------------------------------------------------------------- | 0 | X(1) | SSIDCMD | SSID Command | 'X' | [58] | 1 | 9(1) | SSIDLEV | Protocol Release Level | '5' | | 2 | X(25) | SSIDCODE | Initiators Identification Code | 'XXX ' | | 27 | X(8) | SSIDPSWD | Initiators Password | 'XXX ' | | 35 | 9(5) | SSIDSDEB | Data Exchange Buffer Size | '02048' | | 40 | X(1) | SSIDSR | Send/Receive Capabilities | 'B' | | 41 | X(1) | SSIDCMPR | Buffer Compression Indicator | 'N' | [4e] | 42 | X(1) | SSIDREST | Restart Indicator | 'N' | [4e] | 43 | X(1) | SSIDSPEC | Special Logic Indicator | 'N' | [4e] | 44 | 9(3) | SSIDCRED | Credit | '099' | [30 39 39] | 47 | X(1) | SSIDAUTH | Secure Authentication | 'N' | [4e] | 48 | X(4) | SSIDRSV1 | Reserved | ' ' | [20 20 20 20] | 52 | X(8) | SSIDUSER | User Data | ' ' | [20 20 20 20 20 20 20 20] | 60 | X(1) | SSIDCR | Carriage Return | ' ' | [0d] o------------------------------------------------------------------------------- [ :48 AM] [Session 15033055135604] Received command ESID [ :48 AM] [Session 15033055135604] Received command o---------------------------------------------- | ESID End Session o---------------------------------------------- | 0 | X(1) | ESIDCMD | ESID Command | 'F' | [46] | 1 | 9(2) | ESIDREAS | Reason Code | '05' | [30 35] | 3 | 9(3) | ESIDREASL | Reason Text Length | '000' | [30 30 30] | 6 | T(n) | ESIDREAST | Reason Text | '' | [] | 6 | X(1) | ESIDCR | Carriage Return | ' ' | [0d] o---------------------------------------------- [ :48 AM] [Session 15033055135604] Statemachine "Session Connection State Machine" received signal "ESID", state is "I_WF_SSID" [ :48 AM] [Session 15033055135604] Statemachine "Error and Abort State Machine" received signal "F_ABORT_IND", state is "I_WF_SSID" [ :48 AM] [Session 15033055135604] Session terminated [OFTP2 - XXX] ("Local side emergency close down", internal code 5) [ :48 AM] [Session 15033055135604] Connection closed [OFTP2 - XXX, .com/xxx.xxx.xxx.xxx:3305]. Established for 0.7s, 96 bytes transfered Thank you for assistance. Kind regards M. Forum:  OFTP2 [Less]

In reply to bRahms, Any possibiity to check this in detail, not via the forum, to verify what's going wrong? Log in or register to post comments

In reply to Setting up new AS2 bRahms, the MDN sends back the state of your partners processing. In your case the configuration of your partners system does not seem to match yours regarding the AS2 paramters - it also looks as if you are not even configured in your partners system? Regards Log in or register to post comments

Hi all, I'm new into the AS2 world and would appreciate some help in setting up a new AS2 connection. We already use the Mendelson AS2 software for a few years and have already a few connections runnning (set up by an ex-colleague) - but now we have ... [More] to set up a new connection, which i fail to set up correctly :-( What I did: * created the partner and added its sign/crypt sign to the keystore * set up everything in mendelson, following the set up procedure * created the necessary folders and requested a testfile from the partner. We received the message correctly and send back a sync MDN: [Jun 22, 2017 11:21:18 AM] xxx: Incoming transmission is a AS2 message, raw message size: 3.55 KB. [Jun 22, 2017 11:21:18 AM] xxx: AS2 message is encrypted. [Jun 22, 2017 11:21:18 AM] xxx: The data has been decrypted using the key "ourkey". [Jun 22, 2017 11:21:18 AM] xxx: AS2 message is signed. [Jun 22, 2017 11:21:18 AM] xxx: The sender used the algorithm SHA1 to sign the message. [Jun 22, 2017 11:21:18 AM] xxx: Using certificate "parntersname.nl" to verify signature. [Jun 22, 2017 11:21:18 AM] xxx: Digital signature verified successful. [Jun 22, 2017 11:21:18 AM] xxx: Found 1 payload attachments in the message. [Jun 22, 2017 11:21:18 AM] mendelson_opensource_AS2-14981...: Outgoing MDN has been signed with the algorithm "SHA1". [Jun 22, 2017 11:21:18 AM] mendelson_opensource_AS2-14981...: MDN created, state set to [processed]. [Jun 22, 2017 11:21:18 AM] mendelson_opensource_AS2-14981...: Synchronous MDN sent as answer to message xxx. [Jun 22, 2017 11:21:18 AM] xxx: AS2 communication successful, payload 1 has been moved to "E:\AS2_MESSAGES\inbox\testmessagename". We thought everything was OK, but the partner gives me back this info: Details of the message and exception are as follows: AS2-From:"..." AS2-To:"..." MessageID:"" MessageType: "MDN" Exception:"Configuration error. The message signature doesn't match the signature configured for this party. Contact the sending partner and verify the certificate used. AS2-From:"..." AS2-To:"..." MessageID:""" What am I doing wrong? Thanks in advance for any help! Kind regards, BS. Forum:  AS2 [Less]

In reply to SSL handshake failed Log file part 2.2: File attachments:  20170622_085239_oftp2_ssl_debug_handshake_failed_part2_2.txt Log in or register to post comments

In reply to SSL handshake failed Log file part 2.1: File attachments:  20170622_085239_oftp2_ssl_debug_handshake_failed_part2_1.txt Log in or register to post comments