| Previous | Next |
| ERROR_HV_INVALID_PORT_ID | ERROR_HV_INSUFFICIENT_BUFFERS |
ERROR_HV_INVALID_CONNECTION_ID
Connection and port are different objects
Hyper-V inter-partition communication uses a one-way connection associated with a destination port. The sender owns the connection; the receiver owns the port. A message or event is sent through that pre-allocated connection, not directly to an arbitrary partition or virtual processor. This status says that the supplied connection identifier cannot be used as such a sender-side object.
It is distinct from ERROR_HV_INVALID_PORT_ID. A valid connection can outlive a deleted destination port, in which case the connection exists but can no longer deliver data.
What to inspect
- Track connection creation, deletion and ownership with the ID returned by the same Hyper-V object lifecycle.
- Do not reuse a connection ID after the owning partition, channel or driver context has been torn down.
- Confirm that the sender invokes the message or event operation that matches the connection's intended channel type.
- When debugging a race, log the port and connection lifecycle events in order; a numeric ID without ownership context is not enough.
Microsoft TLFS: ports, connections, messages and events · Microsoft TLFS: HvCallPostMessage return values
Looking for a different code? Search another status or error code.