The response codes returned by the methods used by the LINCEnvironment, TransactionManager, IspecFrameModel, and IspecModel objects are listed in ResponseCodes in the Agile Business Suite Component Enabler Class Reference Summary.
The main response codes are listed in the following table.
| Response Code | Value | Methods | Description |
|---|---|---|---|
| OK | 100 | all | The operation completed successfully. |
| OK_LOGIN | 101 | connect | The connect was successful, but the client is required to login. |
| OK_SECURE_LOGIN | 102 | connect | The connect was successful, but the client is required to complete a secure login. |
OK_MORE_LOGIN_INFO | 103 | login | The login has succeeded to this stage, but the server requires more information to complete the login. Another login is required. |
ERR_NO_SUCH_SYSTEM | 201 | login, connect | The system name is not known. |
ERR_CANT START_ SYSTEM | 202 | login, connect | The server could not start the system. |
ERR_SYSTEM_NOT_ RESPONDING | 203 | login, connect | The system is not responding. |
ERR_ACCESS_DENIED | 204 | login | The login id and password you used were not valid for the system. |
ERR_ACCESS_DENIED_ CLOSING | 205 | login | The login id and password you used were not valid for the system. The session is being closed. |
ERR_PROTOCOL_VERSION | 206 | connect | The protocol version is not valid. |
ERR_INCORRECT_VIEW | 207 | VIEW definition on the MCP Runtime Host is incorrect. | |
ERR_CANT_CHANGE_ LANG | 301 | The language you specified is incorrect. | |
ERR_PROTOCOL | 302 | login, connect, hello, simpleTransaction, transaction, loadIspec | The server detected a protocol error. |
ERR_SERVER | 303 | login, connect, hello, simpleTransaction, transaction, loadIspec | An error was detected by the server. |
OK_TRANSACTION_HAD_ ERRORS | 801 | simpleTransaction, transaction, hello, loadIspec | The transaction succeeded, but there were some errors. Check your LINCStatus object. |
OK_BYE | 802 | simpleTransaction(), transaction() | The transaction completed and the server returned a BYE. |
ERR_EXCEPTION | 901 | all | An exception occurred when processing the transaction. |
ERR_FATAL_EXCEPTION | 902 | all | A fatal exception occurred when processing the transaction. |
ERR_CLIENT_PROTOCOL | 903 | login, connect, hello, simpleTransaction, transaction | The client encountered a protocol error talking to the server. |
ERR_CANT_CONNECT | 904 | connect | The client could not connect to the server. |
ERR_TRANSPORT | 905 | login, connect, hello, simpleTransaction, transaction, close | A communication error occurred. |
ERR_TIMED_OUT | 906 | login, connect, hello, simpleTransaction, transaction, close | The client timed out while waiting for the server to respond to a message. |
ERR_TRANSACTION_ FAILED | 911 | simpleTransaction, transaction | The transaction failed. Check your LINCStatus object for error messages. |
ERR_TRANSACTION_ VETOED | 912 | simpleTransaction, transaction | The transaction was vetoed by a transaction listener. |
ERR_APPLICATION_ CHANGED | 913 | simpleTransaction, transaction | The Ispec that sent in the transaction is from a different application from the one to which you are currently connected. |
ERR_CANT_LOAD_ISPEC | 921 | loadIspec, transaction | The Ispec specified in loadIspec or sent by the transaction could not be loaded. |
ERR_ISPEC_VERSION | 925 | loadIspec, transaction | The data class for the Ispec does not match the version on the host. |
ERR_PROPERTY_CHANGE_ VETOED | 931 | setFieldValue | An attempt to set a field in an IspecModel was vetoed by a VetoableChangeListener. |
ERR_NO_SUCH_FIELD | 932 | setFieldValue | An attempt to set an IspecModel field failed because the field does not exist. |
ERR_BAD_FIELD | 933 | setFieldValue | An attempt to set an IspecModel field failed because the new value is bad. |
Error codes in the range 100 – 399 are generated from errors detected by the server. Error codes in the range 800 – 999 are generated internally by the client.