| Previous | Next |
| ERROR_DS_NO_PARENT_OBJECT | ERROR_DS_CANT_MIX_MASTER_AND_REPS |
ERROR_DS_PARENT_IS_AN_ALIAS
An alias entry cannot act as a directory container
LDAP aliases are entries that name another object through alias semantics. They are not transparent directory junctions for Add or ModifyDN. RFC 4512 describes alias dereferencing as name resolution; it does not turn the alias entry into the referred object for every update operation. Active Directory therefore rejects an attempt to create a child beneath an alias.
Resolve the alias target and decide whether the new entry should actually be created beneath that real object. Do not simply concatenate the child RDN to the alias DN. Search operations have explicit alias-dereferencing choices, while update operations identify their target entries by DN and have different semantics.
What to inspect
- Read objectClass and aliasedObjectName on the proposed parent.
- Resolve the real target DN before building the child DN.
- Keep search alias-dereference settings separate from write-operation target selection.
References
- IETF RFC 4512: LDAP directory model, aliases, DNs, and schema
- IETF RFC 4511: LDAP protocol operations and result semantics
- MS-ADTS: constraints on Active Directory Add operations
Looking for a different code? Search another status or error code.