This message class contains messages that can occur with ApplinX Connections in the EntireX Adapter. The messages have the format:
2023nnnn
where | 2023 | is the message class, and |
nnnn | is the message number in the range 0000 - 9999 |
20230001 | 20230009 | 20230010 | 20230011 | 20230012 | 20230013 | 20230015 | 20230022
20230001 | Process request and reply: illegal action <number indicating action>. |
Explanation |
During request/reply processing the next action is illegal in the current state. |
Action |
Contact Software AG support. |
20230009 | <Exception with detailed message > |
Explanation |
An exception occurred while formatting the message. In most cases, the reason is an inconsistency in metadata. |
Action |
See detailed message or contact Software AG support. |
20230010 | Compression=off not possible |
Explanation |
An RPC with compression "0" ("off") is not supported. |
Action |
Change compression to 1 or 2. |
20230011 | Type of marshalling not allowed |
Explanation |
For the |
Action |
Check configuration and client. |
20230012 | <Exception with detailed message> |
Explanation |
This exception occurs in message processing. |
Action |
See detailed message and contact Software AG support. |
20230013 | Preparing message failed, see log for details
or Message received from server does not fit buffer |
Explanation |
There are two possible reasons for this error code:
|
Action |
Check metadata (IDL, SVM, adapter connections) for consistency or contact Software AG support. |
20230015 | Transformation error on request: <Exception with detailed message>. |
Explanation |
This data type is not supported. |
Action |
See detailed message or contact Software AG support. |
20230022 | Unsupported command <command>.
or Exception: <Exception with detailed message> |
Explanation |
There are two possible reasons for this error code:
|
Action |
See detailed message and log files or contact Software AG support. |