| Previous | Next |
| ERROR_DS_CANT_DEL_MASTER_CROSSREF | ERROR_DS_NOTIFY_FILTER_TOO_COMPLEX |
ERROR_DS_SUBTREE_NOTIFY_NOT_NC_HEAD
AD subtree notifications are scoped to NC heads
Change-notification searches are not ordinary polling searches. Active Directory keeps a notification request associated with directory change processing, and subtree notification has partition-scope constraints. This status indicates that the requested notification base is below the NC head even though the DN may be a valid search base for a normal LDAP subtree search.
The distinction is easy to miss in synchronization code that accepts an arbitrary configured base DN. A client can search an OU subtree but cannot assume every such base is a legal root for NC-level subtree notification. The caller must discover the partition that contains the object and design its filtering or post-processing around the NC boundary.
What to inspect
- Resolve the configured base DN to its containing naming context using
rootDSEand partition metadata. - Request notification at the NC head when the API requires that scope, then filter returned changes to the desired subtree.
- Do not create a new application partition merely to satisfy a notification call unless a separate replicated NC is an actual design requirement.
References
Looking for a different code? Search another status or error code.