| Previous | Next |
| ERROR_DS_EXISTS_IN_SUB_CLS | ERROR_DS_RECALCSCHEMA_FAILED |
ERROR_DS_EXISTS_IN_POSS_SUP
A placement rule still depends on the target class
Possible-superior metadata allows one class to appear as the parent of another class in the directory tree. This status means the class being removed is still named in possSuperiors or a related system list. Deleting it would make a child class carry a parent-class reference that the schema can no longer resolve.
Locate every class that names the target as a legal superior and determine whether those placement rules are still required. Existing directory objects may already use that hierarchy, so changing schema metadata is only part of the migration problem. The correct sequence is to understand the tree and schema dependencies before modifying the target class definition.
What to inspect
- Search possible-superior lists for references to the target class.
- Inspect existing object placement that relies on those class relationships.
- Do not confuse schema superior relationships with the existence of one particular parent object.
References
- MS-ADTS: schema consistency checks
- Microsoft: classSchema class
- IETF RFC 4512: LDAP directory models and schema
Looking for a different code? Search another status or error code.