AS2 Troubleshooting

Could not listen on port XXXX - Address in use: JVM_BIND

(Generated when an attempt is made to start the Local Listener.)

Port XXXX defined on the listener's HTTP panel is already being used by another application.

Use the "netstat -an" command (if available) to verify that the port is in use.  

Stop the listener, if it is running. Define a different port on the HTTP panel and restart the listener.

Result: Error - Method GET is not implemented by this server

(Generated by the Local Listener receiving incoming messages)

A remote user is attempting to access your Local Listener using a web browser by entering your URL in the form: 

http://your-host-address:your-port/your-resource-path/

The VersaLex Listener is only capable of processing HTTP POST requests, but messages from web browsers are sent as HTTP GET requests. 

If the message is coming from a bona fide trading partner, ask them to send you messages using  POST requests instead of GET requests.

If the message is from an unknown/unwanted source, modify your firewall settings to reject messages from the incoming IP address or change the setting for the Unknown Partner Message Action in the Local Listener's Advanced tab to either Ignore or Reject.

Result: Connection refused: connect

Remote server is currently not running or is not listening on the specified port.

Contact your trading partner regarding the availability of the server and verify the configured host and port settings are correct.

Result: Operation timed out: connect

Remote server is running but is not able to receive messages from you.

Verify firewall settings on the sending and receiving ends are properly configured.

Result: Timeout waiting for response

The action is unable to fully complete (i.e., complete transfer to remote host, decryption and/or signature verification) within the specified ConnectionTimeout period.

Increase the default ConnectionTimeout value on the Host/Advanced panel or increase the ConnectionTimeout value for the individual Action.

Result: Warning - Undefined AS2-To/AS2-From Relationship

(Generated by the Local Listener receiving incoming messages)

The incoming AS2-To and AS2-From header values do not match exactly with local AS2-From and AS2-To settings or the settings have not yet been defined.

Verify that there is an entry for the designated AS2-From / AS2-To setting.

Verify your AS2-To header value matches your trading partner's AS2-From header value and vice versa. 

These values are case-sensitive and there must be only one instance of the pair defined in your installation.

Result: Warning - MDN processing warnings occurred at the remote host. See MDN for further details.

(Generated when sending a message to the remote host.)

A warning occurred at the remote host. The message was still correctly processed. Commonly reported warnings are Undefined AS2-To / AS2-From Relationship and Duplicate file received.

View the associated MDN to diagnose the cause of the warning and perform any corrective action as necessary.

Result: Error - MDN processing errors occurred at the remote host: authentication failed - see MDN for further details

(Generated when sending a message to the remote host.)

The remote host was unable to verify the signature of your signed message.

Verify that you have successfully sent your signing certificate to your trading partner and that it was properly installed at the remote host.

Result: Exception - Certificate chain not trusted! 

(Generated when receiving a message from a remote host.)

Some of the certificates listed in the signature of the received message are missing in VersaLex's store of trusted certificates.

Verify that all CA certificates used by your trading partner's signing certificate have been received and installed in VersaLex.

Result: Exception - The signature could not be verified!

(Generated when receiving a message from a remote host.)

The Local Listener was unable to verify the signature of a remote host's signed message.

Verify that you have successfully received and installed your trading partner's signing certificate.

Result: Exception - The trading partner's encryption certificate could not be found!

(Generated when attempting to send an encrypted message to a remote host.)

VersaLex was unable to find the Trading Partner's Encryption Certificate defined on the Mailbox’s Certificate Panel.

Verify the file defined on the Mailbox’s Certificate panel exists and has not been accidentally deleted.   Click Browse to choose a new encryption certificate.

Result: Error - MDN processing errors occurred at the remote host: decryption failed - see MDN for further details

(Generated when sending a message to the remote host.)

The remote host was unable to decrypt your encrypted message.

Verify that you have successfully installed your trading partner's encryption certificate and have properly selected that certificate on the Mailbox’s Certificate panel.

Verify the remote host is able to decrypt messages according to the Encryption Method specified on the Mailbox’s AS2 panel.

Result: Exception - The message could not be decrypted!  

(Generated when receiving a message from a remote host.)

The Local Listener was unable to decrypt a remote host's encrypted message.

Verify that you have successfully received and installed your trading partner's encryption certificate.

WARNING: Source file is zero-length. 

(Generated when sending a message to the remote host.)

An attempt was made to send a file with no content. The file will still be sent, but there may be unexpected results on the receiving end.

Verify that the intent is to send files of zero-length and ignore any error messages generated due to this condition.