| Previous | Next |
| WDSTPC_E_NOT_INITIALIZED | WDSTPC_E_KICKED_FALLBACK |
WDSTPC_E_KICKED_POLICY_NOT_MET
WDSTPC_E_KICKED_POLICY_NOT_MET is a server policy decision, not a generic packet-loss condition. WDS transport management exposes multicast-session policy and client/session objects, so diagnosis should correlate the disconnected client with the server policy active for that transmission.
Compare the client against the server policy that removed it
- Identify the namespace, active transport session, and WDS client ID associated with the disconnect.
- Capture server-side diagnostics and the multicast session policy values in effect at that time.
- Do not immediately retry the identical session without understanding the policy condition; the same server decision can repeat deterministically.
WDS exposes policy controls for slow-client handling and automatic disconnection thresholds, along with management objects that report client transfer rate, join duration, CPU, memory, and network utilization. The HRESULT itself does not name the exact violated rule. Therefore, the server event/diagnostic record is the authoritative place to identify why the client failed policy, while the client should preserve the session and request identity for correlation.
Multicast session policy · WDS management API · Slow-client handling
Looking for a different code? Search another status or error code.