| Previous | Next |
| RPC_NT_PIPE_DISCIPLINE_ERROR | STATUS_PNP_BAD_MPS_TABLE |
RPC_NT_PIPE_EMPTY
RPC pipe has no more data
RPC_NT_PIPE_EMPTY is the pipe-stream equivalent of reaching the end of available data. It does not by itself prove a transport failure; it may be the normal result when a pull operation consumes the stream.
The important distinction is whether the application expected more chunks at this point. If the pipe should still contain data, inspect callback state, chunk counts, and whether the producer signaled end-of-stream too early.
What to check
- Treat this as normal stream exhaustion unless protocol-level framing says more chunks were required.
- Check producer callbacks for zero-count or end-of-stream returns before all data was queued.
- Compare expected byte or element counts with the number actually delivered through the pipe callbacks.
References
- Microsoft RPC: pipes
- Microsoft MIDL: pipe type constructor
- Microsoft RPC: client-side pipe implementation
- Microsoft Open Specifications: MS-RPCE overview
Looking for a different code? Search another status or error code.