Error during protcol negotiation with Axway TradeSync

I'm trying to establish a new connection with Axway via their TradeSync platform. I keep getting this message.

> Feb 27, 2019 10:11:34 AM] [Session 20190227101133-394] java.lang.RuntimeException: The system is unable to parse the inbound OFTP2 command "ESID" (The received OFTP2 protocol command data is to short). This is not a problem of your mendelson OFTP2 system. It is a protocol violation performed by your partners OFTP2 system. It looks as if your partner is using a OFTP 1.x system or falls back to the OFTP1 protocol in an error case. If this problem happens during the connection attempt please check if you have transmitted the right connection password. Please also check your secure authentication challenge settings. Please also contact your partner to clarify this issue. (Hexdump: 10 00 00 07 46 30 34)

When I crank up logging, I see this detail on the final message Mendelson sends to Axway before their bad ESID response:

> o-----------------------------------------------------------------------------------------
> | SSID Start Session [Outbound]
> o-----------------------------------------------------------------------------------------
> | 0 | X(1) | SSIDCMD | SSID Command | 'X' | [58]
> | 1 | 9(1) | SSIDLEV | Protocol Release Level | '5' | [35]
> | 2 | X(25) | SSIDCODE | Initiators Identification Code | 'SCSI ' | [53 43 53 49 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20]
> | 27 | X(8) | SSIDPSWD | Initiators Password | 'AXCLD ' | [41 58 43 4c 44 20 20 20]
> | 35 | 9(5) | SSIDSDEB | Data Exchange Buffer Size | '02048' | [30 32 30 34 38]
> | 40 | X(1) | SSIDSR | Send/Receive Capabilities | 'B' | [42]
> | 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-----------------------------------------------------------------------------------------

I have tried with and without secure OFTP2 session authentication, and I'm sure the password is correct.

Any ideas on what else to try? I of course have asked Axway to look into it further, but I'm hoping to get some other ideas of things to try rather than just waiting for them.

Forum
OFTP2

Comments

Profile picture for user service
Permalink

jllawler,

this is a known problem in the product you mentioned. Whenever a problem in the negotiation phase occurs the product switches to OFTP1 which is incompatible to OFTP2. It is possible to see what happens if you analyse the hex data that could be found in the mendelson OFTP2 log. You need the OFTP1 RFC to see what happened. Please understand the the mendelson OFTP2 does not support OFTP1.

Please refer to http://mendelson.de/node/3197
for further information

Regards

Permalink

Thanks. I eventually worked around this with Axway. I don't remember exactly what the solution was, but it may've involved moving to a newer platform they have, which they refer to as commhub.