| Previous | Next |
| RPC_NT_SS_IN_NULL_CONTEXT | RPC_NT_SS_CONTEXT_DAMAGED |
RPC_NT_SS_CONTEXT_MISMATCH
RPC context handle mismatch
RPC_NT_SS_CONTEXT_MISMATCH indicates that a context handle supplied to a stub cannot be matched to known server-side context state. DCE/RPC context handles are created by the server and are meaningful only for the server/context relationship that produced them.
The common cause is mixing handles from different bindings, sessions, interface instances, or server restarts. The byte value of a context token is not portable application state; it is a runtime-managed reference to server-side context.
What to check
- Confirm that the handle was obtained from the same server/interface path that is now receiving it.
- Check failover, service restart, or reconnect logic that reuses old context handles after server state was lost.
- Verify that generated stubs and IDL agree about which parameter is the context handle.
References
- Microsoft MIDL: context_handle attribute
- The Open Group: DCE RPC context handles
- Microsoft RPC: handles
- Microsoft Open Specifications: MS-RPCE overview
Looking for a different code? Search another status or error code.