Windows error 1714 (RPC_S_NO_PROTSEQS

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: The RPC server has not registered any protocol sequence on which it can receive calls.

Previous	Next
RPC_S_ALREADY_LISTENING	RPC_S_NOT_LISTENING

RPC_S_NO_PROTSEQS_REGISTERED

A registered interface is not enough to make a server reachable

RPC_S_NO_PROTSEQS_REGISTERED means the server runtime has no registered protocol sequences for receiving RPC traffic. RPC interface registration defines what procedures the server exposes; protocol-sequence registration defines how calls can arrive, for example over ncacn_ip_tcp, ncacn_np, or ncalrpc.

A server can therefore have a valid interface specification and still have no usable bindings to publish or register with the endpoint mapper.

What to inspect

Confirm that startup called one of the RpcServerUseProtseq* or RpcServerUseAllProtseqs* functions before inquiring about bindings or publishing endpoints.
Check the return status of protocol-sequence setup; do not ignore an earlier unsupported or invalid protocol-sequence error.
Use RpcNetworkInqProtseqs when code must discover transports supported by both the runtime and operating system.

Starting RpcServerListen cannot compensate for a server that registered no transport. Fix initialization order and the earlier protocol-sequence status first.

References

Looking for a different code? Search another status or error code.