| Previous | Next |
| RPC_X_SS_CONTEXT_DAMAGED | RPC_X_SS_CANNOT_GET_CALL_HANDLE |
RPC_X_SS_HANDLES_MISMATCH
Two handles describe incompatible server context
RPC_X_SS_HANDLES_MISMATCH means that binding handles supplied to one RPC call do not agree. This matters when an interface uses an explicit binding handle together with a context handle, or otherwise supplies more than one handle-bearing parameter. A non-null context handle is valid for one server, and the related binding information must resolve to the same server address space.
The status is not a generic credentials failure. It points to a mismatch in the identity or destination selected for the call. The error can appear after failover, rebinding, endpoint changes, or incorrect use of a context handle with a newly created binding.
Typical failure patterns
- A client keeps a context handle from server A but rebuilds the explicit binding for server B.
- Load balancing or reconnection changes the target while a higher-level object still stores an old handle.
- Two independently created bindings are combined in a wrapper that assumes they are interchangeable.
- An IDL declaration or FFI wrapper assigns the wrong parameter to the binding-handle role.
How to investigate
- Log the string binding, interface UUID, object UUID where used, and the context-handle owner for every open and subsequent call.
- Verify the IDL declaration: a context handle used as a binding handle changes how the runtime chooses the destination.
- On reconnect or failover, invalidate dependent contexts rather than attempting to attach them to a new binding.
- Keep context ownership explicit in multithreaded code; do not pass a context from one client session into another.
References
Microsoft: context_handle binding rules · The Open Group: RPC handles in IDL · Microsoft: RPC return values
Looking for a different code? Search another status or error code.