| Previous | Next |
| RPC_E_THREAD_NOT_INIT | RPC_E_INVALID_HEADER |
RPC_E_VERSION_MISMATCH
Client and server OLE versions are incompatible
RPC_E_VERSION_MISMATCH is HRESULT 2147549456 (0x80010110) from winerror.h. The documented description is “The version of OLE on the client and server machines does not match.” 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 activation or communication between COM/OLE components whose protocol or runtime expectations do not match.
What to verify
Verify that client, proxy, stub, server, and system component versions are captured from both machines. Validate this condition using the owning API state, not an inferred UI symptom.
Correct handling and recovery
Align supported component versions, repair proxy/stub registration, and avoid copying individual OLE binaries between systems.
Practical scenario
A legacy automation client connects to a server after only its executable was upgraded. Deployment installs the matching proxy/stub and server set.
Difference from nearby HRESULTs
It is protocol/runtime incompatibility; RPC_E_INVALID_OBJREF indicates malformed marshaled data.
Developer and administrator guidance
References
Looking for a different code? Search another status or error code.