Windows error 8386 (ERROR_DS_EXISTS_IN_MAY

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: The attribute cannot be removed while a class still references it in mayContain.

Previous	Next
ERROR_DS_EXISTS_IN_MUST_HAVE	ERROR_DS_NONEXISTENT_MAY_HAVE

ERROR_DS_EXISTS_IN_MAY_HAVE

An optional class-attribute relationship still points to the definition

Optional does not mean unreferenced. A classSchema object can list an attribute in mayContain, allowing instances of that class to carry the value. This status means a schema removal operation targets an attribute that is still named by one or more class definitions. Removing it would leave those class definitions inconsistent.

Locate all schema references before editing the attribute object. Also inspect whether application objects currently use the attribute, because removing a class reference and removing the schema definition are separate concerns. A safe schema migration needs an explicit dependency order and rollback plan; repeatedly retrying the deletion will not make Active Directory ignore the class reference.

What to inspect

Search mayContain and related inherited class metadata for the attribute.
Identify applications and object classes that rely on the optional value.
Change dependent schema definitions before considering the attribute definition itself.

References

Looking for a different code? Search another status or error code.