| Previous | Next |
| RPC_NT_PROTSEQ_NOT_SUPPORTED | RPC_NT_INVALID_STRING_UUID |
RPC_NT_INVALID_RPC_PROTSEQ
RPC_NT_INVALID_RPC_PROTSEQ is an NTSTATUS value used by the Windows RPC runtime. This status is about the protocol-sequence identifier supplied to the RPC runtime. The sequence is not accepted as a valid RPC protocol-sequence name, so the runtime cannot use it to interpret the network address, endpoint or binding options that depend on that transport.
It is narrower than RPC_NT_PROTSEQ_NOT_SUPPORTED. A supported-status failure starts with a valid sequence that the host cannot use; this status means the requested sequence is not valid in the first place.
The protocol-sequence identifier is malformed or unknown to RPC
- Compare the configured sequence against the documented identifiers used by the target RPC transport, including spelling and case where configuration tooling imposes it.
- Validate the sequence together with the endpoint syntax; an endpoint that is meaningful for one transport is not automatically valid for another.
- Do not diagnose firewall, DNS or listener state until the protocol sequence has been accepted.
References
- Microsoft: String binding
- Microsoft: RpcBindingFromStringBinding
- The Open Group: DCE 1.1 RPC specification
Looking for a different code? Search another status or error code.