Bookshelf v7.5: Load and Run Error Codes

Table 21. EIM Error Codes for Load and Run Errors (400-499)
Code	Message Text	Description	Recommendation
401	Missing process section in configuration file.	The RUN PROCESS parameter of the configuration file header section named a process for which there is no corresponding process section.	Check and correct the process name provided by the RUN PROCESS parameter or create a process section for the named process.
402	Invalid process type in section.	The PROCESS TYPE parameter of the configuration file process section contained a value other than IMPORT or SHELL.	Correct the parameter value to one of the specific PROCESS TYPE supported.
403	Error resolving includes.	An INCLUDE parameter provided a process name that EIM could not find, or an error occurred when loading the process named in the INCLUDE parameter.	Check all INCLUDE statements to make sure that they refer to valid subprocess sections.
404	Error getting interface table names.	One or more of the EIM table names specified by the TABLE parameters were invalid, or no TABLE parameters were specified.	Check and correct TABLE parameter errors.
405	Invalid batch number specified.	The batch number specified in the process was not valid or was not specified. Batch numbers must be positive integers of fewer than 15 digits.	See Error Message 405 for further details.
406	Invalid choice value in assignment.	The parameter value did not match any of the expected values.	Review and correct parameter values.
407	Invalid Boolean value in assignment.	The value of the parameter should have been TRUE or FALSE, but some other value was found.	Correct the parameter value.
408	Invalid numeric value in assignment.	The value of the parameter should have been a number, but some other value was found.	Correct the parameter value.
409	Invalid table or column in assignment.	The value of the parameter should have been a table or column name, but the value found is not a valid SQL table or column specification.	Correct the parameter value.
410	Invalid report specification.	The value of the parameter should have been a report specification consisting of an optional prefix ("TAB", "CSV", or "columns"), a comma, and the filename used to save the report.	Correct the report specification.
411	SQL WHERE clause expression invalid.	The value was expected to be an SQL WHERE clause expression fragment but was unable to be processed as such.	Make sure the value is an SQL WHERE clause fragment in parentheses.
412	Invalid ONLY/IGNORE BASE TABLES specification.	The value for the ONLY BASE TABLES or IGNORE BASE TABLES parameter should have been a list of base table names, separated by commas.	Correct the parameter value.
413	Invalid ONLY/IGNORE BASE COLUMNS specification.	The value for the ONLY BASE COLUMNS or IGNORE BASE COLUMNS parameter should have been a list of base table column names, separated by commas.	Correct the parameter value. See Error Message 413 for further details.
420	Subprocess failed to execute.	One of the subprocesses identified by an INCLUDE statement failed to execute.	Check the EIM Log File for an indication of why the failure occurred.
421	Interface table not in DB schema.	The TABLE parameter named a table that is not identified as a Siebel EIM table.	Check the spelling and syntax of all values for TABLE parameters. Siebel EIM table names begin with EIM_.
422	No rows in given batch to process.	EIM detected no rows that were eligible for processing and that had the batch number specified by the BATCH NUMBER parameter.	Check to be sure the correct batch number was specified. If it is correct, the rows with that batch number may have a data error.
423	Unable to register with docking log.	Docking Transaction Logging is on, but EIM could not contact the transaction log. There is an installation problem with the Siebel applications database.
424	All interface tables failed.	Importing failed for all specified EIM tables. This generally indicates a data problem.
425	All rows in interface table failed.	Processing for all rows in this EIM table failed. This generally indicates a data problem. Either data was not available for insert, update, delete or merge, or all rows had errors. For example, all rows may be duplicates in a merge process or no rows are based on the user key filled in the EIM table for delete and merge processes.
426	All batches in run failed.	Processing for all batches specified for this run of EIM failed. This generally indicates a data problem.
430	Invalid character seen in string.	Characters were encountered in the WHERE clause fragment that could not be properly interpreted.	Make sure literal string values are enclosed in quotes.
431	Invalid comparison operation.	The comparison operator in a match expression was not understood.	Make sure all comparisons in the WHERE clause fragment are simple column-to-value comparisons.
432	Invalid column name for comparison.	The left-hand side of a comparison in a match expression was not a column.	Make sure all comparisons in the WHERE clause fragment are simple comparisons.
433	End-of-file in quoted string value.	A string being read was not terminated before the expression ended.	Make sure all strings are properly terminated with a closing quote. To embed a quote in a string, double it.
434	Unexpected token in expression.	Unexpected value seen while parsing a matching expression. This represents a syntax error in the SQL WHERE clause fragment.
435	Invalid value for column type.	The value to be compared with this column could not be converted to the column's type.	Make sure the comparison value is of the correct type. Date/time values should be in the ODBC format: yyyy-mm-dd hh:mm:ss.
440	Default/fixed column not found in table.	The configuration file specified a default column or a fixed column, but the column does not exist in the EIM table.	Check the spelling and syntax of the column name.
441	Invalid filter query expression.	The expression provided for the FILTER QUERY parameter did not conform to SQL WHERE clause syntax. Invalid FILTER QUERY expressions usually cause the SQL statement generated during the EIM Import Process to fail with an ODBC error.	Correct the SQL statement and resubmit the process.
442	Update of primary child columns failed.	Updating the primary child key columns failed. This indicates an error during the EIM Import Process.
450	Cannot operate on child table directly.	This EIM table is a child of another. Export, delete, and merge operations must be done on the parent table instead of this child.	Make sure the parent table is included in the process as well as the child.
451	Cannot operate on this IF table directly.	This EIM table has no defined target and thus cannot be used in export, delete, or merge operations. This is an import-only table.
452	Match expression invalid for IF table.	A match expression uses columns that are not present in the current EIM table.	Make sure the match expressions are for the specific EIM tables being processed.
453	Specified column is not exportable.	The requested column cannot be exported. Either this column is not being used or it does not exist.	Omit this column from the list of columns to be exported.
454	Target table for IF table has no user keys.	This EIM table does not support delete exactly or merge (which require user keys) because its base table has no user keys.	You can delete using match expressions, but you cannot merge through this EIM table.
460	Column value too long for base table.	The value in the EIM table column is too long to fit into the base table column. Columns are limited to 4095 bytes.