| Previous | Next |
| RPC_E_WRONG_THREAD | RPC_E_VERSION_MISMATCH |
RPC_E_THREAD_NOT_INIT
Current thread has not initialized COM
RPC_E_THREAD_NOT_INIT is HRESULT 2147549455 (0x8001010F) from winerror.h. AllStat describes it as “CoInitialize has not been called on the current thread.” 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.
Telemetry should preserve this result as a separate outcome rather than merging it with unrelated COM or WinRT failures.
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 a thread calling COM or OLE functionality before <code>CoInitialize</code> or <code>CoInitializeEx</code>. 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 failing thread and its intended apartment model are identified, including framework threads created outside application startup. 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
Initialize COM on that thread before COM calls and balance every successful initialization with <code>CoUninitialize</code>. Choose STA or MTA deliberately.
Reconcile partial output and server-side effects before attempting the operation again.
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 thread-pool callback creates a COM parser without initializing COM. A scoped initializer configures the worker as MTA and balances cleanup.
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 means COM was never initialized on the thread; RPC_E_WRONG_THREAD means COM exists but the interface belongs elsewhere.
Tests for this HRESULT should force both results and verify that object lifetime, output use, and user messaging differ.
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.