| Previous | Next |
| RPC_NT_ALREADY_LISTENING | RPC_NT_NOT_LISTENING |
RPC_NT_NO_PROTSEQS_REGISTERED
RPC_NT_NO_PROTSEQS_REGISTERED is an NTSTATUS value used by the Windows RPC runtime. A server must register at least one protocol sequence before it can receive RPC calls. This status says the runtime has no such registration at the point where listening is requested or required. It describes the server configuration state before a remote client can be served.
It differs from RPC_NT_PROTSEQ_NOT_SUPPORTED, where a requested transport is valid but unavailable on the host, and from RPC_NT_NO_PROTSEQS, which can describe an empty set supplied to a particular operation rather than the server listener state.
The server listener has no registered transport to activate
- Verify that protocol-sequence registration succeeds before listener startup and that its error is not discarded.
- Record the intended endpoint and transport for each server interface, not just the final listener call.
- Check startup ordering in services that conditionally enable transports after configuration or policy is loaded.
References
Looking for a different code? Search another status or error code.