| Previous | Next |
| STATUS_INVALID_PIPE_STATE | STATUS_ILLEGAL_FUNCTION |
STATUS_PIPE_BUSY
The pipe is busy with outstanding operations
These statuses belong to the Windows named-pipe path. For STATUS_PIPE_BUSY, A named pipe can have multiple instances with the same name, but each instance has its own state, buffer, handles, type mode, read mode, and wait mode.
This is a state and scheduling condition. The pipe may be configured for operations that complete later, while current I/O is still queued on the handle or instance.
For STATUS_PIPE_BUSY, for diagnostics, record the pipe name, server/client end, instance count, blocking versus nonblocking mode, byte versus message mode, overlapped operation state, and whether the handle is connected, listening, closing, or disconnected.
What to inspect
- Check for pending overlapped reads or writes.
- Inspect wait mode and completion routine behavior.
- Avoid closing or reusing the instance until queued I/O is drained.
References for STATUS_PIPE_BUSY
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Named Pipes
- Microsoft: Named Pipe Operations
Looking for a different code? Search another status or error code.