Cloud Access Point Error codes explained
The error codes described below assume that you have a PEPPOL Access Point managed by Tickstar. If you receive a NACK (negative acknowledgement) for a PEPPOL transaction it will contain a status code (500) and error code(s) with description(s).
Change log
Date Change 2023-12-20 Deprecated error codes -4001, -4002, -4401, -4402, -4403, -4404, -4405, -4406, -4408, -4409, -4410, -4411 and -4412. They have all been replaced by -1403 (integration method TxAPI) or -4000 (for integration method SFTP). 2023-09-04 Added code -4312 which will indicate that receiving AP only supports deprecated transport profile(s).
The column “Expected action” lets you know if you can simply Resend a file without any other action or of you need to first Fix something (i.e your file) before resending.
| Error code | Error description | Recommended action | Expected action (Fix and Resend or Resend) FR/R |
|---|---|---|---|
| -1360 | The participant ${customData} cannot be resolved in the SML | Make sure that the RecipientIdentifier element in the SBDH envelope is valid. Perform a Particpant Lookup to verify it. If re-send fails, the SMP where the participant is registered or the SML most likely suffer from a temporary disruption. | FR |
| -1361 | Unknown reason, SMP query failed. With error; ${customData} | The response from the SMP in which the receiver is registered could not be used to initiate a transaction to the Receiving Access Point. Re-send the file.If the error persists, contact the admin of the SMP in which the receiver is registered.Click here to find the contact details of a receiving AP. | R |
| -1362 | Http error 404 participant identifier not found | Make sure that the RecipientIdentifier used in the envelope is valid. Perform a Particpant Lookup to verify it. If re-send fails, the SMP where the participant is registered or the SML most likely suffer from a temporary disruption. | FR |
| -1363 | Http error 404 document identifier not found | Either the ProcessIdentifier in the SBDH was incorrect or the receiver is not able to receive the document type you tried to send. Correct the ProcessIdentifier in the SBDH or change to a document type that the receiver is capable of receiving. | FR |
| -1364 | Failed to unmarshall response | The response from the SMP in which the receiver is registered could not be used to initiate a transaction to the Receiving Access Point. Re-send the file.If the error persists, contact the admin of the SMP in which the receiver is registeredClick here to find the contact details of a receiving AP. | R |
| -1365 | Unexpected documentidentifier returned | Either the ProcessIdentifier in the SBDH was incorrect or the receiver is not able to receive the document type you tried to send. Correct the ProcessIdentifier in the SBDH or change to a document type that the receiver is capable of receiving. | FR |
| -1366 | No matching processidentifier found or no processidentifier with valid endpoint | Either the ProcessIdentifier in the SBDH was incorrect or the receiver is not able to receive the document type you tried to send. Correct the ProcessIdentifier in the SBDH or change to a document type that the receiver is capable of receiving. | FR |
| -1367 | Could not parse the endpoint certificate | The certificate of the receiving Access Point that was fetched from the SMP, where the receiver is registered, could not be parsed. Contact the receiving AP and notify them to update their certificate in the SMP.Click here to find the contact details of a receiving AP. | FR |
| -1368 | Unknown transport profile found | An incorrect schema type for the ProcessIdentifier (ProfileId) was used. This error is returned only if you use the legacy Envelope type “TransactionRequest” when exchanging files with GalaxyGateway. | FR |
| -1369 | The resolved endpoint Access Point URL ‘${customData} is malformed. | Check the encoding of your file. It should be UTF-8. | FR |
| -1403 | Unable to parse the payload: %s | Ensure that the document is valid XML. Used for integration method TxAPI. | FR |
| -1700 | Stored certificate for ROID [${customData}] cannot be parsed. ${customData} | R | |
| -1701 | Certificate for id ${customData} is invalid | The certificate of the receiving AP is invalid. Please notify the them.Click here to find the contact details of a receiving AP. | FR |
| -1702 | Certificate is expired since ${customData}. | The certificate of the receiving AP is expired. Please notify the them.Click here to find the contact details of a receiving AP. | FR |
| -1703 | Certificate could not be entrusted. With error; ${customData} | The certificate of the receiving AP could not be trusted. Please notify the them.Click here to find the contact details of a receiving AP. | FR |
| -1373 | Timeout occurred communicating with SMP using ‘${customData}’. | The SMP where the receiver is registered might suffer from a temporary disruption. Re-send the file. | R |
| -1803 | Unable to use resolved AS4 endpoint address ${customData}. With error; ${customData}” | Contact the receiving Access Point and let them now about the issue.Click here to find the contact details of a receiving AP. | FR |
| -1804 | AS4 exchange with ${customData} failed unexpectedly (or non-conformant error reporting was used). With error; ${customData}” | The receiving Access Point might suffer from a temporary disruption. Please re-send the file. If the issue remains, you should contact the receiving Access Point.Click here to find the contact details of a receiving AP. | R |
| -4000 | Corrupt data in received file. Original filename: [${customData}]. With error; ${customData} | Ensure that the document is valid XML. Used for integration method SFTP. | FR |
| -4100 | Document validation was completed with reported errors. ValidatorResult=[${customData}] | Fix the validation issues in the document. | FR |
| -4101 | Provided document is not supported by document validator. | The document was forwarded to the receiving Access Point but it could not be validated. Visit https://www.tickstar.com/support/peppol-validator for more information. | |
| -4102 | Document validation reported mismatch error. ValidatorResult=[${customData}] | The document you sent did not match what was declared in the DOCUMENTID element in the SBDH. Fix the document and resend it. Visit https://www.tickstar.com/support/peppol-validator for more information. | FR |
| -4200 | The certificate [${customData}] is revoked. | The receiving Access Point have configured a certificate that has been revoked. This might be due to a misconfiguration or the Access Point may have been excluded from the Peppol network. The receiving Access Point needs to be informed about the situation, and possibly the relevant Peppol Authority. Tickstar can assist in these contacts if necessary. Once the issue with the configuration has been resolved, the transaction can be resent. | FR |
| -4310 | Resolved profile ${customData} is unsupported and cannot be exchanged with this Access Point implementation. | Correct the transport profile in the SBDH envelope of your file. | FR |
| -4311 | Possible security exploit detected. Receiving AP might be subject for an MITM-attack. The receipt of ${customData} exchange was signed with a different certificate than expected. Please alert this with relevant Peppol authority. Expected: ${customData} Actual: ${customData} | Please file a helpdesk ticket on Peppol’s web site. | |
| -4312 | Resolved transport profile [${customData}] has been deprecated since [${customData}]. | Receiving AP only support deprecated transport profile(s). If the error persists, please contact the receiving Access Point. Click here to find the contact details. | FR |
| -4330 | Receiving AP reported an error during exchange. With error; ${customData} | A negative MDN was received from the receiving Access Point. Re-send the file. If the error persists, please contact the receiving Access Point.Click here to find the contact details of a receiving AP. | R |
| -4340 | Communication with receiving AP @ ${customData} failed. With error; ${customData} | The receiving Access Point might suffer from a temporary disruption. Re-send the file. If the error persists, please contact the receiving Access Point.Click here to find the contact details of a receiving AP. | R |
| -4378 | Receiving AP responded with an error or negative MDN. | A negative MDN was received from the receiving Acess Point. Re-send the file. If the error persists, please contact the receiving Access Point.Click here to find the contact details of a receiving AP. | R |
| -4379 | Failed to find an ISO6523 sender identifier. | Visit https://www.tickstar.com/iso6523 for a list of valid identifiers. Update the SenderIdentifier in the SBDH. | FR |
| -4407 | DocumentIdentifier value not according to specification (POLICY1) | Click here to find the link to “Peppol Policy for use of Identifiers” and the related policy. | FR |
| -4413 | Provided value [${customData}] for ParticipantIdentfier is not compliant. | Fix the relevant element in the SBDH. | FR |
| -4414 | Provided value [${customData}] for DocumentIdentifier is not compliant. | Fix the DOCUMENTID element in the SBDH. | FR |
Learn more about PEPPOL in the Frequently Asked Questions section.
SMP API v.2 Error codes explained. The error codes described below assume that you are using the SMP Manager API v.2.
Learn More