Status Codes: 600 - 699
This section describes the status codes, which are specific to BusinessConnect Container Edition - EDI Protocol powered by Instream.
These status codes might display in the following areas:
-
The
statusCodefield in private messages. See Initiator Inbound Response for an example. -
The
statusMsg field. See Initiator Inbound Response for an example. -
The
Descriptionfield in the logs. The contents of thestatusCodeandstatusMsg fieldfields may or may not display in this field, depending on the transaction. See Transaction Details View.
Note: In the
statusMsg field, the text explains the meaning of the code, but does not specify the value that the statusMsg field can contain.| Code (statusCode Field) | Description (statusMsg Field) | Role | Category |
|---|---|---|---|
| 601 | FTP error | Error | |
| 605 | Local posting error | Error | |
| 620 | No HTTP reply after waiting for HTTP acknowledgment wait time. | Error | |
| 630 | Mime encoding error | Error | Security |
| 631 | Encryption error | Error | Security |
| 632 | Decryption error ERROR_SMIME_DECRYPT | Error | Security |
| 633 | Signature error | Error | Security |
| 634 | Signature verification error ERROR_SMIME_VERIFY | Error | Security |
| 635 | Compression error | Error | |
| 636 | Decompression error | Error | |
| 637 | Receipt request error | Error | |
| 638 | Receipt match error | Error | |
| 639 | MDN receipt request state error | Error | |
| 640 | Receipt disposition error | Error | |
| 641 | HTTP headers error | Error | Configuration |
| 660 | Configuration error | Error | Configuration |
| 661 | Bad configuration - No matching TP email address ERROR_TP_CONFIG | Error | Configuration |
| 662 | Missing decryption key | Error | Configuration |
| 663 | Missing authentication certificate | Error | Configuration |
| 699 | Internal system error | Error | System |
| 1000 - 1999 | Private-party defined codes |