Table of Contents
Advertisement
8.8.8 RPC error messages
No.
Error message
1
Line error (A signal was received.)
2
Line error (A timeout error occurred.)
3
Line error (The RPC server does not
exist.)
4
Line error (The RPC server is
disconnected.)
5
Line error (The connection is reset.)
6
Line error (The RPC server is closed.)
7
Line error (A timeout error occurred during inter-PU
communication. Check the status of each PU, and
then retry operation.)
8
Line error (The line port is busy. Wait until the use
by other users ends, and then retry operation.)
9
Line error (An invalid socket was specified.)
10
Line error (Failed to generate a socket.)
11
Line error (Failed to allocate the memory.)
12
Line error (The network is disconnected.)
13
Line error (The network connection interface is
down.)
14
Line error (Failed to load the port number.)
15
Line error (Failed to load the IP address.)
16
Line error (Failed to attach the shared memory.)
17
Line error (A fatal error occurred.)
18
Line error (RPC library error (rc=%d))
#: Interpreting rc values in RPC library errors:
23: There is no function corresponding to CPMS.
Other value: The Windows socket error code output by the WSAGetLastError function of the Windows API.
Table 8-47 RPC error messages
If there is no issue with the communication paths, contact
the system administrator.
If there is no issue with the communication paths, contact
the system administrator.
If there is no issue with the communication paths, contact
the system administrator.
If there is no issue with the communication paths, contact
the system administrator.
If there is no issue with the communication paths, contact
the system administrator.
If there is no issue with the communication paths, contact
the system administrator.
If there is no issue with the communication paths, contact
the system administrator.
Wait until the other user has finished using the line port,
and then perform the operation again.
If there is no issue with the communication paths, contact
the system administrator.
If there is no issue with the communication paths, contact
the system administrator.
If there is no issue with the communication paths, contact
the system administrator.
If there is no issue with the communication paths, contact
the system administrator.
If there is no issue with the communication paths, contact
the system administrator.
If there is no issue with the communication paths, contact
the system administrator.
If there is no issue with the communication paths, contact
the system administrator.
If there is no issue with the communication paths, contact
the system administrator.
If there is no issue with the communication paths, contact
the system administrator.
If there are no issues with the CPMS and RPDP versions or
the communication paths, contact the system
administrator
8-163
Action to take
#
.
8. Tools
Advertisement
Table of Contents
Troubleshooting
