| Previous | Next |
| STATUS_CANT_WAIT | STATUS_CANT_ACCESS_DOMAIN_INFO |
STATUS_PIPE_EMPTY
The pipe had no data available to read
Record whether the call was expected to block and which read mode was configured. An empty pipe can be a normal transient state rather than evidence that the server endpoint disappeared.
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.
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
Looking for a different code? Search another status or error code.