| Previous | Next |
| ERROR_DS_ROOT_CANT_BE_SUBREF | ERROR_DS_NO_CHAINED_EVAL |
ERROR_DS_NO_CHAINING
The server refuses distributed-directory request chaining
Directory chaining means one directory server continues a client operation by contacting another directory service on the client's behalf. LDAP also defines referrals, where the client is told about another server or naming location and decides whether to follow it. These are different distributed-directory behaviors. This code says chaining is not available for the attempted operation.
Inspect the target DN and the naming contexts held by the contacted domain controller. If the object is outside a writable local partition, the correct client behavior can be to process a referral or bind directly to an appropriate server rather than expecting server-side chaining. Repeating the same request against the same scope does not change that directory topology.
What to inspect
- Record referrals returned with the LDAP result and preserve their URLs.
- Compare the target DN with naming contexts advertised in rootDSE.
- Use referral-aware client logic instead of assuming transparent server proxying.
References
- IETF RFC 4511: LDAP protocol operations and result semantics
- Microsoft: RootDSE naming-context metadata
- MS-ADTS: constraints on Active Directory Modify operations
Looking for a different code? Search another status or error code.