This document describes possible error codes that appear in the E1ROOT_*.LOG or JDEROOT_*.LOG files in Tools Releases 8.96 and below for JAS.
For example:
CallObjectSystemException
Errors are defined as below:
| Message | Error Code | Error Detail |
|---|---|---|
| UNKNOWN | -1 | Unknown error code: "+errorCode |
| NOERROR | 0 | |
| SYS_ERROR_START_NUM | 90 | |
| GENERIC_ERROR | 99 | Generic (unknown) error. Please see Enterprise Server log for details |
| GETPROCADDRESS_FAILED | 98 | GetProcAddress failed. Please see Enterprise Server log for details. Business function cannot be found |
| LOADLIB_FAILED | 97 | LoadLib failed.Please see Enterprise Server log for details. Library in which business funtion resides cannot be loaded |
| TIMEOUT | 1000 | (COSE#1000) Request timeout |
| ALREADY_EXECUTED | 1001 |
(COSE#1001) The requested object has already been executed |
| CONN_FAILED | 1002 | (COSE#1002) Connection failed |
| HOST_NOT_FOUND | 1003 | (COSE#1003) Host not found |
| IO_FAILED | 1004 | (COSE#1004) I/O Failed |
| FAILOVER | 1005 | (COSE#1005) Original server has gone down, a failover is needed however there is either a cache or a manual commit transaction is in progress |
| TM_TRAN_CANCELLED | 1006 | (COSE#1006) TM_TRAN_CANCELLED was received from CallObject |
| SERVER_DOWN | 1007 | (COSE#1007) Unable to execute request because the primary server is down and either there is no secondary server defined, or secondary server is also down |
| RETRY_NEEDED | 1008 | (COSE#1008) Server problem. The server may still be available, but because of the state of information, the entire unit-of-work must be resubmitted |
| BSFN_PROBLEM | 1009 | (COSE#1009) The business function being executed is causing a problem |
| REMOTE_ENV_INIT_FAILED | 1010 | (COSE#1010) Remote environment initilization failed. Please see Enterprise Server log for details, environment may not be supported by server |
| REMOTE_USER_INIT_FAILED | 1011 | (COSE#1011) Remote user initilization failed. Please see Enterprise Server log for details |
| BAD_ERRORPACKETS | 1012 | (COSE#1012) Bad error packet structure returned from CallObject |
| HANDLE_INVALID | 1013 | (COSE#1013) User handle invalid |
| OCM_LOOKUP_FAILED | 1014 | (COSE#1014) OCM lookup failed |
| CONN_CLOSED | 1015 | (COSE#1015) Connection closed by server. Please see Enterprise Server log for details |
| MSG_NOT_SUPPORTED | 1016 | (COSE#1016) Message type not recognized by server Please see Enterprise Server log for details |
| ASSOC_KERNEL_NOT_FOUND | 1017 | (COSE#1017) Associated kernel not found. Please see Enterprise Server log for details |
Syntax to describe the error is:
For example: COSE#1000 TIMEOUT Request timeout
| Error Message | Action |
|---|---|
| LOADLIB_FAILED | When it fails to Load Parent Library which called BSFN belongs to. |
| GETPROCADDRESS_FAILED | Library is loaded but it is not able to find the address (compilation issue). |
| TM_TRAN_CANCELLED | Transaction itself is canceled most probably because Row Security is preventing a user from updating/adding data from/into a certain table(s). |
For this type of error, a retry does not take place. Rather, JAS just issues an error and stops processing.
In general, the errors below will come when a certain Business Function is called with 'Transaction Processing' ON (MANUAL Commit) and it was called Asynchronously across E1 Distribution Module.
| Error | Cause/Debug |
|---|---|
| TIMEOUT | Unless issue is specific to transaction volume timeout error will come when a called BSFN (xxxEndDoc or its sub-routine) falls into zombie(caused by memory error) or locking(including deadlock) so analyze jdedebug.log (call object kernel log) |
| TM_TRAN_CANCELLED | This error will come when Transaction Processing is on and when it fails to commit cache to Table(s). Usually jde.log in logic server will contain Primary Key Constraint or Row Security Violation message. So check jdedebug.log for further detail |
| RETRY_NEEDED | Most of call object kernel error will call this error message. Consider this rather informational as most of case (unless error is specific to a certain data set) error may be repeated |
| ASSOC_KERNEL_NOT_FOUND | Common cause of this error is when a certain call object kernel falls into zombie before it reaches return(); so it failed to return to called routine(event rule) |