| Return Code | Short Error Description
| Possible Reason for Error |
|---|
| 25001 | OUT_OF_MEMORY | There is not enough memory to complete Integration Engine request.
|
| 25002
| UNSUPPORTED_VERSION
| An unsupported version of Visual Basic attempted to use Integration Engine
|
| 25003
| UNKNOWN_SPOKE_TYPE
| This error can be returned in two different contexts. First, it can mean that a spoke type has not been selected for the source or target. In this case, the error code will be accompanied by the message "Spoke type invalid or unspecified".
Second, it can mean that the requested spoke can not be loaded. In this case, the message "Unable to create new spoke" will be used.
Reasons a spoke cannot be loaded:
- The spoke registry (connlist) can not be found. The registry is usually located in the Integration Engine install directory.
Invalid spoke name given.
- Integration Engine is unable to locate the dynamic libraries required for the spoke 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.
- Some spokes rely on the proper installation and configuration of third party dynamic libraries.
- Not enough system memory or other necessary resource; it may not be possible to load a spoke.
|
| 25004
| UNKNOWN_ACTION
| This error is returned when an application tries to assign an invalid action.
|
| 25005
| VALID_FIELD_INDEX
| An invalid field index or an invalid field name was encountered
|
| 25006
| INVALID_OPTION
| An error was encountered trying to retrieve a spoke option value from a spoke.
|
| 25007
| FIELD_NAME_NOT_DEFINED
| This error is returned when an application attempts to reference an invalid line style field name.
|
| 25008
| INVALID_IMPORT_CONTROL
| The source on the conversion is invalid or unspecified. Certain API functions require that a source be bound to a target to execute properly. In addition, the Import Conversion and Export Conversion options in the Data Junction product require a valid source bound to a valid target.
|
| 25009
| NO_CONNECTION
| No connection established for data source. This error can occur on a source or a target.
|
| 25010
| INVALID_EXPRESSION
| An expression is invalid. The expression may not be syntactically correct or it references undefined fields.
|
| 25011
| FIELD_NAME_TOO_LONG
| The specified field name exceeds the maximum length for field names for the currently selected spoke. This error occurs when defining fields.
|
| 25012
| FIELD_NAME_BAD_CHAR
| The assigned field name includes one or more invalid characters for the current spoke type.
|
| 25013
| FIELD_NAME_RESERVED_WORD
| The specified field name is invalid because it is a reserved word
|
| 25014
| FIELD_NAME_NOT_UNIQUE
| A field name is not unique.
|
| 25015
| UNKNOWN_BROWSER_TYPE
| The browser type is unknown or not supported
|
| 25016
| FIELD_COUNT_EXCEEDED
| The field count has been exceeded
|
| 25017
| INDEX_ERROR
| This error is returned any time 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_LAYOUT_CONFLICT
| A spoke option was set that may invalidate the target record layout. 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 source. For example, the application has designed a conversion specification that uses append mode with a Fixed ASCII target file and then changes the record separator. The Fixed ASCII spoke 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_CONVERSION
| Error importing the conversion
|
| 25027
| EXPORT_CONVERSION
| Error exporting the conversion.
|
| 25028
| EXPORT_PARTIAL
| Exporting partial conversions is invalid. A partial conversion is a conversion specification that is missing an active connection for either the source or target data source. Exports of partial conversions are not currently supported. The application should ensure that both halves of the conversion are connected and try again.
|
| 25029
| NO_REJECT_FILE
| During a conversion, 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 conversion
|
| 25030
| CONVERSION_ABORTED
| If a conversion 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 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
| TRANSACTION_BATCH_TOO_LARGE
| Licensing error. Invalid combination of source and target types
|
| 25036
| RECORD_LAYOUT_NOT_DEFINED
| Record layout not specified.
|
| 25037
| INVALID_RECORD_LAYOUT_INDEX
| Invalid record layout 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 not unique.
|
| 25042
| INVALID_RECORD_RULE_CONDITION
| Invalid record rule condition
|
| 25043
| INVALID_EVENT_ACTION
| Invalid event action.
|
| 25044
| INVALID_FIELD_NAME
| Invalid field name.
|
| 25045
| INVALID_RECORD_LAYOUT_NAME
| Invalid record layout name.
|
| 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 | Invalid Transformation XML. Indicates an invalid or corrupt Transformation file was encountered (.tf.xml) |
| 25051 | INVALID_MAP_XML | Invalid Map XML. Indicates an invalid or corrupt Map File was encountered (.map.xml) |
| 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 Info 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 an 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 | XML Parser initialization error encountered. |
