RN20Agent Error Messages
This topic describes the error messages that the Delivery Agent writes to the Audit Log.
See "Using the Audit Notification System" in the IBM® Sterling Gentran:Server® for Microsoft Windows Administration Guide for more information on the audit log. Also see the Using the PIP Profiler section for more information.
The following table describes the Delivery Agent error messages.
| Msg ID | Message Text | Explanation | Your Action |
|---|---|---|---|
| 4-11-100 | Invalid option parameter specified. Delivery agent processing cannot continue. | "Inbound" and "Outbound" are the only valid parameters. | Ensure that the delivery rule is not mistyped. |
| 4-11-103 | Delivery agent failed to process attachment [Mailbox attachment ID] for message [Mailbox message ID]. | An "end" message that bookends one attachment processing session, and you should get an audit error message before it. | Follow the instructions listed in this appendix for the error message that precedes this one. |
| 4-11-104 | Could not get attachment(s) for message [Mailbox message ID]. Delivery agent processing cannot continue. Mailbox error code returned: [Mercury error code] | Mailbox API error. | Call support. |
| 4-11-105 | Could not delete attachment [Mailbox attachment ID] for message [Mailbox message ID]. Delivery agent processing cannot continue. Mailbox error code returned: [mailbox error code] = Mercury error code. | Mailbox API error. | Call support. |
| 4-11-106 | An exception occurred while processing attachment [Mailbox attachment ID] for message [Mailbox message ID]. Delivery agent processing cannot continue. Error message: [CException error text] | A MFC CException occurred while opening or closing the attachment. | Call support. |
| 4-11-1000 | A file exception occurred while accessing an attachment. Error returned: [CFileException error text] | A MFC CFileException occurred while accessing the attachment. | Call support. |
| 4-11-1001 | An error occurred while processing the attachment. [error text (e.g., "The attachment has an invalid file length.") ] | Depending on the error indicated, either the attachment is empty or a Win32 API or MFC error occurred while performing the task indicated. | Call support. |
| 4-11-1002 | Could not create a new copy of attachment [Mailbox attachment ID] for message [Mailbox message ID]. Mailbox error code returned: [mailbox error code] | Mailbox API error. | Call support. |
| 4-11-1003 | An exception occurred while processing attachment [Mailbox attachment ID] for message [Mailbox message ID]. Error message: [CException error text] | A MFC CException occurred while opening or closing the attachment as a stream. | Call support. |
| 4-11-1004 | Could not delete mailbox message [Mailbox message ID to be deleted] associated with attachment [Mailbox attachment ID] for message [Mailbox message ID]. Mailbox error code returned: [mailbox error code] | Mailbox API error. | Call support. |
| 4-11-1005 | A file exception occurred while accessing the interchange file [interchange filename]. Error returned: [FileException error text] | A MFC CFileException occurred while accessing an interchange file. | Call support. |
| 4-11-1100 | A database error occurred while [task (e.g., "querying the database")]. [error text (e.g., "Can't create the recordset.")] | Depending on the error indicated, either database access info is missing from the registry or a MFC CDatabase/CRecordset error occurred while accessing the database. | Call support. |
| 4-11-1101 | A database exception occurred while [task (e.g., "querying the database")]. Error returned: [CDBException error text] | A MFC CDBException occurred while accessing the database. | Call support. |
| 4-11-1102 | An exception occurred while [task (e.g., "querying the database")]. Error returned: [CException error text] | A MFC CException occurred while accessing the database. | Call support. |
| 4-11-1103 | Could not find the partner EDI code ["partner EDI code"] in the database. | No partner with that EDI code was found in the Partner_tb database table. | Check the EDI code for the partner in question. Verify the EDI Code in the partner definition you created. This EDI code must match the valued entered in the Sender box on the Outbound Envelope PIP Initiation dialog box. |
| 4-11-1104 | An instance with PIPTrackKey [PIPTrackKey] already exists in the database. Unable to insert [document name] document [document IID] from [trading partner name]. | Could not save the new PIP instance data to the PIPTrack_tb database table because the primary key number allocated by the Executive Service already is already being used in that table. | Restart services and try again. If this is unsuccessful, call support. |
| 4-11-1105 | A(n) [role ("initiating" or "responding"] PIP [PIP name] profile (PIP version [PIP version] for RNIF [RNIF version]) was not found for either [trading partner name] or "["Any" keyword ]" partner. The partner is not authorized to do this PIP. | No matching PIP profile entry was found in the PIPProfile_tb database table | Create a PIP profile for the PIP and partner in question. |
| 4-11-1106 | An error occurred while [task (e.g., "querying the database")]. [error text (e.g., "Could not find the signal document.") | This message is used for a variety of errors and will only appear in very unlikely scenarios, such as deleting or modifying PIP documents or profiles while the delivery agent is accessing that data. | Call support. |
| 4-11-1107 | PIP [PIP name] version [PIP version] instance [PIP IID] being traded with [trading partner name] is not in order. | The documents in this PIP set are not in the proper sequence when compared to the document order in the corresponding PIP profile. | Make sure the documents are sent and received in the order specified in the PIP profile. |
| 4-11-1108 | A security violation was encountered with a [document name] document for PIP [PIP name] version [PIP version] instance [PIP IID] being traded with [trading partner name]. [security violation type]. | The security properties of the inbound document do not match the security settings in the corresponding PIP profile. | Make sure the security properties of the document and the PIP profile match. |
| 4-11-1109 | A [document name] document for PIP [PIP name] version [PIP version] instance [PIP IID] being traded with [trading partner name] arrived late since the corresponding [parent action document name] document has already timed out and is being resent. | The inbound signal document arrived too late to be considered a valid acknowledgement since its parent action document is being resent. | Wait for the resend process to complete. The signal document will eventually be resent by the trading partner. |
| 4-11-1111 | A [document name] document was received from [trading partner name] for PIP [PIP name] version [PIP version] instance [PIP IID] since the [parent action document name] document that we sent is bad (and will be errored). | An inbound exception document was received because you sent a bad action document. | Check all maps to ensure that a valid document is being sent. |
| 4-11-1112 | A [document name] document was received from [partner name]. There is a problem with the [document name of bad document] document belonging to PIP [PIP name of bad document] version [PIP version of bad document] instance [PIP IID of bad document]. That PIP will be errored. | The trading partner did not receive a response from you after sending an action document and thus initiated a PIP 0A1 document since the retry attempts for the action document have been exceeded. | Make sure there are no communications, network, or system problems. Check your map and partner settings to ensure a proper response document can be generated. Call support if necessary. |
| 4-11-1113 | The document name "[document name of first instance]" of the initiating instance for PIP [PIP name] version [PIP version] instance [PIP IID] being traded with [trading partner name] does not match any document name in the corresponding profile. | The document name in the data does not match any document name in the profile. | Check all maps to ensure that the document name matches the one in the PIP profile. |
| 4-11-1114 | The initiating document for PIP [PIP name] version [PIP version] instance [PIP IID] being traded with [trading partner name] is missing. The PIP set will be errored. | The documents in this PIP set are not in the proper sequence when compared to the document order in the corresponding PIP profile. | Make sure the documents are being sent and received in the order specified in the PIP profile. |
| 4-11-1115 | Due to [reason for discarding messages] message [Mailbox message ID], this message and all related mailbox messages will be discarded. | Mailbox messages will be deleted because of either a security violation or an exception that was generated. | Refer to the previous audit message for further explanations about the error. |