| Previous | Next |
| WSA_QOS_REQUEST_CONFIRMED | WSA_QOS_POLICY_FAILURE |
WSA_QOS_ADMISSION_FAILURE
Admission control rejected capacity, independently of user authorization
WSA_QOS_ADMISSION_FAILURE means a node could not allocate the traffic-control resources required by the requested FLOWSPEC. RSVP separates capacity admission from policy control: this code points to bandwidth, scheduler, queue, or local traffic-control limits rather than invalid credentials or an administrative policy decision.
Capture the requested service type, token rate, peak bandwidth, latency, and path location that produced the error. Reducing only one field may not make the request admissible because burst size and minimum packet size also affect resource calculations. Retry after capacity changes or with a deliberately revised service profile; repeated identical requests can continue to fail and may hide contention from competing reservations. Check whether the rejection arose locally during conversion to the Traffic Control API or from an RSVP-capable network hop.
Capacity evidence to collect
- Complete sending and receiving FLOWSPEC values.
- Failing interface or RSVP hop.
- Existing reservations sharing the scheduler.
- Extended status identifying local or remote admission control.
References
- Microsoft: FLOWSPEC resource parameters
- IETF RFC 2205: admission versus policy control
- IETF RFC 2211: controlled-load service
Looking for a different code? Search another status or error code.