| Previous | Next |
| ERROR_DS_EXISTS_IN_MAY_HAVE | ERROR_DS_NONEXISTENT_MUST_HAVE |
ERROR_DS_NONEXISTENT_MAY_HAVE
mayContain references an invalid attribute definition
When Active Directory validates a classSchema update, every attribute named by mayContain and the corresponding system lists must exist and be active. This error means an optional-attribute reference cannot be resolved. The class definition is therefore incomplete even though the missing attribute would not be mandatory on each instance.
Check the schema import order and the exact identifier used in the class definition. A class LDIF applied before its custom attribute definitions can produce this failure, as can an OID or LDAP name typo. If the attribute was made defunct, the class must not continue to reference it as an active optional attribute.
What to inspect
- Resolve every value in the class optional-attribute lists against the schema NC.
- Ensure custom attributes are created and active before importing the dependent class.
- Compare identifiers exactly; a similar CN is not proof that the referenced schema element exists.
References
Looking for a different code? Search another status or error code.