| Previous | Next |
| RPC_E_INVALID_IPID | RPC_S_CALLPENDING |
RPC_E_INVALID_OBJECT
Requested COM object no longer exists
RPC_E_INVALID_OBJECT is HRESULT 2147549460 (0x80010114) from winerror.h. The documented description is “The requested object does not exist.” The relevant context is the COM/RPC call control, message filtering, apartment routing, marshaling, security negotiation, or remote object lifetime.
The caller should keep this result intact through logging, exception translation, and RPC or language projection boundaries.
What to verify
Verify that server object lifetime and client reference ownership are reconstructed without assuming the process itself failed.
Where it is encountered
- Cross-apartment or cross-process COM method invocation and activation.
- STA message filtering, reentrancy, call cancellation, timeout, or retry handling.
- DCOM security initialization, proxy/stub marshaling, OBJREF processing, and server object lifetime.
The immediate focus is a proxy or call that refers to an object identity removed, released, rundown, or invalidated on the server.
Correct handling and recovery
Release the invalid proxy, reacquire or recreate the object through its documented owner, and stop calls during server teardown.
An unchanged retry loop can duplicate effects, deepen reentrancy, or hide an invalid lifetime transition.
Difference from nearby HRESULTs
It faults object identity; RPC_E_INVALID_IPID can fault a particular interface pointer identity on an object.
Developer and administrator guidance
Document the component that returned the result so future occurrences can be correlated across client, proxy, server, package, and security logs.
Practical scenario
A session object is destroyed when its parent document closes, but a background task keeps its proxy. Cancellation now follows parent lifetime.
References
Looking for a different code? Search another status or error code.