| Previous | Next |
| STATUS_PIPE_LISTENING | STATUS_IO_TIMEOUT |
STATUS_INVALID_READ_MODE
The pipe read mode does not match the operation
These statuses belong to the Windows named-pipe path. For STATUS_INVALID_READ_MODE, 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 can be byte-type or message-type, and handles can use byte or message read mode within the rules of the pipe type. This status indicates that the requested read behavior requires a mode the handle does not have.
For STATUS_INVALID_READ_MODE, 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 PIPE_TYPE_MESSAGE versus PIPE_READMODE_MESSAGE.
- Use SetNamedPipeHandleState only with a compatible pipe type.
- Verify both ends agree about byte-stream versus message semantics.
References for STATUS_INVALID_READ_MODE
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Named Pipe Type, Read, and Wait Modes
- Microsoft: Named Pipe Operations
Looking for a different code? Search another status or error code.