General Information - Error Messages (ER)
Error Messages (ER)
This section of the Nlets User Guide presents pertinent information about error messages. If Nlets detects any condition that prevents delivery of an input message to the destination, an error message will be sent to the originating station explaining the condition.
Note: The Nlets system (ORI NL0000000) is the only originator of ER messages. Neither state computer systems nor terminals may generate ER messages.
Nlets Error Message Specifications
Each Error Message Will Contain:
- Standard output header
- A numeric and plain English error notification.
- The first 100 characters of the input message.
- The sending ORI will always be NL0000000. (ORI assigned to the Nlets message-switch [NJIN])
Nlets Error Messages, Numbers and Explanations
Below is a list of all error messages generated by Nlets with the associated error numbers for each error message.
Error #:
Nlets Error Message:
Explanation:
0
MESSAGE FORMAT/STRUCTURE ERROR
THE RECEIVED MESSAGE IS INCORRECTLY FORMATTED
The received message was not formatted correctly.
.01.
INVALID HEADER INFORMATION
This error message indicates that there is an error in the message header. Specific information about the error is returned in the message itself.
.02.
MESSAGE TYPE NOT ALLOWED TO DESTINATION
Indicates that a state does not accept the message type being sent. Specific information about the error is returned in the message itself.
.03.
TXT NOT FOUND OR IMPROPERLY FORMED XML
The Nlets System encountered a problem parsing the XML or the TXT could not be found in the message. Specific information about the error is returned in the message itself.
.04.
MEXICAN CDL ERROR
Missing or invalid field to destination. Specific information about the error is returned in the message itself.
.05.
DOB INVALID or MISSING
Indicates that the DOB field could not be found, exceeded maximum length or had a non-numeric character within the date of birth.
.06.
INVALID MESSAGE FORMAT FOR CN
Missing or invalid field to destination. Specific information about the error is returned in the message itself.
.10.
A YEAR FIELD IS INVALID or MISSING
A year field such as VYR, BEG, END and LIY is invalid or missing. Specific information about the error is returned in the message itself.
.14.
FIELDS MISSING
Indicates that a required field could not be found. Specific information about the error is returned in the message itself.
.16.
ATN FIELD INVALID
Indicates that the attention field has invalid characters. Specific information about the error is returned in the message itself.
.19.
INVALID DESTINATION ORIs
Indicates that the message is being sent to an invalid destination. Specific information about the error is returned in the message itself.
.20.
INVALID CONTROL FIELD
Indicates that the control field is too long or has illegal characters. Specific information about the error is returned in the message itself.
.21.
INVALID SENDING ORI
Indicates that the source ORI is invalid or does not belong to the user. Specific information about the error is returned in the message itself.
.22.
INVALID MESSAGE FORMAT
Indicates that incorrect fields or missing fields found in message. Specific information about the error is returned in the message itself.
.23.
INVALID FIELD LENGTH
Indicates that a required field is too short or too long. Specific information about the error is returned in the message itself.
.24.
MESSAGE HAS AN INVALID FIELD
Indicates that there is an invalid field in the message. Specific information about the error is returned in the message itself.
.27.
MESSAGE HAS TOO MANY DESTINATIONS
Indicates that the user has included too many destinations.
.29.
MESSAGE NOT ALLOWED FROM SENDER
Indicates that the sender has tried to send a message type that they are not authorized to send.
.53.
DESTINATION DOES NOT ACCEPT MESSAGES FROM THIS TYPE OF ORI
Indicates that the destination does not accept messages from this ORI type (i.e. ORI ending in a "S" or "F").
.54.
TOO MANY DESTINAITONS FOR HIT CONFIRMATION
Indicates that too many destinations have placed in the header of the hit confirmation.
.75.
REQUIRED FIELD MISSING
Indicates that a required field is missing from the message type. Specific information about the error is returned in the message itself.
A snippet of an XML Error Message:
<n2:ResponseText><![CDATA[.01. MSG TYPE INVALID or INVALID TO DESTINATION]]></n2:ResponseText>