| Previous | Next |
| WSA_QOS_EUNKOWNPSOBJ | WSA_QOS_EFLOWDESC |
WSA_QOS_EPOLICYOBJ
Policy objects carry authorization data with their own type and encoding
WSA_QOS_EPOLICYOBJ means a policy element in the provider-specific reservation information cannot be validated. Policy data is opaque to the RSVP transport itself but is interpreted by a policy component or decision point; structural validity, recognized element type, credentials, and request context can all matter.
Capture the policy-element type, byte length, originating identity, and exact encoding before any transformation by middleware. Distinguish this structural error from WSA_QOS_POLICY_FAILURE, where a valid policy request is understood but denied. Recreating the same bytes with a different object length can make parsing succeed while still leaving credentials or authorization claims invalid, so validate both syntax and the policy contract.
Policy-object diagnostics
- Policy element type and declared length.
- Credential or identity represented by the payload.
- Encoding and byte order used by the producer.
- Policy engine that was expected to interpret it.
References
- Microsoft: PolicyElementList in reservations
- Microsoft: RSVP_POLICY structures
- IETF RFC 2749: RSVP policy decisions with COPS
Looking for a different code? Search another status or error code.