| Previous | Next |
| ERROR_DBG_COMMAND_EXCEPTION | ERROR_THREAD_WAS_SUSPENDED |
ERROR_OBJECT_NAME_EXISTS
What ERROR_OBJECT_NAME_EXISTS means
A named kernel or system object already exists when code attempts to create it. In practical terms, this status belongs to named object creation: CreateEvent, CreateMutex, CreateFileMapping, registry, or related APIs encounter an existing name.
Typical causes
- Another process created the object first
- The same process repeated initialization
- A stale object remains alive because a handle is still open
How to investigate
- Check whether the creating API returned a valid handle together with this status
- Log the full object namespace and session context
- Determine whether sharing the existing object is intended or a name-collision bug
Developer guidance
For many Win32 create APIs this is an informational result, not a failed handle. Always inspect the documented return contract before closing or discarding the returned object.
Operational interpretation
When ERROR_OBJECT_NAME_EXISTS appears, first determine whether the operation actually failed, completed with an informational condition, or transferred work to another component. Record the API name, returned value, affected process or object, and the immediately preceding event. For this code, the most useful boundary is the named object creation boundary; broad machine-wide remediation before that boundary is identified can hide the original evidence.
Example scenario
An incident begins when another process created the object first. A responder investigating this result should not begin with a generic reboot that destroys the original context. A better first step is to check whether the creating API returned a valid handle together with this status. That evidence connects it to its producing operation and reveals whether this particular result is repeatable, expected, or merely secondary.
Logging and telemetry
Telemetry for this Win32 error should preserve its numeric value, component version, process and thread identifiers, operation name, affected object or endpoint, elapsed time, and the first earlier failure in the same activity. Keep the result correlation identifier stable across callbacks so the status can be joined to the request that initiated this exact operation.
Recovery and validation
Apply recovery only after the responsible state has demonstrably changed. After changing that state, repeat one controlled this result scenario and verify both the returned status and the resulting system state. Absence of another log line is not sufficient: confirm that the intended named object creation action completed, that no resource remains pending, and that later cleanup does not produce a different secondary error.
References
Looking for a different code? Search another status or error code.