| Previous | Next |
| RPC_NT_SS_CONTEXT_DAMAGED | RPC_NT_SS_CANNOT_GET_CALL_HANDLE |
RPC_NT_SS_HANDLES_MISMATCH
Mismatched RPC binding handles in a stub call
RPC_NT_SS_HANDLES_MISMATCH is a generated-stub validation failure. It appears when the handles supplied for one remote call do not agree with each other, such as mixing an explicit binding handle with a context handle created through a different binding.
This is a sequencing and ownership problem rather than a transport failure. The runtime is protecting the server from receiving a call whose handle parameters identify inconsistent client/server state.
What to check
- Check calls with multiple handle parameters and verify that they originate from the same binding/session path.
- Avoid copying context handles between objects that use different explicit or implicit binding handles.
- Review IDL/ACF handle declarations after refactoring from automatic or implicit handles to explicit handles.
References
- Microsoft MIDL: context_handle attribute
- The Open Group: DCE RPC context handles
- Microsoft RPC: handles
- Microsoft RPC: automatic binding handles
- Microsoft Open Specifications: MS-RPCE overview
Looking for a different code? Search another status or error code.