| Previous | Next |
| WSA_QOS_NO_SENDERS | WSA_QOS_REQUEST_CONFIRMED |
WSA_QOS_NO_RECEIVERS
The last RESV state has disappeared while sender path state may remain
WSA_QOS_NO_RECEIVERS means no receiver reservation currently reaches the sender for the monitored flow. A sender can continue advertising PATH state and transmitting best-effort traffic even though every RESV state was removed, expired, or torn down. The event therefore describes reservation membership, not necessarily socket connectivity.
For multicast, identify which reservation branch vanished and whether merged state was recomputed. For unicast, compare the event with receiver shutdown, RESV teardown, policy rejection, and refresh timeout. Applications that require reserved service should downgrade or pause the affected media flow rather than silently assuming the prior QoS still applies. A reconnect is useful only when it recreates the missing receiver and signaling state; it cannot repair an administrative or capacity rejection by itself.
Reservation state to compare
- Last receiver or filter specification.
- Reservation style and merged flowspec.
- RESV refresh, teardown, or error timestamp.
- Application fallback chosen after QoS disappeared.
References
- Microsoft: status information carried with FD_QOS
- Microsoft: RSVP reservation styles
- IETF RFC 2205: RESV state and refresh
Looking for a different code? Search another status or error code.