OSF DCE Problem Determination Guide

Error Messages and Status Codes
procedure call made to a different server instance than the one originally associated with
the binding handle results in the remote procedure call failing with this status code.
An application may also see this status code returned from the
rpc_mgmt_ep_elt_inq_begin routine. In this case, the endpoint map service rebooted
during the lifetime of the inquiry context.
Action: For the case of a failed remote procedure call, the client can call
rpc_binding_reset for communications with the new server instance to succeed.
For inquiring endpoint map elements, call rpc_mgmt_ep_elt_inq_done to delete the
failed inquiry context. Next, restart the inquiry by calling rpc_mgmt_ep_elt_inq_begin.
0x16c9a065 rpc_s_wrong_kind_of_binding
Severity: Varies Component: rpc
Text: Wrong kind of binding
Explanation: An application specified a client (server) binding handle as input to an RPC
runtime routine that expects a server (client) binding handle.
Action: Change the application to use the correct kind of binding handle.
0x16c9a10e rpc_s_wrong_pickle_type
Severity: Varies Component: rpc
Text: Wrong type of pickle passed to unpickling routine
Explanation: Pickles are typed with a UUID. Unpickling routines are specific to a single
type of pickle. If an unpickling routine is passed a pickle containing the wrong type
UUID it will return this status code.
Action: Use the correct pickling routine or the correct type of pickle.
0x17122ee3 rsdb_journal_cant_init_list
Severity: Fatal Component: sec / sec_s_rs_rsdb
Text: Could not initialize journal list
Explanation: ?
Action: ?
0x17122ee4 rsdb_journal_cant_open
Severity: Fatal Component: sec / sec_s_rs_rsdb
Text: Unable to open registry journal file
Explanation: ?
Action: ?
124330 Tandem Computers Incorporated 2−543