OSF DCE Problem Determination Guide

0x16c9a159 rpc_m_unk_ifspec

Severity: Varies Component: rpc

Text: (%s) Unknown interface spec version

Explanation: An internal error occurred.

Action: Report the error to your vendor.

0x16c9a15f rpc_m_unk_sock_type

Severity: Varies Component: rpc

Text: (%s) Unknown socket type

Explanation: The socket corresponding to a ﬁle descriptor is of an unknown type.

Action: Report the error to your vendor.

0x16c9a14d rpc_m_unsupp_stub_rtl_if

Severity: Varies Component: rpc

Text: (%s) Unsupported stub/RTL IF version

Explanation: An internal error occurred.

Action: Report the error to your vendor.

0x16c9a04a rpc_s_access_control_info_inv

Severity: Varies Component: rpc

Text: Access control information invalid at remote host

Explanation: The client may have attempted to connect to a server at a protected address

for which the client lacks the required permissions. If the client is attempting to connect

to a server using the ncacn_dnet_nsp protocol sequence using a well known endpoint or

a fully speciﬁed string binding, there are three possible reasons for this status:

The server is not running

The server is not listening for client connects over the ncacn_dnet_nsp protocol

sequence.

The server is not listening for client connects on the endpoint speciﬁed by the client.

Action: In general, you should modify the access controls on the speciﬁed address to

allow the client access. If the client is attempting to communicate with a server using the

ncacn_dnet_nsp protocol sequence with a well-known or explicitly speciﬁed endpoint,

do the following:

Verify at the server node that the server application has been started and is listening over

the ncacn_dnet_nsp protocol sequence.

Verify that the client has speciﬁed the correct server endpoint.

2− 500 Tandem Computers Incorporated 124330