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).
Below are the error codes currently in use. The table suggests what action(s) you should take to resolve a specific issue.
| Error code | Error description | Recommended action |
| 501 | PEPPOL Error from receiving Access Point as follows.\r\nGeneral Error: ${customData}\r\nAction: ${customData}\r\nFaultCode: ${customData}\r\nFaultString: ${customData}\r\nDetails: ${customData} | |
| 504 | A payload MUST be of valid XML and have contents. Found payload with (${customData} bytes) content. | |
| 505 | There MUST be exactly one payload in a request. Found (${customData}) payloads. | |
| 507 | The supplied payload could not be parsed as valid XML. Pleasy verify that the payload is valid. | |
| 508 | Failed to relay WS SendRequest to PeppolBridge QueueInterface. | |
| 509 | Received JMS message was not of expected type TextMessage. | |
| 510 | Failed to unmarshall contents [${customData}] to type [${customData}] | |
| 511 | Failed to marshall contents from type [${customData}]. | |
| 601 | The participant is not known in the SML. Generated SML URL did not resolve, either the provided participant identifier does not exist in the SML or the SMP where participant belongs is unresponsive. |
|
| 602 | Transport profile could not be matched in SMP lookup. Participant-, Document- and ProcessIdentifier were all matched, but requested transport profile not present. | Correct the transport profile in the envelope of your file you sent. Re-send the file. |
| 603 | Process identifier could not be matched in SMP lookup. Participant- and DocumentIdentifier were all matched, but requested ProcessIdentifier could not be found. | Either the ProcessIdentifier in your file was incorrect or the reciever is not able to receive the document type you have tried to send. Correct the ProcessIdentifier in your file or change to a document type that the receiver is capable of receiving. Check here for a current list of PEPPOL document types and identifiers currently in use. Re-send the file. |
| 604 | Document identifier could not be matched in SMP lookup. Requested document identifier could not be found | Either the DocumentIdentifier in your file was incorrect or the reciever is not able to receive the document type you have tried to send. Correct the DocumentIdentifier in your file or change to a document type that the receiver is capable of receiving. Check here for a current list of PEPPOL document types and identifiers currently in use. |
| 605 | Generation of the SML URL could not be completed. Either an unsupported encoding was provided or requested algorithm is not available. | Check the encoding of the file you sent. It should be UTF8. Re-send the file. |
| 606 | Generated SML URL could not be used, seems to be malformed. | |
| 607 | An error occurred when connecting to SMP. Refer to stacktrace for more details. | The SMP in which the receiver is located might suffer a temporary disruption. If you are sending to a Norwegian receiver, check the status of the Norwegian SMP Elma. Re-send the file. |
| 608 | Error occurred when unmarshalling response from SMP. The response from the SMP did not contain data in the expected format. | The response from the SMP in which the receiver is registered could not be used to initiate a transaction to the receiver's Access Point. If the error persists, contact the admin of the SMP in which the receiver is registered. |
| 609 | The SMP responded with an unsupported TransportProfile. | This error msg is displayed when an incorrect schema type for the ProcessIdentifier (ProfileId) was used. This is applicable if you use the Envelope type "TransactionRequest" when exchanging files with GalaxyGateway. |
| 620 | Unable to generate a port based on the receiving endpoint address resolved. | |
| 700 | The receiving AccessPoint has rejected the transaction with error: The channel is full and not accepting messages for this destination | |
| 701 | The receiving AccessPoint has rejected the transaction with error: The endpoint is not known for the receiving AccessPoint. | |
| 702 | The receiving AccessPoint has rejected the transaction with error: There is a security error in processing this request. | |
| 703 | The receiving AccessPoint has rejected the transaction with error: The recipient does not accept documents of this type | |
| 704 | The receiving AccessPoint has rejected the transaction and reported an unknown internal server error. | |
| 705 | The receiving AccessPoint has rejected the transaction with error. The cause is unknown since FaultCode according to specification was not used. | |
| 706 | The receiving AccessPoint does not seem to be available, connection cannot be established. Tried connecting to [receiving access point url]. | Check if the receiving Access Point is online at www.galaxygw.com/peppol-ap-monitor. Re-send the file when the AP is online again. |
| 707 | A communication problem occurred during exchange of transaction with receiving AS2 AccessPoint. | |
| 708 | The response from the receiving AS2 server (${customData}) was empty and did not contain the mandatory MDN | |
| 709 | Request failed with with status code = ${customData}, contents received (${customData} characters): \r\n\t ${customData} | A negative MDN was received. Please re-send the file. If the error persists, please contact the receiving Access Point. |
| 710 | Receiving AS2 server (${customData}) returned status code = ${customData}, MDN couldn't be parsed. Contents could be corrupt or failed to follow specification. | |
| 711 | Receiving AS2 server (${customData}) did not include a Content-Type header in the response, MDN cannot be parsed. | |
| 712 | Receiving AS2 server (${customData}) returned an unsupprted Content-Type header = (${customData}), MDN cannot be parsed. | |
| 713 | Failed verifying the certificate used for signing MDN from AS2 server (${customData}). | |
| 714 | Receiving AS2 server (${customData}) reported errors in the MDN. Please check custom error message: \r\n${customData}" | |
| 800 | Expected AS2 Header \"${customData}\", but it was not found. | |
| 801 | Disposition Notification Options could not be understood, received value = [${customData}]" | |
| 802 | Could not parse disposition notification parameter. ${customData}" | |
| 803 | Unsupported MIC algorithm. ${customData} | |
| 804 | No understandable content type set for MIME message. ${customData} | |
| 805 | Failed to parse attached MIME message, perhaps it is corrupt. ${customData} | |
| 806 | This Access Point only supports AS2 version '${customData}', supplied version was '${customData} | |
| 807 | Sending AP identified itself as '${customData}', but according to attached certificate the senders identity is '${customData} | |
| 808 | Failed digesting a MIC value for this transaction. | |
| 809 | Failed to extract DocumentIdentifier from SBDH. | |
| 810 | Failed to extract ProcessIdentifier from SBDH. | |
| 995 | Unhandled exception occurred when processing outbound AS2 transaction. Please contact support@tickstar.com with information regarding this transaction for a quick resolvement of this problem. ERRID=[${customData}] | |
| 996 | Failed to persist incoming AS2 transaction. Please contact support@tickstar.com | |
| 997 | Failed to receive incoming AS2 transaction. Please contact support@tickstar.com with information regarding this transaction for a quick resolvement of this problem. | If you received this message when sending a file to yourself, please ensure that the envelope is complete and correct, visit https://www.galaxygw.com/support/payload-envelope for more information. |
| 998 | When sending an unhandled exception was thrown. | |
| 999 | During transaction with receiving access point an unrecoverable error occurred, retry policy enforced but failed as well. | The receiving Access Point might suffer from a temporary disruption. Please re-send the file. If the error persists, contact the support/helpdesk/admin of the receiving AP by doing an Participant Lookup. |
