OSF DCE Problem Determination Guide

Explanation: An application manager routine tried to inquire about authentication

information from a client binding handle but the client did not establish any

authentication on the call.

Action: The manager routine can either ignore the error or refuse to execute the call. The

application writer can change the client to use authentication.

0x16c9a0fb rpc_s_binding_incomplete

Severity: Varies Component: rpc

Text: Binding incomplete (no object ID and no endpoint)

Explanation: The speciﬁed server binding information was insufﬁcient. In a local or

remote management call to the RPC runtime, the client-supplied binding information

lacked an endpoint and an associated object UUID.

Action: Supply complete binding information and an object UUID to local or remote

management calls.

0x16c9a0b9 rpc_s_binding_vector_full

Severity: Varies Component: rpc

Text: Binding vector full

Explanation: An internal status code.

Action: None required.

0x16c9a031 rpc_s_call_cancelled

Severity: Varies Component: rpc

Text: Call canceled

Explanation: A cancel was posted to a thread making a remote call. This error condition

occurs at the server but is usually not seen by the server application.

Action: None required.

0x16c9a014 rpc_s_call_faulted

Severity: Varies Component: rpc

Text: Call faulted

Explanation: The execution of an application manager routine raised a fault (exception),

for example, division by zero. Applications usually do not see this error as it is

intercepted by the client stub and transformed into the speciﬁc error condition that occurs

in the application manager routine.

Action: None required.

0x16c9a0e4 rpc_s_call_id_not_found

2− 506 Tandem Computers Incorporated 124330