What does HRESULT 0x80010113 (RPC_E_INVALID_IPID) mean?

 
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. AllStat describes it as “The requested object or interface does not exist.” In the COM/RPC call control, message filtering, apartment routing, marshaling, security negotiation, or remote object lifetime, the code identifies a specific failure boundary and should not be replaced by a generic COM exception.

The caller should keep this result intact through logging, exception translation, and RPC or language projection boundaries.

Where it is encountered

  • Cross-apartment or cross-process COM method invocation and activation. Record the interface, method, component version, thread, apartment, process, and correlation ID.
  • 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 for this HRESULT is DCOM/RPC dispatch for an interface pointer identifier that is unknown, expired, disconnected, or associated with another object exporter. Keep it attached to that operation; the same numeric severity outside the owning API does not supply enough context.

Decisive interpretation boundary

Before choosing recovery, verify that the object exporter, OXID/OID/IPID tuple, proxy lifetime, and server restart generation are correlated. The decisive boundary for this HRESULT determines whether the same object can continue, a new object is required, or policy must change.

Also confirm that all observed objects, tokens, buffers, proxies, metadata files, or ACLs belong to the current operation generation and were not retained from an earlier attempt.

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.

Repeat the operation after it only when the documented precondition, identity, apartment, object generation, buffer, or configuration has changed.

Lifetime, retry, and cleanup rules

After it, determine whether the current object, interface pointer, call context, token, stream, metadata reader, asynchronous operation, or access-control instance remains valid. Release only resources owned by the failing attempt, cancel callbacks through their documented mechanism, and avoid double close, double commit, repeated activation, or replay of a non-idempotent remote method.

The retry policy for this HRESULT should state the trigger, maximum attempts, cancellation owner, and reconciliation step for effects that may have completed elsewhere.

Difference from nearby HRESULTs

It identifies an invalid interface endpoint; RPC_E_INVALID_OBJECT says the requested object itself no longer exists.

A support tool discussing it should name the neighboring result only after the originating API and decisive state are known.

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.

A regression test should reproduce it, assert the raw HRESULT and all relevant outputs, then correct only the decisive condition and verify the intended success or neighboring failure result.

References

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