| Previous | Next |
| ERROR_DS_DUP_RDN | ERROR_DS_DUP_MAPI_ID |
ERROR_DS_DUP_OID
The proposed governsID or attributeID is not unique
LDAP schema elements use object identifiers as stable identities. In Active Directory, an attributeSchema object carries attributeID and a classSchema object carries governsID. MS-ADTS requires the relevant identifiers to be unique. Reusing an OID for a different definition makes schema interpretation ambiguous and the update is rejected.
Search by the numeric OID, not only by CN or lDAPDisplayName. If the existing object belongs to the same product, compare the entire schema definition and version history; the correct action may be to skip an already-applied extension. If it is a real collision, obtain a properly allocated OID branch and revise the extension before production deployment.
What to inspect
- Locate any existing
attributeIDorgovernsIDwith the proposed OID. - Verify whether the import is idempotently encountering the same definition.
- Never solve an OID collision by deleting or repurposing a deployed schema identifier.
References
- MS-ADTS: schema consistency checks
- IETF RFC 4512: LDAP directory models and schema
- Microsoft: Active Directory schema terminology
Looking for a different code? Search another status or error code.