OSF DCE Problem Determination Guide

security processing. In this case the sender of a remote procedure call requested the

receiver to use an algorithm that the receiver (the server system) does not support.

Action: This may be an attempt to violate system security.

0x16c9a0a6 rpc_s_unsupported_name_syntax

Severity: Varies Component: rpc

Text: Unsupported name syntax

Explanation: The value speciﬁed for the entry name syntax was valid, but not supported.

Action: Check the value provided and use one of the supported API deﬁned constants

rpc_c_ns_syntax_*.

0x16c9a0e0 rpc_s_unsupported_protect_level

Severity: Varies Component: rpc

Text: Requested protection level is not supported

Explanation: The value for the protection level supplied to rpc_binding_set_auth_info

is unsupported.

Action: Change the application to use a supported value.

0x16c9a02d rpc_s_unsupported_type

Severity: Varies Component: rpc

Text: Unsupported type

Explanation: A client application tried to make a remote call using a binding handle

whose associated object UUID has a type that is unsupported for the interface being used.

Action: Either the client established a binding with an inappropriate server (and the client

should rebind to another server), or an application error exists.

0x16c9a05f rpc_s_who_are_you_failed

Severity: Varies Component: rpc

Text: Who are you failed

Explanation: An internal error occurred.

Action: Report the error to your vendor.

0x16c9a006 rpc_s_wrong_boot_time

Severity: Varies Component: rpc

Text: Wrong boot time

Explanation: A binding handle that is successfully used to make a remote procedure call

using the ncadg RPC protocol will be bound to that server instance (identiﬁed by

remembering the server’s boot (startup) time in the binding handle). An ncadg remote

2− 542 Tandem Computers Incorporated 124330