| Previous | Next |
| RPC_NT_INVALID_BINDING | RPC_NT_INVALID_RPC_PROTSEQ |
RPC_NT_PROTSEQ_NOT_SUPPORTED
RPC_NT_PROTSEQ_NOT_SUPPORTED is an NTSTATUS value used by the Windows RPC runtime. A protocol sequence selects the RPC transport semantics, such as a connection-oriented TCP transport or a named-pipe transport. This status says the requested sequence is recognized as an RPC protocol sequence but is not supported on the local host or by the installed runtime configuration.
It differs from RPC_NT_INVALID_RPC_PROTSEQ, which means the sequence identifier itself is invalid. It also differs from RPC_NT_NO_PROTSEQS_REGISTERED, which is a server-side state where no supported sequence has been registered for listening.
A valid protocol sequence is not available in this runtime environment
- Capture the exact protocol-sequence identifier used by the client or server and the API that received it.
- Verify that the selected transport is supported on the target Windows installation and is appropriate for the endpoint form being used.
- Choose a documented alternative transport only when both client and server interfaces are designed to expose it.
References
- Microsoft: String binding
- Microsoft: RpcServerUseProtseqEp
- The Open Group: DCE 1.1 RPC specification
Looking for a different code? Search another status or error code.