OSF DCE Problem Determination Guide

Error Messages and Status Codes
receive remote calls.
Action: Make sure the underlying network transport service is working. Try a non-RPC
application that uses this service (for example, file transfer or remote login).
0x16c9a05c rpc_s_cant_get_if_id
Severity: Varies Component: rpc
Text: Cannot get interface ID
Explanation: The RPC runtime tried to get information about a communications socket
but failed due to an underlying network transport service problem.
Action: Make sure the underlying network transport service is working. Try a non-RPC
application that uses this service (for example, file transfer or remote login).
0x16c9a05b rpc_s_cant_getpeername
Severity: Varies Component: rpc
Text: Cannot get peer name
Explanation: There was a failed attempt to get the network address of the other end of
the connection. If the client-server connection is closed, an executing manager routine
that calls either rpc_binding_to_string_binding or rpc_binding_server_from_client
may receive this status. Both routines require connection information that is no longer
available. This status can occur if the executing remote procedure was specified with the
IDL maybe attribute, or if the remote procedure call has been orphaned.
Action: The getpeername routine returns the name of the peer connected to a particular
socket. See the getpeername(2) for more information. In the case of an orphaned call the
client can try to reissue the call.
0x16c9a029 rpc_s_cant_inq_socket
Severity: Varies Component: rpc
Text: Cannot inquire socket
Explanation: The RPC runtime tried to get information about a communications socket
but failed due to an underlying network transport service problem.
Action: Make sure the underlying network transport service is working. Try a non-RPC
application that uses this service (for example, file transfer or remote login).
0x16c9a104 rpc_s_class_version_mismatch
Severity: Varies Component: rpc
Text: RPC class version mismatch
Explanation: The application attempted to read or modify a name service entry with an
incompatible RPC class version. For example, a V1.0 client tried to read a name service
entry with a V2.0 version. Only major version incompatibilities are flagged.
124330 Tandem Computers Incorporated 2−509