AS2 Error Warnings and Prompts
EFT provides error warnings and prompts when you are configuring the AS2 module and when you are sending/receiving files using AS2.
AS2 Configuration Errors
EFT presents a prompt and disallows changes to AS2 configuration in the following instances:
-
Settings are enabled that require a partner AS2 certificate and no certificate has been defined for that partner
-
Settings are enabled that require EFT’s AS2 certificate and no certificate has been defined for EFT
-
Settings are enabled that require the partner’s or the Server’s identifier and no identifier has been defined for the partner or EFT
-
The chosen certificate is set to expire in 30 days or fewer
-
A certificate being imported is a combined certificate
-
You open the AS2 Send File dialog box and click OK or Apply without specifying a partner profile.
AS2 Transfer Errors
EFT provides the following transfer error messages. When you receive one of these errors, you should examine your AS2 configuration and other Site/User settings. Certain messages are simply an indication that the configuration is working as designed. For example, if your AS2 outbound configuration has a filter mask to ban files with a .zip extension or if the Site's configuration bans files of this type on the Server, you will receive a banned file message when a user attempts to send files of this type.
Error |
Possible Cause/ Solution |
---|---|
A network error occurred |
Verify AS2 server address and port; ensure there is a connection between the two servers and nothing is blocking the connection; require SSL certificates from connected clients might be enabled; SSL negotiation failed; retry transfer |
Error decoding certificate |
AS2 module cannot decode EFT's or partner's certificate. Make sure the certificate is not corrupt or is of an unsupported format. Also check that the certificate is a single certificate and not multiple certificates inside of a certificate. |
The receipt was unsigned and a signed receipt was expected |
Incorrect certificate used for EFT or partner certificate |
Incorrect AS2-From field |
Incorrect "Your AS2 identifier" |
Incorrect AS2-To field |
Incorrect "Partner AS2 identifier" |
RSA Error: Inadequate amount of padding in encrypted message |
AS2 module cannot verify signature of signed incoming message; possible problem with identifiers; sender might be using incorrect identifier; AS2 MDN cannot be verified |
Timeout occurred while sending MDN |
Firewall blocking receipt send (MDN blocked) |
File already exists, Message with duplicate ID and different payload was received. |
(Tried to overwrite existing file and corresponding policy is set to Reject.) AS2 configuration does not allow overwriting files of same name; change AS2 configuration to Accept these files or move/rename files after they are received. |
Quota exceeded |
File is too large. User configuration does not accept files of this size; Specifying Disk Quota or compress/split file. |
File is banned |
(Uploaded file meets Site’s "Ban" mask) Site configuration does not accept files of this type/name. Banning Unwanted File Types or let your partner know that files of that type cannot be uploaded to EFT. |
(Tried to use "plain" AS2 without encryption.) AS2 configuration must be set to use encrypted HTTP or HTTPS. Or use redirection; refer to Redirecting HTTP to HTTPS for details of redirection. |
|
Unable to decrypt message, RSA Error |
Inadequate amount of padding in encrypted message. AS2 module cannot decrypt encrypted incoming message. |
HTTP error: 400 Bad Request |
Receiver/ sender has incorrect or missing certificate; Connection problem of some kind |
HTTP error: 401 Unauthorized |
Authentication failed for username/ password; IP address is blocked |
HTTP error: 403 Forbidden |
Incorrect folder location, Mailbox path; do not have permission to remote folder/ path; AS2 is not enabled/ supported on receiving side |