| Previous | Next |
| RPC_NT_WRONG_STUB_VERSION | RPC_NT_INVALID_PIPE_OPERATION |
RPC_NT_INVALID_PIPE_OBJECT
Invalid RPC pipe object
RPC_NT_INVALID_PIPE_OBJECT belongs to the RPC pipes feature. A MIDL pipe represents streaming data across a call; the generated code uses a pipe control structure with application-supplied push, pull, alloc, and state callbacks.
This status means the pipe object presented to the stub is not a valid pipe object for the operation. It often points to uninitialized pipe structures, overwritten callback fields, lifetime bugs, or using a pipe object after the owning call has ended.
What to check
- Check that the pipe control structure was fully initialized before the call.
- Validate the push, pull, alloc function pointers and application state pointer.
- Look for use-after-return or concurrent reuse of one pipe object across multiple RPC calls.
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.