When the sender adapter detects an error situation it returns an RPC message to the RPC client application. All errors returned by the adapter use message class 3000.
The messages have the format:
3000nnnn
where | 3000 | is the message class, and |
nnnn | is the message number in the range 0000 - 9999. |
30000001 | 30000002 | 30000003 | 30000004 | 30000005 | 30000006 | 30000007 | 30000008 | 30000009 | 30000010 | 30000011 | 30000012 | 30000013 | 30000014 | 30000015
30000001 | Processing RPC request from client failed |
Explanation |
During the processing of the RPC request from a client an exception occurred. The message text is the text of the exception. |
Action |
Check the error message for details. Typical situations are
|
30000002 | Listening for an RPC request from client failed |
Explanation |
An exception occurred while the adapter was waiting for an RPC request or while it was analyzing a request received from a client. The message text is the text of the exception. |
Action |
Check the error message for details. |
30000003 | Multiple channels configured for program |
Explanation |
There are multiple specific channel configurations for the same program name in PI. |
Action |
Correct the channel configurations in PI. |
30000004 | Multiple generic channels configured |
Explanation |
There are multiple generic channel configurations ( |
Action |
Correct the channel configurations in PI. |
30000005 | No channel configuration found for program |
Explanation |
No channel configuration can be found for the program name specified in the RPC client request. |
Action |
Correct the RPC client application or specify a channel configuration in PI for this program. |
30000006 | XMM file of channel channel has no definition for program |
Explanation |
A generic channel configuration is available but the XMM file does not contain an entry for the program name specified in the RPC client request. |
Action |
Correct the RPC client application or the channel configuration in PI. |
30000007 | Unknown RPC server command cmd |
Explanation |
The adapter received an unknown server command from the RPC client. |
Action |
Check the RPC client. |
30000008 | Invalid RPC call with type type |
Explanation |
The adapter received a request type from the RPC client. |
Action |
Check the RPC client. |
30000009 | Conversational RPC not possible |
Explanation |
The adapter received a conversational RPC request type from the client. The adapter does not support conversational RPC. |
Action |
Correct your RPC client application so that it does not use conversational RPC. |
30000010 | Program programName in lib libraryName cannot be used with QoS qos |
Explanation |
The adapter received an RPC request type from the client which contained
|
Action |
Correct your RPC client application so that it uses only |
30000011 | Duplicate Sender Agreement for program/interface programName found |
Explanation |
More than one Sender Agreement has been found with the same interface name for the mentioned program. |
Action |
Change the Sender Agreements so that only one Sender Agreement with the same interface name exists for every Communication Channel. |
30000012 | No Sender Agreement for program/interface programName found |
Explanation |
No Sender Agreement has been found for the mentioned program. |
Action |
If the parameter |
30000013 | First parameter has incorrect format for external Message ID: message |
Explanation |
The parameter |
Action |
Correct the definition of the first parameter or deselect the parameter in the Communication Channel. |
30000014 | Program programName in lib libraryName cannot be used with Reliable RPC |
Explanation |
The RPC client is sending a Reliable RPC call to a Communication Channel which is using "EntireX RPC" as the message protocol. |
Action |
Either change the client so it uses standard RPC, or set the message protocol in the Communication Channel to "EntireX Reliable RPC". |
30000015 | Program programName in lib libraryName can only be used with Reliable RPC |
Explanation |
The RPC client is sending a standard RPC call to a Communication Channel which is using "EntireX Reliable RPC" as the message protocol. |
Action |
Either change the client so it uses Reliable RPC, or set the message protocol in the Communication Channel to "EntireX RPC". |