| Previous | Next |
| CO_E_INIT_UNACCEPTED_USER_ALLOCATOR | CO_E_INIT_SCM_FILE_MAPPING_EXISTS |
CO_E_INIT_SCM_MUTEX_EXISTS
OLE service initialization found an existing mutex
CO_E_INIT_SCM_MUTEX_EXISTS is HRESULT 2147500046 (0x8000400E) from winerror.h. The documented description is “The OLE service mutex already exists.” The value must be interpreted at startup coordination between COM/OLE clients and the Service Control Manager activation infrastructure.
A synchronization object expected to be created for a fresh initialization already exists in an incompatible state. Keep the symbolic name beside the raw hexadecimal value so later analysis does not collapse the result into an unrelated COM family.
Where the result appears
- This result may surface in startup coordination between COM/OLE clients and the Service Control Manager activation infrastructure.
Determine the object and lifecycle phase that owned this result; a UI symptom cannot establish whether the origin was the caller, proxy, runtime, server, or metadata producer.
Typical causes and interpretation
Common cause categories are: a previous OLE service instance did not clean up; duplicate startup races; namespace collision; inconsistent service state remains after a crash. Evaluate these branches independently and require evidence from the owning API before promoting one branch to the root cause.
Key distinction: a synchronization object expected to be created for a fresh initialization already exists in an incompatible state.
Correct handling and recovery
The appropriate recovery is to identify the owner, allow the legitimate service to finish, restart the affected service or session, and do not delete named kernel objects blindly. The owner of retry must define idempotency, refreshed state, maximum attempts, backoff, and cancellation responsibility.
After this result, apply the API-specific validity rules to outputs and release only resources whose ownership transferred during this attempt.
Practical scenario
After an activation service crash, a stale coordinated startup path sees the mutex but no healthy owner; restarting the service clears the state.
A regression test should force the relevant precondition, assert native outputs, fix only that condition, and confirm the expected neighboring result.
Difference from related HRESULTs
CO_E_INIT_SCM_FILE_MAPPING_EXISTS reports the analogous collision for the shared file mapping rather than the mutex.
Represent this distinction directly in control flow and dashboards instead of grouping it under a single COM-failure label.
References
Looking for a different code? Search another status or error code.