Administer > Database administration > Data persistence > Importing records > Load error messages and notifications

Load error messages and notifications

Service Manager displays an error message if it cannot successfully load an external file. The following list contains load error messages and notifications.

Load error message or notification Description
<WINDOWS.FILENAME> or <UNIX.FILENAME> file loaded. Service Manager has finished loading the named file.
File(s) loaded from external file: <WINDOWS.FILENAME> or <UNIX.FILENAME> Service Manager has finished loading the named files.
<Number> records loaded into <Database name> from external file: <WINDOWS.FILENAME> or <UNIX.FILENAME> Service Manager has finished loading <Number> records from the named file.
Loading <Database name> from external file: <WINDOWS.FILENAME> or <UNIX.FILENAME>. Service Manager has started loading <Database name> from the named file.
<Number> records have been loaded so far into the <Database name> file. The load utility generates this message for every hundredth record it attempts to load into the named Service Manager database.
The config record (database load/unload) is missing. The hardware configuration record database load/unload.unix required for database loads and unloads has been deleted or renamed. It must be replaced. Refer to Unload/Load for more information.
The external file <WINDOWS.FILENAME> or <UNIX.FILENAME> is being written to and cannot be read at this time. The load utility could not access the named external file because another task has a lock on it.
Invalid end of file encountered in external file <WINDOWS.FILENAME> or <UNIX.FILENAME>. The load utility encountered an incomplete file. Typically, this means that the unload process was interrupted before completion.
All null keys:file: <Database name>;rec no:<Number> in external file:<WINDOWS.FILENAME> or <UNIX.FILENAME>. The load utility attempted to add record number <Number> to the named Service Manager database and encountered all null keys.
Invalid null key;file:<database name>;rec no:<Number> in external file <WINDOWS.FILENAME> or <UNIX.FILENAME>. The load utility attempted to add record number <Number> to the named Service Manager database and encountered an invalid null key.
Invalid duplicate key:file:<Database name>;rec no:<Number> in external file <WINDOWS.FILENAME> or <UNIX.FILENAME>. The load utility attempted to add record number <Number> to the named Service Manager database and encountered an invalid duplicate key.
External file: %S is not in Unload Format. The named file is not in file format required by the load utility.
You have duplicated column headers: <column names> When duplicate source columns are detected in the external source file, warns the user about the column names.
You have specified data mapping between the target fields and source columns. This will disable RAD expressions. If the user has specified a correct mapping between target fields and source columns, when the user specifies a RAD expression, warns the user that RAD expressions will not work in this situation.
Column not found in external file, column: <columns names> When a specified column is not found in the source file, warns the user about the missing column.
Line <line id> is empty. Skipped the line. When the line being processed is empty, warns the user about the line number.
Error occurs when processing line <line id>. When an error occurs during the processing of a line, warns the user about the line number.
Record already exists on line<line id>. Updated the record. When a record already exists during the processing of a line, warns the user about the line number.
<processed rows count> records processed. When every 100 rows have been processed, notifies the user about the current number of rows processed.

Related topics

Importing records