User Guide : Error Codes and Message : Transformation Engine Error Codes : Transformation Engine Error Return Codes
 
Share this page                  
Transformation Engine Error Return Codes
The following is a list of error messages that may occur while using Map Editor. The messages are listed in numerical order.
Base Transformation Processing Return Codes
 
Number
Short Description
Explanation
25001
OUT_OF_MEMORY
Not enough memory to complete Runtime Engine request.
25002
UNSUPPORTED_VERSION
An unsupported version of Visual Basic attempted to use Runtime Engine.
25003
UNKNOWN_CONNECTOR_TYPE
Returned in either of two different contexts:
A connector (spoke) type was not selected for the source or target. In this case, the error includes the message "Spoke type invalid or unspecified."
The requested connector cannot be loaded. In this case, the message "Unable to create new Connector" appears.
Reasons a connector cannot be loaded:
The connector registry (connlist) cannot be found. The registry is usually located in the Runtime Engine install directory. Invalid connector name given.
Runtime Engine is unable to locate the dynamic libraries required for the connector using the application search path.
The -Initialization_Info command line option can be used to specify the name and location of the registry with the ConnListFile and LibraryPath entries.
Problem with installation and configuration of third party dynamic libraries.
Not enough system memory or other necessary resource.
The connector is not supported on 64-bit Runtime Engine.
25004
UNKNOWN_ACTION
Returned when an application tries to assign an invalid action.
25005
INVALID_FIELD_INDEX
An invalid field index or an invalid field name was encountered.
25006
INVALID_OPTION
An error was encountered trying to retrieve a connector option value from a connector.
25007
FIELD_NAME_NOT_DEFINED
Returned when an application attempts to reference an invalid line style field name.
25008
INVALID_IMPORT_CONTROL
The source on the transformation is invalid or unspecified. Certain API functions require that a source be bound to a target to execute properly. In addition, the Import Transformation and Export Transformation options require a valid source bound to a valid target.
25009
NO_CONNECTION
No connection established for data source. Can occur on a source or a target.
25010
INVALID_EXPRESSION
An expression is invalid. The expression may not be syntactically correct, or it may reference undefined fields.
25011
FIELD_NAME_TOO_LONG
Specified field name exceeds the maximum length for field names for the currently selected connector. This error occurs when defining fields.
25012
FIELD_NAME_BAD_CHAR
Assigned field name includes one or more invalid characters for the current connector type.
25013
FIELD_NAME_RESERVED_WORD
Specified field name is invalid because it is a reserved word.
25014
FIELD_NAME_NOT_UNIQUE
Field name that is not unique is encountered.
25015
UNKNOWN_BROWSER_TYPE
Browser type is unknown or not supported.
25016
FIELD_COUNT_EXCEEDED
Field count has been exceeded.
25017
INDEX_ERROR
Returned when an application attempts to use an index for an array that is out of range.
25018
VALUE_ERROR
A value is out of range or invalid.
25019
UNKNOWN_DATA_TYPE
This error is returned when an invalid datatype name is assigned.
25020
LOSS_OF_PRECISION
A field definition has been copied from the layout for one data source to the layout of another data source, and the target layout does not support a compatible datatype with the same precision as the data type for the source field definition. This is considered a warning for most applications.
25021
INVALID_STYLE_CONTROL
The application has made a request that requires that the DJText control be bound to the DJStyle control.
25022
INVALID_STYLE_INDEX
An invalid index was specified for a line style in the DJText control.
25023
STYLE_NAME_NOT_DEFINED
An invalid line style name was specified as an index for a line style in the DJText control.
25024
STYLE_NAME_NOT_UNIQUE
An attempt was made to add a new line style definition in the DJText control and a line style with the same name has already been defined.
25025
OPTION_SCHEMA_CONFLICT
A connector option was set that may invalidate the target structured schema. This can happen in situations where the application is appending data to an existing file, and the file format is a format that determines record characteristics based on options settings, and there is a connection to the target data. For example, the application has designed a transformation specification that uses append mode with a fixed ASCII target file and then changes the record separator. The fixed ASCII connector uses the record separator to determine the record lengths. If the target layout is designed with the assumption of one record length and the option setting changes this assumption, the layout is likely to be invalid. The best way to avoid this sort of problem is to make sure all option settings are made prior to layout design.
25026
IMPORT_TRANSFORMATION
Error importing the transformation.
25027
EXPORT_TRANSFORMATION
Error exporting the transformation.
25028
EXPORT_PARTIAL
Exporting partial transformations is invalid. A partial transformation is a transformation specification that is missing an active connection for either the source or target data. Exports of partial transformations are not currently supported. The application should ensure that both halves of the transformation are connected and try again.
25029
NO_REJECT_FILE
During a transformation, if one of the mapping Expressions calls the Reject() Function and no reject log is connected, the error callback routine will be called passing this error code. This is considered a warning for the application user, so it is fired only once during a transformation.
25030
TRANSFORMATION_ABORTED
If a transformation is aborted with either the DJAbort API function or by a map expression calling the Abort() function, the error callback routine will be called with this error code. This is an advisory error code.
25031
BUFFER_TOO_SMALL
A buffer passed to receive a value that is too small for the entire value to be returned.
25032
UNCOMMITTED_ TRANSACTION_BATCH
An uncommitted transaction was encountered.
25033
TRANSACTION_BATCH_NOT_ STARTED
A commit transaction or rollback transaction was requested when a transaction had not previously been started.
25034
TRANSACTION_BATCH_TOO_ LARGE
The size limit on a batch transaction has been exceeded.
25035
SOURCE_TARGET_LICENSE
Licensing error. Invalid combination of source and/or target types.
25036
RECORD_LAYOUT_NOT_ DEFINED
Record layout not specified.
25037
INVALID_RECORD_LAYOUT_ INDEX
Invalid structured schema index.
25038
RECORD_LAYOUT_NAME_NOT_ UNIQUE
Record layout name not unique.
25039
RECORD_RULE_NOT_DEFINED
Record discriminator rule not defined.
25040
INVALID_RECORD_RULE_INDEX
Invalid record rule index.
25041
RECORD_RULE_NAME_NOT_ UNIQUE
Record rule name encountered that is not unique.
25042
INVALID_RECORD_RULE_ CONDITION
Invalid record rule condition encountered.
25043
INVALID_EVENT_ACTION
Invalid event action encountered.
25044
INVALID_FIELD_NAME
Invalid field name encountered.
25045
INVALID_RECORD_LAYOUT_NAME
Invalid structured schema name encountered.
25046
SAVE_TRANSFORMATION
Indicates an error was encountered while saving the transformation. Specific error details are written to the log file.
25047
LOAD_TRANSFORMATION
Indicates an error was encountered while loading the transformation. Specific error details are written to the log file.
25048
LOAD_MAP
Indicates an error was encountered while loading the map. Specific error details are written to the log file.
25049
SAVE_MAP
Indicates an error was encountered while saving the map. Specific error details are written to the log file.
25050
INVALID_CONVERSION_XML
Indicates an invalid or corrupt transformation file was encountered
25051
INVALID_MAP_XML
Invalid map XML. Indicates an invalid or corrupt map file was encountered
25052
LOAD_STRUCTURED_SCHEMA
Indicates an error was encountered while loading the structured schema.
25053
SAVE_STRUCTURED_SCHEMA
Indicates an error was encountered while saving the structured schema.
25054
INVALID_STRUCTURED_SCHEMA_XML
Invalid structured schema XML.
25055
INVALID_VALIDATION_TYPE
Invalid validation type encountered.
25056
VALIDATION_ERROR
Validation error encountered.
25057
INVALID_ACTION_EXPRESSION
Invalid action expression encountered.
25058
INVALID_DATACHANGE_MONITOR_EXPRESSION
Invalid Datachange Monitor Expression encountered.
25059
INVALID_ACTION_MAP
Invalid action map encountered.
25060
INVALID_ACTION_KEYS
Invalid action keys encountered
25061
INVALID_FILTER_EXPRESSION
Invalid filter expression encountered.
25062
INVALID_CONNECTION_INFO
Invalid connection information encountered.
25063
INVALID_FIELD_EXPRESSION
Invalid field expression encountered.
25064
INVALID_DISCRIMINATOR_ RECORD_RULES
Invalid discriminator record rules encountered.
25065
INVALID_CODE_MODULE
Invalid code module encountered.
25066
XML_PARSE_ERROR
Indicates an error was encountered while parsing an XML document.
25067
XML_READ_ERROR
Indicates a read error was encountered while reading the XML document.
25068
XML_WRITE_ERROR
Indicates an error was encountered while writing the XML document.
25069
XML_PARSER_INITIALIZATION_ERROR
End of File (EOF) error. An attempt was made to read a nonexistent record.
25501
EOF
EOF error. An attempt was made to read a nonexistent record.
25502
BADNAME
Specified file name is invalid, or the file does not exist.
25504
READERR
An error was encountered reading file or table.
25505
NOMEM
Out of memory.
25507
CREATERR
Error encountered when creating file or table.
25508
WRITERR
Error writing to a file or table.
25509
NOSPACE
No space available on disk.
25510
INDEX_ERROR
Index error encountered.
25511
RECTOOBIG
Record definition is too large. The Structured Schema contains too many fields, or the combined size of each of the fields exceeds the maximum record length for the data format.
25512
NOSOURCE
An attempt was made to perform some operation on a data source and the data source is not connected.
25513
BADLOGIC
An internal error occurred while attempting to set a connector option.
25514
BADUPDATEOPTS
An internal error occurred while initializing the Update option settings after a target connector is switched to Update mode.
25515
BADMATCH
Target layout and target file or target definitions do not match.
25516
BADMODE
The application attempted to set an invalid output mode for target data.
25517
INDEX_INVALID
An attempt was made to define an invalid index. One or more of the fields in the index do not exist in the layout.
25518
NOLAYOUT
No fields defined for the target data and an attempt was made to open the target for output.
25519
OPENERR
Error opening data source.
25520
BADFILETYPE
Invalid or corrupt data file.
25521
DELETERR
Unable to delete a file, drop a table, or delete all of the records from the target data.
25522
INDEX_UNSUP
Unsupported index.
25523
SQL_NOSERVER
Bad or missing server name.
25524
SQL_LOGERR
Server login error.
25525
BADTYPE
Invalid data or record type.
25526
FIELDNAME
Invalid field name.
25527
CLOSERR
Error closing target file.
25528
DELETED
Attempting to delete a record that is already marked as deleted.
25529
RECCRYPTERR
Records are encrypted.
25530
RNOTOOBIG
The record number is greater than maximum allowed.
25531
USERID
Invalid user ID encountered.
25532
BADOPTIONNAME
Invalid property name encountered.
25533
BADOPTIONVALUE
Invalid property value encountered.
25534
INVALID
Generic error meaning the connector encountered some type of unusual error condition.
25535
NOBROWSER
Bad or missing data structure browser.
25536
NOMEMOFILE
Bad or missing memo file. Some data formats use a separate file to store memo fields. Error is returned if the data source layout includes memo fields, but the memo file cannot be found.
25537
SORTFILE
The target connector was unable to create a sort index file.
25538
SORTDUP
Returned when a duplicate is encountered and duplicates are not allowed.
25539
FIELDCOUNT
Too many fields in structure.
25540
MEMOCOUNT
Too many memo fields in structure.
25541
MEMOPOS
Memo field in wrong position in structure.
25542
TRUNCATE
Returned by source and target connectors. For a target, this is returned only when the Truncation Handling option is set to error. For a source, it is returned when the Truncation Handling option is either warn or error. To change the settings, see Setting Preferences.
25543
RUNTIMERR
Run­-time error evaluating expressions.
25544
NOTSUP
Indicates that a connector does not support a particular method.
25545
NOTIMP
Indicates that a connector has not implemented a particular method.
25546
LICENSING
Indicates that a particular connector or browser is not licensed for the product version.
25547
LOADLIBRARY
Indicates that the load library for a particular connector or browser failed to load or could not be found.
25548
SUPPDLL
Indicates that a load library required by the connector or browser (supporting load library) failed to load or could not be found.
25549
NEWPROC
Indicates an error was encountered trying to get the address of a function in a load library.
25550
UNSPECIFIED
An error occurred while loading a new connector or browser.
25551
USERABORT
The loading of a connector or browser was aborted at the request of the user.
25552
OVERFLOW
Returned by sources and targets. For a target, this is returned when the Overflow Handling option is set to error. For a source, it is returned when the Overflow Handling option is set to warn or error.
25553
NOCONNECTION
No connection established.
25554
SQLEXECERR
SQL statement execution error.
25555
EXTEXECERR
External application execution error encountered.
25556
NULLINSERT
Null value not allowed.
25557
NOTUNIQUE
Key value not unique.
25558
CONSTRAINT
Integrity constraint error encountered.
25559
DICTNOSOURCE
Metadata source not defined.
25560
DICTOPENERR
Error opening metadata source.
25561
DICTREADERR
Error reading metadata.
25562
IOWAIT
Waiting on input.
25563
MISMATCH
No matching records for update.
25564
SQLTRANSACTION DEADLOCK
Transaction deadlock detected.
25565
LICENSE_EXPIRED
Appears only in code that is commented out
25566
TIME_EXPIRED
Indicates when a message expiration date is reached.
25567
ASSERTION_FAILED
Indicates an Assert action failed.
25568
RECORD_INVALID
Returned when a Validate Record action fails.