| Previous | Next |
| STATUS_INSTRUCTION_MISALIGNMENT | STATUS_PIPE_NOT_AVAILABLE |
STATUS_INSTANCE_NOT_AVAILABLE
All pipe instances are busy or unavailable
Check how many pipe instances the server created and whether all are connected or reserved. The client may need to wait for an instance rather than recreate the pipe name.
A client reached the pipe name, but the server has no instance that can accept the connection at that moment. This is different from a missing pipe name: the server side may exist, but the instance pool is exhausted or not listening.
What to inspect
- Check the maximum instance count passed to CreateNamedPipe.
- Verify that the server creates a replacement instance after each connection.
- Use WaitNamedPipe-style retry only when the server is expected to create another instance.
References for STATUS_INSTANCE_NOT_AVAILABLE
Looking for a different code? Search another status or error code.