This message class contains messages that can occur with Direct RPC. The messages have the format:
0400nnnn
| where | 0400 | is the message class, and |
| nnnn | is the message number in the range 0000 - 9999 |
04000001 | 4000002 | 04000003 | 04000004 | 04000005 | 04000006 | 04000007 | 04000008 | 04000009 | 04000010 | 04000011 | 04000012 | 04000013 | 04000014 | 04000015 | 04000017 | 04000018 | 04000019 | 04000020 | 04000021 | 04001000 | 04001001| 04000001 | Exception during processing call: <exception text> |
| Explanation |
An unexpected error occurred during processing of a call from an RPC client or server. |
| Action |
Check the exception text for details. |
| 4000002 | Transport session not active |
| Explanation |
A call happens on an adapter connection although this connection instance is disabled. |
| Action |
Contact Software AG support. |
| 04000003 | Invalid usage of Direct RPC (<class/server/service>) |
| Explanation |
An RPC client sends a request to an RPC server using Direct RPC. This is not supported. |
| Action |
Change your application setup so that
|
| 04000004 | Invalid register: replicate from different transport (<class/server/service>) |
| Explanation |
Both a listener and an RPC server try to register using the same
|
| Action |
Change your application so that only listeners or RPC servers register
for the same |
| 04000005 | Send with wait not possible for servers (<class/server/service>) |
| Explanation |
An RPC server issues a synchronous send command, which is not supported. |
| Action |
Check your configuration: for example, an ACI server might be using Direct RPC. |
| 04000006 | Send with no wait not possible for clients (<class/server/service>) |
| Explanation |
An RPC client issues an asynchronous send command, which is not supported. |
| Action |
Check your configuration: for example, an ACI client might be using Direct RPC. |
| 04000007 | Receive not possible for clients (<class/server/service>) |
| Explanation |
An RPC client issues a receive command, which is not supported. |
| Action |
Check your configuration: for example, an ACI client might be using Direct RPC. |
| 04000008 | Direct RPC not started |
| Explanation |
An adapter service or a listener issues a call using Direct RPC, but the Direct RPC component is not started. |
| Action |
Start the Direct RPC component, or ignore error if stopping of Direct RPC is intended. |
| 04000009 | Information Service error: <detailed message> |
| Explanation |
An error occurred while processing an Information Service request. |
| Action |
See error message for details. |
| 04000010 | Command Service error: <detailed message> |
| Explanation |
An error occurred while processing a Command Service request. |
| Action |
See error message for details. |
| 04000011 | Compression not supported |
| Explanation |
The compression feature is not supported. |
| Action |
Disable compression (use value
" |
| 04000012 | Publish and Subscribe not supported |
| Explanation |
The Publish and Subscribe functionality is not supported. |
| Action |
Change your application. |
| 04000013 | Character set for <character set type> not available |
| Explanation |
No character set is available for an RPC call. |
| Action |
Contact Software AG support. |
| 04000014 | Encoding LS=<char set name> not supported |
| Explanation |
The specified character set is not available. Only character sets supported by the Java JVM can be used. |
| Action |
Change the configuration of the RPC client or server. |
| 04000015 | <error message> |
| Explanation |
An error during character set conversion. |
| Action |
See error message for details. |
| 04000017 | Send with wait not possible for UOWs (<service>) |
| Explanation |
UOWs can be sent only asynchronously. |
| Action |
Check your configuration: for example, an ACI server might be using Direct RPC. |
| 04000018 | Unable to load/store SCM conversation data: <detailed message> |
| Explanation |
An error occurred while loading or storing conversation data. |
| Action |
See error message for details. |
| 04000019 | Invalid usage of convid: <detailed message> |
| Explanation |
A conversation ID has been used in an invalid context. |
| Action |
See error message for details. |
| 04000020 | No listener enabled for <service> |
| Explanation |
Either no listener exists or is not enabled for the specified service. |
| Action |
Create or enable a listener for this service or use a different service. |
| 04000021 | UOW Processor not available |
| Explanation |
Commit of a UOW fails. |
| Action |
Contact Software AG. |
| 04001000 | Notification not processed |
| Explanation |
Processing the notification in the Integration Server fails. |
| Action |
Check the server log for errors. |
| 04001001 | Notification processing cancelled: <detailed message> |
| Explanation |
Processing the notification in the Integration Server has been cancelled. |
| Action |
See error message for details. |