| Previous | Next |
| STATUS_CANT_WAIT | STATUS_CANT_ACCESS_DOMAIN_INFO |
STATUS_PIPE_EMPTY
The pipe had no data available to read
These statuses belong to the Windows named-pipe path. For STATUS_PIPE_EMPTY, 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 does not prove that the peer has closed the pipe. It means the read path reached an empty pipe in a mode where empty-buffer state is reported to the caller.
For STATUS_PIPE_EMPTY, 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 blocking versus nonblocking wait mode.
- Look for message boundaries and partial reads.
- Separate empty-pipe state from STATUS_PIPE_CLOSING or STATUS_CONNECTION_RESET.
References for STATUS_PIPE_EMPTY
- 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.