| Previous | Next |
| RPC_S_INVALID_BINDING | RPC_S_INVALID_RPC_PROTSEQ |
RPC_S_PROTSEQ_NOT_SUPPORTED
RPC_S_PROTSEQ_NOT_SUPPORTED means that the specified RPC protocol sequence is recognized, but the local RPC runtime cannot use it in the current environment.
Protocol sequence versus endpoint
A protocol sequence selects the transport, for example local RPC, RPC over TCP/IP, named pipes, or RPC over HTTP. It is separate from the network address and endpoint. An endpoint valid for one transport is not automatically valid for another.
What to check
- Use a protocol sequence supported by both the client and the server deployment.
- Do not derive the transport from an arbitrary URI scheme or configuration label.
- On a server, register the intended protocol sequence before starting to listen.
Microsoft: Selecting a Protocol Sequence · RpcServerUseProtseqEp
Looking for a different code? Search another status or error code.