What does HRESULT 0x80010115 (RPC_S_CALLPENDING) mean?

 
Previous Next
RPC_E_INVALID_OBJECT RPC_S_WAITONTIMER

RPC_S_CALLPENDING

COM call is still pending

RPC_S_CALLPENDING is HRESULT 2147549461 (0x80010115) from winerror.h. The documented description is “OLE has sent a request and is waiting for a reply.” The value must be interpreted at OLE/COM call control while a request has been sent and the caller is awaiting a reply.

The call has not completed and remains outstanding rather than having failed.

Where the result appears

  • This result may surface in OLE/COM call control while a request has been sent and the caller is awaiting a reply.

Typical causes and interpretation

Common cause categories are: the server is still processing; the STA must dispatch messages; a nested wait observes the outstanding call; network latency delays reply. The candidate causes are alternatives, so test one precondition at a time instead of applying several broad repairs together.

Key distinction: the call has not completed and remains outstanding rather than having failed.

Correct handling and recovery

The appropriate recovery is to continue through the documented wait or message-pump mechanism, honor cancellation, and avoid issuing a duplicate non-idempotent call.

Practical scenario

A UI STA waits for a document server and receives the pending status while its message loop continues dispatching incoming COM calls.

Difference from related HRESULTs

RPC_S_WAITONTIMER means COM is deliberately delaying before a retry; it means the original call remains outstanding.

References


Looking for a different code? Search another status or error code.