| Previous | Next |
| ERROR_DS_INVALID_SEARCH_FLAG | ERROR_DS_COULDNT_LOCK_TREE_FOR_DELETE |
ERROR_DS_NO_TREE_DELETE_ABOVE_NC
A tree delete cannot cross an NC boundary from above
Naming contexts are independent replication units. A generic subtree deletion that starts above an NC head would implicitly consume a separate partition boundary as if it were ordinary child data. Active Directory blocks that operation because NC creation and removal follow partition-specific lifecycle and role-owner rules.
This status is not equivalent to “children exist.” Even a caller using a tree-delete control cannot treat the descendant NC as an ordinary subtree. The correct diagnosis is to locate the NC head below the requested delete root and decide whether the partition itself is meant to be removed or whether the delete base is too broad.
What to inspect
- Enumerate descendant naming-context heads and identify the one below the requested deletion root.
- If the partition must remain, narrow the delete to objects within one NC and preserve the NC boundary.
- If the partition must be removed, use the supported domain or application-partition removal process and verify crossRef/replica cleanup.
References
- MS-ADTS naming-context model
- MS-ADTS FSMO processing for crossRef changes
- RFC 4511 directory tree operations
Looking for a different code? Search another status or error code.