| Number | Error no. |
Error Message | Description |
|---|
| 1 | 1000 | The status of the message processing is : Import failed:Error 1000 | System Identifier not authorised to connect. This usually occurs if you are trying to use your production certificate before your go-live date |
| 2 | 1001 | The status of the message processing is : Import failed:Error 1001 | Message fails threatening content checking. Some aspect of the XML code is triggering this error. It is nearly always a TAB character, firstly please check your code to ensure all TAB characters are removed. If that does not resolve the issue please send the code to SDT.Mailbox@hmcts.gsi.gov.uk so it can be checked |
| 3 | 1002 | The status of the message processing is : Import failed:Error 1002 | SDT Customer Information missing |
| 4a | 1003 | The status of the message processing is : Import failed:Error 1003 | This occurs when you have entered an incorrect sdtCustomerID. You must ensure that the sdtCustomerID used for all messages is identical to the one supplied to you for SDT Commissioning or Production |
| 4b | SOAP | SOAP fault Fault:MessageBlocked | This occurs when you have entered an incorrect sdtCustomerID. You must ensure that the sdtCustomerID used for all messages is identical to the one supplied to you for SDT Commissioning or Production |
| 5 | 1004 | The status of the message processing is : Import failed:Error 1004 | This error occurs when the XML is not passing schema validation. Examples include:- Request bulk feedback request which is not equal to 29 valid characters
- Tags with Null specified as “”. Do not include the tags for that element at all if you want to send NULL (for an optional field)
|
| 6 | 1005 | The status of the message processing is : Import failed:Error 1005 | No response from SDT Service |
| 7 | 1006 | The status of the message processing is : Import failed:Error 1006 | Outbound message failed XML validation |
| 8 | SSL | SSLPeerUnverifiedException: peer not authenticated | This can occur if you are accessing through a Proxy server. Try connecting without using a proxy server to see if this eliminates the error |
| 9 | SSL | SSLHandshakeException: Received fatal alert: handshake_failure | There could be a problem with the certificate, you may need to generate another .CSR but contact the SDT mailbox if you receive this as there are other reasons why this could occur |
| 10a | SOAP | SOAP Response - FAILED Unexpected element: CDATA | There is likely a problem in the URL or you haven’t entered the correct endpoint. Make sure this is set to https://commissioning.sdt.justice.gov.uk/producers-comx/service/sdtapi
This can also occur if your network connection is intermittent or having other issues. To resolve try using a different network connection |
| 10b | SOAP | Failed to set localAddress to... | There is likely a problem in the URL or you haven’t entered the correct endpoint. Make sure this is set to https://commissioning.sdt.justice.gov.uk/producers-comx/service/sdtapi
This can also occur if your network connection is intermittent or having other issues. To resolve try using a different network connection |
| 10c | SOAP | UnknownHostException | There is likely a problem in the URL or you haven’t entered the correct endpoint. Make sure this is set to https://commissioning.sdt.justice.gov.uk/producers-comx/service/sdtapi
This can also occur if your network connection is intermittent or having other issues. To resolve try using a different network connection |
