| Previous | Next |
| ERROR_DS_DUP_SCHEMA_ID_GUID | ERROR_DS_SEMANTIC_ATT_TEST |
ERROR_DS_DUP_LDAP_DISPLAY_NAME
The lDAPDisplayName collides with an existing class or attribute
The LDAP display name is the schema name clients use in LDAP requests for an attribute or class. Active Directory schema consistency checks require these names to be unique for the relevant schema definitions. A duplicate would make a textual schema name resolve ambiguously, even when the objects have different CNs, OIDs, or GUIDs.
Search the schema naming context by lDAPDisplayName and inspect the existing definition. Product upgrades commonly encounter an already-installed element; in that case the correct behavior is usually to validate the existing schema version rather than create a duplicate. For a genuine naming collision, rename the new schema element at design time and update every client or LDIF reference consistently.
What to inspect
- Search by the exact
lDAPDisplayName, not by the schema object CN. - Compare OID and schemaIDGUID to determine whether the existing object is the same definition.
- Update dependent class lists and application queries if a new display name is required.
References
- MS-ADTS: schema consistency checks
- IETF RFC 4512: LDAP directory models and schema
- Microsoft: attributeSchema class
Looking for a different code? Search another status or error code.