| Previous | Next |
| RPC_NT_SEC_PKG_ERROR | RPC_NT_INVALID_ASYNC_HANDLE |
RPC_NT_NOT_CANCELLED
RPC call was not cancelled
RPC_NT_NOT_CANCELLED belongs to the Windows RPC runtime NTSTATUS facility. For RPC_NT_NOT_CANCELLED, mS-RPCE extends the DCE/RPC model: generated stubs marshal parameters, the runtime binds to an endpoint and protocol sequence, and security or transport failures can be returned as RPC facility status values.
This status indicates that a cancellation request did not actually cancel the RPC operation. The call may have already completed, may not be cancellable at that point, or the cancellation request may target the wrong thread or asynchronous state.
It is a sequencing result, not proof that the server operation succeeded or failed. For non-idempotent operations, still verify the server-side final state.
What to check for RPC_NT_NOT_CANCELLED
- Check the order of timeout, cancellation, completion, and cleanup callbacks.
- For asynchronous calls, verify that the cancellation uses the correct async handle.
- After cancellation failure, query or log the server-side operation state before retrying destructive work.
References for RPC_NT_NOT_CANCELLED
- Microsoft RPC: asynchronous RPC
- Microsoft RPC: making the asynchronous call
- Microsoft Open Specifications: MS-RPCE overview
Looking for a different code? Search another status or error code.