| Previous | Next |
| STATUS_PIPE_NOT_AVAILABLE | STATUS_PIPE_BUSY |
STATUS_INVALID_PIPE_STATE
The operation does not match the current pipe state
These statuses belong to the Windows named-pipe path. For STATUS_INVALID_PIPE_STATE, 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.
Named pipes move through listening, connected, closing, and disconnected states. This status means the handle is real, but the requested operation is not valid in the current state.
For STATUS_INVALID_PIPE_STATE, 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 whether ConnectNamedPipe, DisconnectNamedPipe, read, or write was called in the wrong order.
- Record both server and client handle states.
- Look for races between overlapped completion and cleanup.
References for STATUS_INVALID_PIPE_STATE
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Named Pipes
- Microsoft: Named Pipe Type, Read, and Wait Modes
- Microsoft: Named Pipe Operations
Looking for a different code? Search another status or error code.