| Previous | Next |
| ERROR_DS_MAX_OBJ_SIZE_EXCEEDED | ERROR_DS_NO_RDN_DEFINED_IN_SCHEMA |
ERROR_DS_OBJ_STRING_NAME_EXISTS
The proposed name collides under the same parent
Directory entries are positioned by distinguished name. For an LDAP Add, the final RDN names the new child beneath its parent. Active Directory rejects creation when another child under that parent already has the same RDN value according to the directory matching rules. This is a namespace collision, not proof that an object with the same display name exists elsewhere in the domain.
Check the actual target parent and normalized RDN. LDAP DN strings can use escaping and different textual presentations, so comparing raw strings in logs is weaker than parsing the DN and comparing its RDN components. A retry with a different server will not make a duplicate sibling legal if the conflicting object has replicated normally.
What to inspect
- Search the intended parent for the proposed RDN, including deleted-object handling when relevant.
- Parse and normalize the DN using LDAP rules before generating a replacement name.
- Do not confuse the naming attribute with unrelated attributes such as displayName.
References
- MS-ADTS: constraints on Active Directory Add operations
- IETF RFC 4512: LDAP directory model, aliases, DNs, and schema
- IETF RFC 4514: string representation of LDAP distinguished names
Looking for a different code? Search another status or error code.