| Previous | Next |
| ERROR_CLUSTER_PARAMETER_OUT_OF_BOUNDS | ERROR_CLUSTER_REGISTRY_INVALID_FUNCTION |
ERROR_CLUSTER_PARTIAL_SEND
A short send is a transport failure inside a framed cluster message
ERROR_CLUSTER_PARTIAL_SEND means a cluster communication path accepted fewer bytes than the message required. The remaining bytes cannot be treated as a second independent message because cluster protocols frame and serialize their data. Retrying only the tail without the original protocol context can leave sender and receiver out of sync.
Correlate the error with FailoverClustering events and cluster logs from both nodes. Record the source and destination node, transport connection, intended and transmitted byte counts, and any simultaneous network reset, firewall, NIC, or resource-pressure event. Validate the cluster networks and adapter configuration rather than focusing only on client-facing application traffic; cluster heartbeat and internal traffic can use different paths or network roles.
Transport evidence worth preserving
- Peer node and cluster network used for the exchange.
- Expected versus actually transmitted bytes.
- Connection reset, timeout, NIC, switch, or firewall events at the same timestamp.
- Whether failures occur on one path, one node pair, or under resource pressure.
References
- Microsoft: generating cluster logs for node correlation
- Microsoft: validating failover-cluster networks
- Microsoft: correlating FailoverClustering events and logs
Looking for a different code? Search another status or error code.