What does Windows error code 1725 (RPC_S_NO_CALL_ACTIVE) mean?

RPC_S_NO_CALL_ACTIVE

A call-scoped API was used outside an active server call

RPC_S_NO_CALL_ACTIVE is a thread and call-context error. Some server APIs inspect the RPC call currently dispatched on the calling thread—for example to test cancellation, query caller information, or manipulate call state. They cannot infer a call after the manager routine has returned or from an unrelated worker thread.

Record the thread identifier at stub entry, manager dispatch, worker handoff, and the failing RPC API. If work is delegated, pass an explicitly supported binding or asynchronous state instead of assuming thread-local call context follows the task. This status does not indicate that the client disconnected; it says the API cannot find an active call in the caller’s current execution context.

What to inspect

• Verify the API is invoked while the server manager routine is still active.
• Do not move call-context-only operations to a generic thread pool.
• Use asynchronous RPC APIs when work must outlive the original dispatch thread.

References

• Microsoft: RPC client, runtime, stub, and server flow
• Microsoft: asynchronous RPC execution model
• Microsoft: RPC error handling