Core Translator Error Messages
Core translator type errors can occur when you are receiving or sending data.
The core translator error messages are listed below in numerical order based on their Message ID. The table also includes an explanation of the error and an action you can take to correct the error.
| Msg ID | Message Text | Explanation | Your Action |
|---|---|---|---|
| 830 | Null Character | The data file contains binary data. | Contact your Trading Partner. |
| 833 | Unexpected End of File | A field of a specified length is incomplete. | Contact your Trading Partner. |
| 835 | Unexpected Start of Text | The record does not contain End of Text character. | Contact your Trading Partner. |
| 836 | Unexpected End of Text | The record does not contain Start of Text character. | Contact your Trading Partner. |
| 837 | Missing Stream Separator1 | The system is reading non-streamed data with a template from a map where "stream segments" box is unchecked. | Contact your Trading Partner. |
| 838 | Missing Stream Separator2 | The system reading non-streamed data with a template from a map where "stream segments" box is unchecked. | Contact your Trading Partner. |
| 839 | Unexpected Separator | A group separator, segment separator, field separator, STX, or ETX is present in the data. | Contact your Trading Partner. |
| 840 | Unexpected Field Separator | Based on the map, two field separators occur consecutively or a different separator is expected. | Contact your Trading Partner. |
| 841 | Unexpected Group Separator | Based on the map, a group separator occurs when none was specified. | Contact your Trading Partner. |
| 842 | Missing Group Separator | Based on the map, a group separator is missing. | Contact your Trading Partner. |
| 843 | Unexpected Stream Separator1 | Based on the map, a stream separator1 is occurs when none was specified. | Contact your Trading Partner. |
| 845 | Positional Tag Defined Beyond EOS | The position of the transaction code (Positional Record Tag) is specified to start beyond the end of the segment. | Change the value of the positional segment under the NCPDP Properties tag to start before the end of the segment. |
| 855 | Delimited Segment Has No Fields | The delimited segment must have at least the mandatory fields. | Contact your Trading Partner. |
| 856 | Missing Delimited FS After SS | The delimited field separator is not present after the segment separator. | Contact your Trading Partner. |
| 857 | Field ID Data Does Not Match Map Field ID | The field ID data is different from the defined delimited field ID tag. | Contact your Trading Partner. |
| 858 | Unexpected Char(s) in Delimited Field ID | A separator was found in the delimited field ID data. | Contact your Trading Partner. |
| 859 | Null Character in Delimited Field ID | The delimited field ID contains binary data. | Contact your Trading Partner. |
| 860 | Incomplete Delimited Field ID | The field ID data is shorter than expected. | Contact your Trading Partner. |
| 861 | Missing Delimited Field Data | No data is found after a delimited field ID. | Contact your Trading Partner. |
| 862 | Null Character in Delimited Field Data | The delimited field data contains binary data. | Contact your Trading Partner. |
| 865 | Segment ID Data Does Not Match Map Segment ID | The segment ID data is different from the defined delimited segment ID field. | Contact your Trading Partner. |
| 866 | Unexpected Char(s) in Delimited Segment ID | A separator was found in the delimited segment ID. | Contact your Trading Partner. |
| 867 | Null Character in Delimited Segment ID | The delimited segment ID contains binary data. | Contact your Trading Partner. |
| 868 | Incomplete Delimited Segment ID | The delimited segment ID is shorter than expected. | Contact your Trading Partner. |
| 869 | Field ID Size Differs From Global Field ID Size | The computed size of the segment/field ID is different from the value of the global field ID length. | Contact your Trading Partner. |
| 885 | No Data after STX in Batch Segment | The batch record does not contain any data. | Contact your Trading Partner. |
| 886 | Unexpected STX in Batch Segment | The batch record does not contain an ETX character. | Contact your Trading Partner. |
| 887 | Missing ETX in Batch Segment | The batch record does not contain an ETX character. | Contact your Trading Partner. |