| Previous | Next |
| OR_INVALID_SET | RPC_S_INVALID_ASYNC_HANDLE |
RPC_S_SEND_INCOMPLETE
The send operation stopped before the complete RPC message left the runtime
RPC_S_SEND_INCOMPLETE reports partial progress in sending an RPC request buffer. It is not success with a shorter application payload: some marshaled request data remains unsent, so the remote procedure cannot safely be assumed to have received a complete call.
Capture the protocol sequence, fragment sizes, bytes submitted, bytes acknowledged, cancellation state, and underlying transport error. With pipes or asynchronous transfer, verify producer callbacks continue until the runtime reports completion and do not free buffers early. Application retry policy must account for whether the server could have observed a partial request or begun processing.
What to inspect
- Log total marshaled size and remaining unsent byte count.
- Keep send buffers valid until the RPC runtime completes the operation.
- Use idempotency or request identifiers before retrying uncertain calls.
References
- Microsoft: asynchronous RPC for large transfers
- Microsoft: RPC call failure phases
- Microsoft: send and receive detection locations
Looking for a different code? Search another status or error code.