| Previous | Next |
| ERROR_DS_INVALID_DMD | ERROR_DS_NOT_ON_BACKLINK |
ERROR_DS_OBJ_GUID_EXISTS
The objectGUID collides with an existing live or deleted identity
Active Directory assigns objectGUID when an object is created and treats the value as stable, read-only identity thereafter. MS-ADTS permits a requester-specified GUID on Add only under narrow conditions, including a heuristic, a control access right, a non-NULL GUID, and forest-wide nonuse. A duplicate GUID is therefore an identity collision, not a naming collision.
Search by objectGUID and include deleted-object state where appropriate. A renamed object keeps its GUID, and a deleted representation can still matter to local directory state. Generating a different DN does not solve a GUID collision. If the caller is a restore, migration, or replication-related tool, verify why it is attempting to preserve or inject object identity.
What to inspect
- Capture the exact GUID in binary or canonical dashed form.
- Locate any live or deleted object associated with that GUID.
- Determine whether the client should be specifying objectGUID at all.
References
- MS-ADTS: objectGUID and special attribute behavior
- MS-ADTS: constraints on Active Directory Add operations
- MS-ADTS: Active Directory Delete operation
Looking for a different code? Search another status or error code.