| Previous | Next |
| ERROR_DS_MASTERDSA_REQUIRED | ERROR_DS_MISSING_REQUIRED_ATT |
ERROR_DS_OBJECT_CLASS_REQUIRED
Active Directory cannot validate an entry without objectClass
LDAP entries are governed by schema through their object classes. The objectClass values identify the structural and auxiliary class hierarchy that determines mandatory attributes, permitted attributes, naming rules, and other constraints. An Add request that omits this information leaves the directory without the class model needed to validate the new object.
This is different from an unknown class name or an object-class violation. Here the request is missing the class declaration itself. Capture the complete LDAP Add request or LDIF record and verify that middleware did not strip objectClass. A retry with unrelated attributes cannot succeed until a valid class set is supplied.
What to inspect
- Inspect the exact Add request and confirm that
objectClassis present. - Use a structural class valid for the intended parent and add required auxiliary classes deliberately.
- Do not infer a class solely from the container name or from a client-side object type.
References
- IETF RFC 4512: LDAP directory models and schema
- Microsoft: classSchema class
- MS-ADTS: schema consistency checks
Looking for a different code? Search another status or error code.