| Previous | Next |
| RPC_E_INVALID_EXTENSION | RPC_E_INVALID_OBJECT |
RPC_E_INVALID_IPID
Requested COM interface pointer identifier is invalid
RPC_E_INVALID_IPID is HRESULT 2147549459 (0x80010113) from winerror.h. The documented description is “The requested object or interface does not exist.” The relevant context is the COM/RPC call control, message filtering, apartment routing, marshaling, security negotiation, or remote object lifetime.
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 DCOM/RPC dispatch for an interface pointer identifier that is unknown, expired, disconnected, or associated with another object exporter.
What to verify
Verify that the object exporter, OXID/OID/IPID tuple, proxy lifetime, and server restart generation are correlated. That condition determines whether the same object can continue, a new object is required, or policy must change.
Correct handling and recovery
Discard the stale proxy, reacquire the interface from a live activation or root object, and fix lifetime or reconnect logic. Do not reuse serialized proxy state.
Difference from nearby HRESULTs
It identifies an invalid interface endpoint; RPC_E_INVALID_OBJECT says the requested object itself no longer exists.
Practical scenario
A client retains a proxy across a server restart. It detects the new server generation and reacquires the interface instead of replaying the old IPID.
References
Looking for a different code? Search another status or error code.