| Previous | Next |
| RPC_NT_SS_CONTEXT_MISMATCH | RPC_NT_SS_HANDLES_MISMATCH |
RPC_NT_SS_CONTEXT_DAMAGED
RPC context handle changed during a call
RPC_NT_SS_CONTEXT_DAMAGED points to a context-handle lifetime or memory-corruption problem around generated stub code. The context handle should remain stable according to the IDL direction attributes and the server contract.
Because context handles represent server-maintained state, arbitrary modification by client code, incorrect marshaling declarations, or memory overwrite near the context variable can make the stub detect that the handle changed unexpectedly.
What to check
- Check whether the parameter is declared with the correct
[in],[out], or[in,out]attributes. - Audit client-side storage for the context handle; avoid sharing the same variable across concurrent calls without synchronization.
- Look for memory overwrite near the context variable before assuming the remote endpoint changed behavior.
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.