| Previous | Next |
| STATUS_DS_ATTRIBUTE_OR_VALUE_EXISTS | STATUS_DS_UNAVAILABLE |
STATUS_DS_BUSY
The directory service was too busy for the request
STATUS_DS_BUSY points to temporary server-side pressure rather than a permanently invalid object. The server accepted the role of directory endpoint, but it could not schedule or finish the requested operation in the current load state.
For write operations, this can coincide with replication backlog, expensive searches, online maintenance, RID allocation pressure, or high LDAP/RPC load. The useful question is not only whether retry succeeds, but why this domain controller became the bottleneck.
What to inspect
- Capture the target DC, operation type, LDAP base/filter or RPC caller, and request duration.
- Review Directory Service events, LDAP query logging and performance counters for queueing or expensive searches.
- Check whether client site mapping is sending too many clients to one DC.
References
- Microsoft: AD replication concepts
- Microsoft: optimize DC/GC location
- LDAP protocol operations: RFC 4511
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.