| Previous | Next |
| STATUS_INSTANCE_NOT_AVAILABLE | STATUS_INVALID_PIPE_STATE |
STATUS_PIPE_NOT_AVAILABLE
The named pipe exists, but no instance is ready to connect
These statuses belong to the Windows named-pipe path. For STATUS_PIPE_NOT_AVAILABLE, 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 status usually means the pipe namespace entry or server process exists, but every instance is connected, closing, or otherwise not in a listening state. It is a pipe-instance state problem rather than a path parsing problem.
For STATUS_PIPE_NOT_AVAILABLE, 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
- Inspect how many instances the server created.
- Check for clients holding pipe handles longer than expected.
- Differentiate this from STATUS_OBJECT_NAME_NOT_FOUND, where the pipe name itself is absent.
References for STATUS_PIPE_NOT_AVAILABLE
Looking for a different code? Search another status or error code.