Site icon EfmSoft

What does HRESULT 0x8000400F (CO_E_INIT_SCM_FILE_MAPPING_EXISTS) mean?

 
Previous Next
CO_E_INIT_SCM_MUTEX_EXISTS CO_E_INIT_SCM_MAP_VIEW_OF_FILE

CO_E_INIT_SCM_FILE_MAPPING_EXISTS

OLE service initialization found an existing file mapping

CO_E_INIT_SCM_FILE_MAPPING_EXISTS is HRESULT 2147500047 (0x8000400F) from winerror.h. The documented description is “The OLE service file mapping already exists.” The value must be interpreted at shared activation state between COM clients and the OLE service.

The named shared-memory mapping already exists when initialization expects to establish a new compatible mapping.

Where the result appears

  • This result may surface in shared activation state between COM clients and the OLE service.

Typical causes and interpretation

Common cause categories are: a stale service instance left shared state; two initializers raced; mapping format differs after an update; namespace isolation is misconfigured. The candidate causes are alternatives, so test one precondition at a time instead of applying several broad repairs together.

Key distinction: the named shared-memory mapping already exists when initialization expects to establish a new compatible mapping.

Correct handling and recovery

The appropriate recovery is to restart the activation service or session, ensure only one owner creates the mapping, and repair version mismatch instead of forcibly deleting live shared state.

Practical scenario

A component update changes the mapping layout while an older service remains running, so the new client refuses the existing mapping.

Difference from related HRESULTs

CO_E_INIT_SCM_MUTEX_EXISTS is a synchronization collision; this code is a shared-memory state collision.

References


Looking for a different code? Search another status or error code.

Exit mobile version