| Previous | Next |
| RPC_NT_NO_BINDINGS | RPC_NT_CANT_CREATE_ENDPOINT |
RPC_NT_NO_PROTSEQS
RPC_NT_NO_PROTSEQS is an NTSTATUS value used by the Windows RPC runtime. This status means the relevant RPC context contains no protocol sequence. A protocol sequence is the transport selection that gives meaning to the network address and endpoint, so an empty sequence set prevents the runtime from constructing or using a transport binding.
Do not confuse it with RPC_NT_NO_PROTSEQS_REGISTERED. That code specifically describes the server listener lacking registered sequences; this one is used for a context in which there are simply no protocol sequences available to the requested operation.
The requested RPC operation has no protocol sequence to use
- Trace the configuration or enumeration path that was expected to provide protocol sequences.
- Keep server-registration state distinct from client binding construction in logs and metrics.
- Confirm that an optional transport list was not filtered to empty by policy, build flags or environment detection.
References
Looking for a different code? Search another status or error code.