| Previous | Next |
| STATUS_PIPE_BUSY | STATUS_PIPE_DISCONNECTED |
STATUS_ILLEGAL_FUNCTION
The named-pipe operation was issued on the wrong pipe end
These statuses belong to the Windows named-pipe path. For STATUS_ILLEGAL_FUNCTION, 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.
Some pipe operations are valid only on the server end. This status points to a wrong-handle problem rather than malformed data in the pipe message.
For STATUS_ILLEGAL_FUNCTION, 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
- Confirm whether the handle came from CreateNamedPipe or CreateFile.
- Do not call server-only operations on the client end.
- Log handle ownership when a pipe handle is passed between threads or processes.
References for STATUS_ILLEGAL_FUNCTION
- 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.