| Previous | Next |
| STATUS_PIPE_CLOSING | STATUS_PIPE_LISTENING |
STATUS_PIPE_CONNECTED
A connect operation was attempted on an already connected pipe
These statuses belong to the Windows named-pipe path. For STATUS_PIPE_CONNECTED, 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.
The pipe instance is past the listening state. Calling a connect path again on that instance is an ordering error in server code or a race with an already-connected client.
For STATUS_PIPE_CONNECTED, 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 whether ConnectNamedPipe returned after a client connected early.
- Use one pipe instance per active client connection.
- Do not recycle an instance without disconnecting it first.
References for STATUS_PIPE_CONNECTED
- 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.