| Previous | Next |
| RPC_NT_FP_OVERFLOW | RPC_NT_NO_MORE_BINDINGS |
RPC_NT_CALL_IN_PROGRESS
An RPC call is already active for the thread or handle
RPC_NT_CALL_IN_PROGRESS belongs to the Windows RPC runtime NTSTATUS facility. For RPC_NT_CALL_IN_PROGRESS, 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 is about RPC call sequencing. It is commonly associated with reusing a thread, binding, asynchronous state, or call context before the previous remote procedure call has completed.
The right fix is not a longer network timeout. Confirm who owns the binding and whether completion, cancellation, or exception cleanup always runs before the next call is started.
What to check for RPC_NT_CALL_IN_PROGRESS
- Audit concurrent use of the same binding handle or async state object.
- Check code paths that retry after timeout but do not complete or cancel the old call.
- For callbacks, verify that server-to-client calls are not recursively using a context that is still busy.
References for RPC_NT_CALL_IN_PROGRESS
- 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.