| Previous | Next |
| STATUS_BAD_NETWORK_PATH | STATUS_DEVICE_DOES_NOT_EXIST |
STATUS_NETWORK_BUSY
STATUS_NETWORK_BUSY is a transient capacity signal. It does not identify a malformed UNC path, an absent share or an authorization decision. It tells the caller that the relevant network path or provider was busy when the request was processed.
How to narrow it down
Preserve timing information. A single busy response during a burst has a different meaning from a steady response under ordinary load. Correlate it with client request concurrency, server queue depth, retransmissions, SMB credits or storage latency, depending on the layer that emitted the status.
Retries should be bounded and should preserve protocol correctness. Repeating a read is usually straightforward; repeating a write or create must be designed around the possibility that the original operation reached the server before the busy condition was reported.
Evidence that matters
- Capture the operation type and whether it was read-only or could change remote state.
- Compare the failure rate with request concurrency and server-side load over the same interval.
- Use backoff rather than immediately opening parallel replacement sessions.
References
Looking for a different code? Search another status or error code.