| Previous | Next |
| CO_E_ASYNC_WORK_REJECTED | CO_E_NO_SECCTX_IN_ACTIVATE |
CO_E_SERVER_INIT_TIMEOUT
COM server did not finish initialization before the deadline
CO_E_SERVER_INIT_TIMEOUT is HRESULT 2147500074 (0x8000402A) from winerror.h. The documented description is “The server started, but did not finish initializing in a timely fashion.” The value must be interpreted at out-of-process COM activation after the server executable starts.
The server process launched but failed to register or signal readiness within the activation timeout.
Where the result appears
- This result may surface in out-of-process COM activation after the server executable starts.
Typical causes and interpretation
Common cause categories are: startup deadlocks; initialization waits on unavailable resources; registration is never reached; security prompts or migrations block readiness. The evidence should distinguish configuration, lifetime, input, identity, resource, and version failures rather than grouping them.
Key distinction: the server process launched but failed to register or signal readiness within the activation timeout.
Correct handling and recovery
The appropriate recovery is to inspect the launched process, remove startup deadlocks and long blocking work, register class objects at the documented point, then retry activation once.
Practical scenario
A local server performs a database migration before CoRegisterClassObject and exceeds the activation deadline; registration is moved earlier and work becomes asynchronous.
Difference from related HRESULTs
CO_E_SERVER_EXEC_FAILURE means launch itself failed; it means the process started but did not become ready.
References
Looking for a different code? Search another status or error code.