On records

Some of the ECMap informational messages are the result of errors in adding, updating, reading and deleting database and index records. Other errors are the result of search or re-index failures. Some of the errors are the result of mistakes made in defining Map Flow records. Some of the messages in this section are described as internal program errors. Internal program error messages are not expected to be displayed. If an internal error message occurs or if the suggested corrective action does not solve a problem, note the message number and any associated DBCIII error number and call support for assistance.

Table 1-4 lists the format, cause, and solution (if applicable) for the ECMap messages related to records, in numeric order by message number.

**Table 1-4: ECMap messages related to records**
Message	Cause	Solution
`(1208) ERROR: invalid record- <EDI segment expected>`	Can occur when an inbound map is running and the inbound EDI X12 file has an invalid or missing control segment. The “EDI Segment Expected” part of the message could be “GS”, “ST” or another control segment name to indicate the control segment that the program was expecting.	Examine the error log and the bad transaction file for the inbound map run to determine where the error occurred.
`(1214) FATAL: can’t find key- <key value>`	Indicates that the index files for a MAPPER database have been corrupted.	Delete the DOS index files (*.NDX) under the current map’s “Data Dictionary Tables” directory. When the MAPPER program is restarted, the index files under the “Data Dictionary Tables” automatically rebuilds. If this does not solve the problem, call support for assistance.
`(1222) FATAL: duplicate record- <record number> found in database- <database>`	Should not display. It can occur when a map is run but the generated tables have become damaged.	Regenerate the map for this transaction. If message occurs again, call support for assistance.
`(1223) FATAL: fseek failed during file read`	An internal error that could occur if, during a map run, an attempt to seek to a saved file location fails.	Call support for assistance.
`(1225) ERROR: <record name> in file <file name> doesn’t have valid record type`	An outbound map run error that occurs when processing a user file that contains multiple records with record type key fields, and a record is read that does not have a type key field value that matches any of the user defined type key field values.	Either correct the user file record so that it has a correct type key field value or modify the User File so that the record key field value of the user file record in error is valid.
`(1226) FATAL: record number out of range- < >`	Could occur when a map is run but the generated tables have become damaged.	Regenerate the map for this transaction. If message occurs again, call support for assistance.
`(1227) FATAL: XML-READ gets into an infinite loop`
`(1228) ERROR: No Tradstat for Tptnr <TRADING PARTNER NAME > Trans <TRANSACTION NUMBER > Vers <VERSION NUMBER> TstInd <TEST INDICATOR NUMBER>Agency <AGENCY NAME> Release <RELEASE NUMBER> – Skipping Forward`	A Trade Agreement entry for this trading partner, for this version, for this test indicator, for this agency, for this release is not present.	Modify the Trading Partner Trade Agreement to link version transaction number for this trading partner. Ensure that agency, release and direction are correct.
`(1230) FATAL: reading record from database- <database>` `(1231) FATAL: reading record- <record number> from database- <database>`	Messages 1230 and 1231 display if a read of a database file fails. When this message occurs, the program has already found or added a record to the database and the read is attempting to retrieve a record that is known to exist in the database. Such an error could occur only if the database or index file has been damaged.	Check to see if the hard disk is full. Also, follow the database re-index procedures outlined in Error 1214 solution. If these corrective procedures fail, then the message can be the result of an internal program error. Call support for assistance.
`(1293) ERROR: Max Record Length of < > exceeded by Record < >`	Occurs when the record you have just defined exceeds the system record length.	If you have requirement that a record exceeds the record boundary, you can define two records – when you write one you write the other. When defining the record, specify NONE as the end of record terminator for the first record.
`(1294) ERROR: Maximum Length < > of EDI record exceeded`	EDI file exceeds the maximum segment length that the system supports.	May be invalid data in the EDI file. Check the EDI file the ensure that segment terminator is present.
`(1297) ERROR: Value- < > is not found in Table- <file name>.XRF`	In performing a cross reference between an EDI value and a user value, the value is not present in the table.	Add the value to cross reference table and regenerate the map.
`(1298) ERROR: Unknown Table Translation Name < file name >.XRF`	A cross reference table has been specified but that table no longer exists. This could occur when you have specified that the table is in an external file, and the file cannot be found. Or a table has been deleted from the list of tables, but is still specified in the mapping under rules.	Verify file location if an external table is specified. If table is no longer needed, and has been deleted from the tables list, remove the rule that calls the table. If the table was erroneously removed, add it again and regenerate the map.
`(1299) DEBUG: Line <line number> Read <record name> Defined Rec Len < >`	Information message. Error occurs when debug mode is on. The record has been defined as a specific length, and the Record read exceeds the defined length	Informational message only.