| Previous | Next |
| RPC_E_REMOTE_DISABLED | RPC_E_NO_CONTEXT |
RPC_E_INVALID_OBJREF
Marshaled COM OBJREF has invalid format
RPC_E_INVALID_OBJREF is HRESULT 2147549469 (0x8001011D) from winerror.h. AllStat describes it as “The marshaled interface data packet (OBJREF) has an invalid or unknown format.” 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.
Handling this result correctly requires the code-specific postcondition, not merely the fact that FAILED(hr) is true.
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 unmarshaling of interface data whose signature, type, extent, identifiers, or custom-marshaler payload is malformed or unsupported. 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 marshaled byte stream is captured safely with length and hash, and producer/consumer proxy versions are known. 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
Reject the data, rebuild it through COM marshaling APIs, and repair custom marshalers or version skew. Never patch unknown OBJREF bytes in place.
Backoff alone is not a repair for this HRESULT; a measurable state or configuration transition must justify another attempt.
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.
Practical scenario
A custom marshaler writes a truncated payload to shared storage. Versioned length validation rejects it and the interface is marshaled again through the fixed component.
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.
Difference from nearby HRESULTs
It faults the marshaled packet; RPC_E_INVALID_IPID can occur after a structurally valid packet refers to a stale endpoint.
A support tool discussing it should name the neighboring result only after the originating API and decisive state are known.
Developer and administrator guidance
Dashboards should classify it by its actual cause category—lifetime, timing, apartment, marshaling, identity, authorization, format, buffer, or storage—rather than grouping every COM failure under one counter.
Document the owner of the boundary so future occurrences can be correlated across client, proxy, server, package, and security logs. Define who owns retry, cancellation, cleanup, policy changes, package repair, and user-facing messaging for this HRESULT.
References
- Microsoft: COM RPC error codes
- Microsoft: IMessageFilter
- Microsoft: RetryRejectedCall
- Microsoft: CoInitialize
- Microsoft: CoInitializeSecurity
- Microsoft: marshaling rules
- Microsoft: HRESULT values
Looking for a different code? Search another status or error code.