Error Codes
The exceptions that are thrown by the plug-in are listed with corresponding descriptions and resolutions.
| Error Code and Error Message | Role | Category | Description | Resolution |
|---|---|---|---|---|
| ERROR_OCCURED_RETRIEVE_RESULT.errorCode=590002
IOException occurred while retrieving XML Output for activity [{0}]. |
errorRole | BW-Plug-in | An IOException occurs while retrieving XML output from the activity. | No action. |
| ERROR_OCCURED_EXECUTE.errorCode=590004
Exception occurred while execute the activity [{0}]. |
errorRole | BW-Plug-in | An exception occurred while executing the activity. | There should be an embedded exception to diagnose. |
| ERROR_COMMON_OBJECT_NOEXIST.errorCode=590005
the object of activity {0} is not exist. The details message is {1}. |
errorRole | BW-Plug-in | The object that the activity operates on does not exist. | Check the object name. |
| ERROR_COMMON_RUN_COMPLETE.errorCode=590006
there are some errors to run the IBMi object {0}.The details message is {1}. |
errorRole | BW-Plug-in | Errors occurred when performing operations on the object. | Depends on the content of the error message. |
| ERROR_COMMON_RUN_IO.errorCode=590007
an error occurs while communicating with the IBMi to run the object of the activity{0}.The details message is {1}. |
errorRole | BW-Plug-in | An error occurred when communicating with the IBM i system. | Depends on the content of the error message. |
| ERROR_COMMON_RUN_SEC.errorCode=590008
a security or authority error occurs while communicating with the IBMi. The details message is {0}. |
errorRole | BW-Plug-in | A security error or authority error occurred when communicating with the IBM i system. | Check the CA file. |
| ERROR_COMMON_RUN.errorCode=590009
the error occurs when run the activity. The details message is {0}. |
errorRole | BW-Plug-in | An error occurred while running the activity. | Check the activity configuration. |
| ERROR_COMMON_CREATE_CONNECTION.errorCode=590010
the error occurs when create IBMi connection for runtime. The details message is {0}. |
errorRole | BW-Plug-in | An error occurred when creating a connection to the IBM i system at runtime. | Check the parameters for the connection. |
| ERROR_PROGRAMCALL_INIT_CHECK.errorCode=520001
The format of program object is invalid. |
errorRole | BW-Plug-in | The format of the program object that the CallProgram activity operates on is invalid. | Check the program object format is valid. |
| ERROR_PROGRAMCALL_INIT_CHECK_NULL.errorCode=520002
The program object is null. |
errorRole | BW-Plug-in | The program object that the CallProgram activity operates on is null. | Check the program object. |
| ERROR_SERVICEPROGRAMCALL_INIT_CHECK.errorCode=530001
The format of program object is invalid. |
errorRole | BW-Plug-in | The format of the service program object that the CallServiceProgram activity operates on is invalid. | Ensure the service program object format is valid. |
| ERROR_SERVICEPROGRAMCALL_INIT_CHECK_NULL.errorCode=530002
The program object is null. |
errorRole | BW-Plug-in | The object that the CallServiceProgram activity operates on is null. | Check the service program object. |
| ERROR_READQUEUE_INIT_CHECK.errorCode=540001
The format of program object is invalid. |
errorRole | BW-Plug-in | The format of the data queue that the ReadQueue activity operates on is invalid. | Check the data queue format. |
| ERROR_READQUEUE_INIT_CHECK_NULL.errorCode=540002
The program object is null. |
errorRole | BW-Plug-in | The data queue that the ReadQueue activity operates on is null. | Check the data queue. |
| ERROR_WRITEQUEUE_INIT_CHECK.errorCode=550001
The format of program object is invalid. |
errorRole | BW-Plug-in | The format of the data queue that the WriteQueue activity operates on is invalid. | Check the data queue format. |
| ERROR_WRITEQUEUE_INIT_CHECK_NULL.errorCode=550002
The program object is null. |
errorRole | BW-Plug-in | The data queue that the WriteQueue activity operates on is null. | Check the data queue. |
| ERROR_MONITOR_START_FAILED.errorCode=560001
Event source starting is failed, details:{0} |
errorRole | BW-Plug-in | The QueueReceiver activity failed to start. | Depends on the content of the error message. |
| ERROR_MONITOR_STOP_FAILED.errorCode=560002
Event source stopping is failed, details:{0} |
errorRole | BW-Plug-in | The QueueReceiver activity failed to stop. | Depends on the content of the error message. |
| ERROR_MONITOR_PROCESS_DATA_FAILED.errorCode=560003
Error happened when process the posted data, details:{0} |
errorRole | BW-Plug-in | An error occurred while QueueReceiver activity was running. | Depends on the content of the error message. |
| ERROR_MONITOR_INIT_CHECK.errorCode=560004
The format of data queue is invalid. |
errorRole | BW-Plug-in | The format of the data queue that the QueueReceiver activity is monitoring is invalid. | Check the data queue format. |
| ERROR_MONITOR_INIT_CHECK_NULL.errorCode=560005
The data queue is null. |
errorRole | BW-Plug-in | The data queue that you want to monitor is null. | Check the data queue |
| ERROR_READMESSAGEQUEUE_INIT_CHECK.errorCode=580004
The format of data queue is invalid. |
errorRole | BW-Plug-in | The format of the message queue is invalid. | Check the message queue format. |
| ERROR_READMESSAGEQUEUE_INIT_CHECK_NULL.errorCode=580005
The data queue is null. |
errorRole | BW-Plug-in | The message queue is null. | Check the message queue. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorcode=140003 The queue name is invalid. |
errorRole | BW-Plug-in | The queue object is invalid. | Correct the queue object specification. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=140004 The queue name is null. |
errorRole | BW-Plug-in | The queue object is null. | Correct the queue object specification. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=340004 Error; the specified search type [{0}] is not one of the allowed values: EQ, NE, LT, LE, GT, GE. |
errorRole | BW-Plug-in | The search type specification is not one of the allowed values. | Correct the search type specification and retry. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=390002 {0} has no input! |
errorRole | BW-Plug-in | No input was provided for the activity. | Rebuild the workspace and ensure that the activity is correctly mapped. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=500001 Internal exception [{0}] Please inform product support immediately. |
errorRole | BW-Plug-in | Internal product problem. | Contact support. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=520001 The format of the program object is invalid. |
errorRole | BW-Plug-in | The format of the program object is not valid. | Correct the specification of the program object. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=520002 The program object is null. |
errorRole | BW-Plug-in | The program object is null. | Specify a valid program object. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=520003 The program call returned an exception with message [{0}]. |
errorRole | BW-Plug-in | The program call returned an exception with message [{0}]. | Use the provided message to resolve the error. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=530001 The format of the program object is invalid. |
errorRole | BW-Plug-in | The program object is null or otherwise invalid. | Correct the program object specification. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=530002 The program object is null. |
errorRole | BW-Plug-in | The program object is null. | Correct the program object specification. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=560001 Event source startup failed for reason: {0} |
errorRole | BW-Plug-in | The event source startup failed. | If the condition persists, use the provided message to resolve the issue. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=560002 Event source shutdown has failed for reason: {0} |
errorRole | BW-Plug-in | The event source shutdown failed. | If the condition persists, use the provided message to resolve the issue. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=560003 Error during post processing of the queue data: {0} |
errorRole | BW-Plug-in | An error was encountered while parsing the received message into XML for the event. This message is lost. | Correct the condition indicated by the message to prevent further message loss. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=560004 The format of the data queue name is invalid. Must be LIB/QUEUE. |
errorRole | BW-Plug-in | The format of the data queue name is invalid. It must be LIB/QUEUE. | Correct the data queue specification as per documentation. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=560005 The data queue is null. |
errorRole | BW-Plug-in | The data queue name is mandatory. | Update the activity config. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=560006 The data queue [{0}] could not be opened. |
errorRole | BW-Plug-in | There was an error initializing the monitor. Failed to open the queue. | Confirm that the queue exists and is accessible. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=560007 JT400 API call being interrupted because it appears to be blocked indefinitely. |
errorRole | BW-Plug-in | The read API call was blocked for an unreasonable length of time and has been interrupted. | This usually indicates a connection or host problem. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=570001 The IBMi type {0} is not supported! |
errorRole | BW-Plug-in | Data type is not supported. | Use one of the supported data types. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=580004 The format of the data queue is invalid. Must be LIB/QUEUE. |
errorRole | BW-Plug-in | The format of the data queue name is invalid. It must be LIB/QUEUE. | Specify a correct queue name. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=580005 The data queue is null. |
errorRole | BW-Plug-in | The data queue is null. | Specify a correct queue name. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=590002 IOException occurred while retrieving XML Output for activity [{0}] |
errorRole | BW-Plug-in | IOException occurred while retrieving XML Output for activity [{0}]. The input or output schemas for the activity are out of sync. | Examine the messages in the console to determine the problem. It may be necessary to rerun the activity in debug mode. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=590002 Required parameter [{0}] not provided. |
errorRole | BW-Plug-in | The required parameter [{0}] is not provided. | Provide the named parameter. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=590003 Job not found for reason: [{0}] |
errorRole | BW-Plug-in | Job not found for reason: [{0}] | The job does not exist. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=590004 Exception occurred while executing the activity [{0}] |
errorRole | BW-Plug-in | Exception occurred while executing the activity [{0}]. | There should be an embedded exception to diagnose. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=590004 Error searching for job: [{0}] |
errorRole | BW-Plug-in | The job was not found. | Use the reason provided to resolve the issue. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=590005 The object of activity {0} does not exist. The detailed message is {1}. |
errorRole | BW-Plug-in | The object of activity {0} does not exist. The detailed message is {1}. |
This generic message occurs when the program, file, or queue does not exist on the host. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=590006 The IBMi API object {0} returned an error. The detailed message is {1}. |
errorRole | BW-Plug-in | This generic message occurs when reporting an IBMi API failure. | Examine the embedded exception for more information. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=590007 An error occurred while communicating with the IBMi server when running the activity: {0}.The detailed message is {1}. |
errorRole | BW-Plug-in | An error occurred while communicating with the IBMi server when running the activity: {0}.The detailed message is {1}. | This generic message occurs when an IO error occurs when communicating with the host. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=590008 A security or authority error occurred while communicating with the IBMi server. The detailed message is {0}. |
errorRole | BW-Plug-in | A security or authority error occurred while communicating with the IBMi server. The detailed message is {0}. |
This generic message occurs when a security error occurs when communicating with the host. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=590009 The following error occurred when running the activity: {0}. |
errorRole | BW-Plug-in | This is a generic runtime message is issued when the activity times out. It is likely that the timeout for the activity is longer than the engine timeout for the process and the engine has terminated the activity. | Shorten the timeout for the activity and determine why it hangs. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=590010 Error occurred when monitor activity [{0}] attempted to create a connection: [{1}] |
errorRole | BW-Plug-in | The Monitor task was unable to connect to the host upon start up. | The monitor activity will retry indefinitely. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=5900012 Error; Failed to get a connection from the connection factory. |
errorRole | BW-Plug-in | A failure occurred when getting a pooled connection. | The source of the connection problem with the host should be determined. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=5900014 The first field in the schema is not a key field which is necessary for processing a KeyedDataQueue. |
errorRole | BW-Plug-in | The first field in the schema is not a key field which is necessary for processing a KeyedDataQueue. | When working with a keyed data queue the first field in the schema must be named "key" and must conform to the key length of the queue. |
| ERROR_TIBCO_BW_PALETTE_AS400
errorCode=5900015 JTOpen AS400Exception: message [{0}] |
errorRole | BW-Plug-in | A generic AS400 exception occurred. | Use the included message to diagnose the problem. |