Error Codes

Support | 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).

Legacy codes (for APs deployed in Galaxy Gateway before December 1st 2019) listed at the bottom of this page should preferably not be used by you. It is advised to use the 4 digit codes instead.

Usage of legacy code: 504 will be replaced with following new error codes:
	-4001 : A payload MUST be of valid XML and have contents. Found payload with (${customData} bytes) content.

 Usage of legacy code: 507 will be replaced with following new error codes:
	-4002 : The supplied payload could not be parsed as valid XML. Pleasy verify that the payload is valid.
	-4000 : Corrupt data in received file. Original filename: [${customData}]. With error; ${customData}

 Usage of legacy code: 510 will be replaced with following new error codes:
	-1403 : Contents of ${customData} could not be unmarshalled to ${customData}. With error; ${customData}
	-1400 : Failed to deserialize contents to ${customData}. With error; ${customData}

 Usage of legacy code: 511 will be replaced with following new error codes:
	-1402 : Contents of ${customData} could not be marshalled to ${customData}. With error; ${customData}

 Usage of legacy code: 512 will be replaced with following new error codes:
	-1367 : Could not parse the endpoint certificate

 Usage of legacy code: 517 will be replaced with following new error codes:
	-4100 : Document validation was completed with reported errors. ValidatorResult=[${customData}]

 Usage of legacy code: 601 will be replaced with following new error codes:
	-1362 : Http error 404 participant identifier not found
	-1360 : The participant ${customData} cannot be resolved in the SML

 Usage of legacy code: 602 will be replaced with following new error codes:
	-4310 : Resolved profile ${customData} is unsupported and cannot be exchanged with this Access Point implementation.

 Usage of legacy code: 603 will be replaced with following new error codes:
	-1366 : No matching processidentifier found or no processidentifier with valid endpoint

 Usage of legacy code: 604 will be replaced with following new error codes:
	-1365 : Unexpected documentidentifier returned
	-1363 : Http error 404 document identifier not found

 Usage of legacy code: 605 will be replaced with following new error codes:
	-1370 : Generation of the SML URL could not be completed. Either an unsupported encoding was provided or requested algorithm is not available.
	-1369 : The resolved endpoint Access Point URL '${customData} is malformed.

 Usage of legacy code: 607 will be replaced with following new error codes:
	-1361 : Unknown reason, SMP query failed. With error; ${customData}

 Usage of legacy code: 608 will be replaced with following new error codes:
	-1364 : Failed to unmarshall response

 Usage of legacy code: 609 will be replaced with following new error codes:
	-1368 : Unknown transport profile found

 Usage of legacy code: 707 will be replaced with following new error codes:
	-4340 : Communication with receiving AP @ ${customData} failed. With error; ${customData}

 Usage of legacy code: 709 will be replaced with following new error codes:
	-4330 : Receiving AP reported an error during exchange. With error; ${customData}
	-4378 : Receiving AP responded with an error or negative MDN.

 Usage of legacy code: 710 will be replaced with following new error codes:
	-1404 : Failed to parse MDN: ${customData}

 Usage of legacy code: 713 will be replaced with following new error codes:
	-4373 : AS2Request, problems with provided certificate

 Usage of legacy code: 715 will be replaced with following new error codes:
	-4379 : Failed to find an ISO6523 sender identifier.

 Usage of legacy code: 716 will be replaced with following new error codes:
	-4380 : Failed to find a RelayoperatorIdentifier.

 Usage of legacy code: 800 will be replaced with following new error codes:
	-4381 : Expected AS2 Header '${customData}', but it was not found.

 Usage of legacy code: 801 will be replaced with following new error codes:
	-4382 : Disposition Notification Options could not be understood, received value = [${customData}]

 Usage of legacy code: 802 will be replaced with following new error codes:
	-4383 : Could not parse disposition notification parameter. ${customData}

 Usage of legacy code: 803 will be replaced with following new error codes:
	-4384 : Unsupported MIC algorithm. ${customData}

 Usage of legacy code: 804 will be replaced with following new error codes:
	-4385 : No understandable content type set for MIME message. Content-Type was '${customData}'

 Usage of legacy code: 805 will be replaced with following new error codes:
	-4386 : Failed to parse attached MIME message, perhaps it is corrupt. ${customData}

 Usage of legacy code: 806 will be replaced with following new error codes:
	-4387 : This Access Point only supports AS2 version '${customData}', supplied version was '${customData}'

 Usage of legacy code: 807 will be replaced with following new error codes:
	-4388 : Sending AP identified itself as '${customData}', but according to attached certificate the senders identity is '${customData}'

 Usage of legacy code: 808 will be replaced with following new error codes:
	-4370 : Failed to calculate message digest for MimeBody

 Usage of legacy code: 809 will be replaced with following new error codes:
	-4003 : Failed to extract DocumentIdentifier from SBDH.

 Usage of legacy code: 810 will be replaced with following new error codes:
	-4004 : Failed to extract ProcessIdentifier from SBDH.

 Usage of legacy code: 811 will be replaced with following new error codes:
	-4390 : AS2 Transaction seems to contain corrupted or unsupported payload. ${customData}

 Usage of legacy code: 890 will be replaced with following new error codes:
	-1210 : Failed to extract key '${customData}' from ExecutionContext.
	-1271 : Value ${customData} of type ${customData} cannot be mapped to a representation of ${customData}.
	-1261 : The certificate import could not be completed. ${customData}
	-1201 : Provided encoding ${customData} is not supported.
	-1227 : Failed to process unknown EnvelopeFormat ${customData}
	-1297 : The RuleAction ${customData} is not supported by the implementation.
	-1263 : There already exists a configuration for this certificate with ID ${customData}.
	-1299 : Could not find errorhandling rule for error with code ${customData} and from job ${customData}
	-1225 : Failed to deserialize JSON [${customData}] to ${customData}. With error; ${customData}
	-1221 : Data inconsistency detected. Expected to modify ${customData} rows but result affected ${customData} rows.
	-1298 : There exists multiple errorhandling rules for error with code ${customData} and from job ${customData}.
	-1223 : Quarantine Trigger is invalid. With error; ${customData}
	-1266 : Unable to decrypt private key. With error; ${customData}
	-1260 : The certificate file ${customData} could not be found.
	-1255 : MD5 sum of file ${customData} and file ${customData} do not match.
	-1200 : Unexpected status '${customData}' found.
	-1290 : The error code ${customData} could not be correlated with a GGWErrorType.
	-4005 : Cannot process on-boarding request due to inconsistency error. ${customData}
	-1220 : Failed to extract ${customData}-object from database using ID '${customData}'.
	-1226 : Failed to persist public certificate. With error; ${customData}
	-1229 : Failed to insert ${customData} to table '${customData}'. With error; ${customData}
	-1222 : Object of type ${customData} holding value ${customData} is malformed. With error; ${customData}
	-1270 : Mandatory input parameter ${customData} is null
	-1228 : Failed to calculate ${customData} for '${customData}'. With error; ${customData}
	-1262 : The result for filename ${customData} is ambigous. Found ${customData} matching files.
	-1224 : Payload type ${customData} is unsupported.
	-1264 : Certificate import would change the relay operator id of an already configured certificate witd ID ${customData} and ROID ${customData}.
	-1211 : Inconsistency in Spring Batch Context detected. With error; ${customData}
	-1267 : A generic certificate parse error occurred. ${customData}
	-1265 : Unable to encrypt private key. With error; ${customData}

 Usage of legacy code: 891 will be replaced with following new error codes:
	-1341 : Failed to complete operation '${customData}'. With error; ${customData}
	-1321 : Failed reading local file object from path '${customData}' With error; ${customData}
	-1310 : Unable to communicate with FileArchiver; ${customData}.
	-1340 : Failed to connect to FTP server @ '${customData}:${customData}'.
	-1350 : Interaction with Validation Engine returned unexpected faults. With error: ${customData}
	-1320 : Failed writing local file resource to path '${customData}' With error; ${customData}

 Usage of legacy code: 892 will be replaced with following new error codes:
	-1401 : Unable to parse file ${customData} with error; ${customData}

 Usage of legacy code: 893 will be replaced with following new error codes:
	-1703 : Certificate could not be entrusted. With error; ${customData}
	-1704 : Internal certificate infrastructure seems corrupt. With error; ${customData}
	-1700 : Stored certificate for ROID [${customData}] cannot be parsed. ${customData}
	-1701 : Certificate for id ${customData} is invalid
	-1702 : Certificate is expired since ${customData}.

 Usage of legacy code: 894 will be replaced with following new error codes:
	-4102 : Document validation reported mismatch error. ValidatorResult=[${customData}]
	-4101 : Provided document is not supported by document validator.

 Usage of legacy code: 895 will be replaced with following new error codes:
	-4371 : AS2Request, failed to create mimebody
	-4375 : AS2Request, Unable to generate signed mime multipart
	-4377 : Unable to save changes to Mime message
	-4374 : Unable to create JcaCertStore with provided certificates
	-4372 : AS2Request, unable to create SignedMimeMessage du to not able to create operator
	-4376 : Unable to  set Content type of MimeMessage

 Usage of legacy code: 896 will be replaced with following new error codes:
	-4401 : Receiver ParticipantIdentifier value not according to specification (POLICY 1)
	-4402 : Receiver ParticipantIdentifier issuing agency not supported (POLICY 4)
	-4404 : Sender ParticipantIdentifier value not according to specification (POLICY 1)
	-4403 : Receiver ParticipantIdentifier schema not supported (POLICY 5)
	-4412 : ProcessIdentifier, Identifier, contains whitespaces
	-4406 : Sender ParticipantIdentifier schema not supported (POLICY 5)
	-4405 : Sender ParticipantIdentifier issuing agency not supported (POLICY 4)
	-4407 : DocumentIdentifier value not according to specification (POLICY1)
	-4408 : DocumentIdentifier schema not supported (POLICY 10)
	-4409 : DocumentIdentifier value not according to specification (POLICY 13)
	-4411 : ProcessIdentifier schema not supported (POLICY 15)
	-4410 : ProcessIdentifier value not according to specification (POLICY1)

 Usage of legacy code: 897 will be replaced with following new error codes:
	-9999 : An unhandled error occurred: ${customData}

 Usage of legacy code: 997 will be replaced with following new error codes:
	-4389 : Failed to receive incoming AS2 transaction. Please contact support@tickstar.com with information regarding this transaction for a quick resolvement of this problem.

Below are the error codes if your Access Point went live before December 1st 2019. 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. Please 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. Make sure that the RecipientIdentifier used in the envelope is correct. Perform a Particpant Lookup to verify it.If the file was intended for a Norwegian receiver, check the current status of Elma, the Norwegian SMP.Re-send the file.If re-send fails, the SMP where the participant is registered or the SML most likely suffer a temporary disruption. If it is a file to a Norwegian receiver and the status of Elma is OK (see paragraph 2 above), then an SML disruption is the probable cause. Then, wait a few minutes and re-send the file.
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 receiver 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 receiver 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.
Re-send the file.
 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.
Re-send the file.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 unsupported 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 sender’s 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 a Participant Lookup.