| Previous | Next |
| ERROR_DS_NO_CHAINED_EVAL | ERROR_DS_PARENT_IS_AN_ALIAS |
ERROR_DS_NO_PARENT_OBJECT
The directory parent required by the operation is not usable
LDAP Add and ModifyDN operations depend on the directory information tree. A child cannot be created or moved beneath a parent that the server cannot resolve as an instantiated entry. In Active Directory this can also intersect with deletion and replication state: the DN text can name a plausible container while the local replica sees the parent as deleted or otherwise unavailable.
Resolve the parent DN directly on the same domain controller that rejected the operation. Checking another DC can hide replication skew. If the parent was recently created, moved, or restored, inspect replication metadata before retrying child creation. Creating intermediate DN components automatically is not part of LDAP Add semantics.
What to inspect
- Derive the parent by removing the leaf RDN from the requested DN.
- Read that exact DN on the failing DC and include deleted-object state when appropriate.
- Verify recent parent creation, move, restore, and replication events.
References
- IETF RFC 4511: LDAP protocol operations and result semantics
- IETF RFC 4512: LDAP directory model, aliases, DNs, and schema
- MS-ADTS: Active Directory Delete operation
Looking for a different code? Search another status or error code.