| Previous | Next |
| ERROR_DS_NOTIFY_FILTER_TOO_COMPLEX | ERROR_DS_DUP_OID |
ERROR_DS_DUP_RDN
Two schema objects collide on their directory RDN
Schema definitions are themselves directory objects stored in the schema naming context. This status reports a duplicate RDN during schema update processing. It is therefore about the directory name of a schema object, not merely the lDAPDisplayName, OID, or GUID used to identify schema semantics.
Compare the proposed LDIF DN with existing schema objects before changing any identifiers. A vendor package can collide because a previous version was imported, because the extension uses a generic CN, or because an interrupted deployment already created the object. Renaming the schema object CN may avoid the RDN collision only if the semantic identifiers remain correct and the extension design allows that change.
What to inspect
- Search the schema NC for the proposed CN or complete RDN.
- Determine whether the existing object is the same schema definition or an unrelated collision.
- Do not delete an existing schema object simply to free its RDN; schema deletions and references require separate validation.
References
- Microsoft: Active Directory schema terminology
- Microsoft: classSchema class
- Microsoft: attributeSchema class
Looking for a different code? Search another status or error code.