| Previous | Next |
| WDSTPC_E_KICKED_FALLBACK | WDSTPC_E_KICKED_UNKNOWN |
WDSTPC_E_KICKED_FAIL
WDSTPC_E_KICKED_FAIL should be handled differently from WDSTPC_E_KICKED_FALLBACK. WDS transport management defines disconnect actions that either direct a client to use an alternate retrieval mechanism or abort attempts to retrieve the data from that server.
Keep abort and fallback outcomes distinct in deployment logic
- Mark the multicast session terminal and preserve the server-provided disconnect outcome.
- Do not silently convert the failure into a unicast fallback unless higher-level policy independently authorizes that behavior.
- Correlate the client ID and session ID with server diagnostics to determine why an administrator or policy path removed the client.
A generic reconnect loop hides the server’s explicit action and can repeatedly rejoin a session that intends the client to abort. The client transport layer should return this status to the deployment coordinator together with content identity and server information. Compare it with the fallback code and unknown-kick code so metrics reveal whether the server intentionally selected an alternate transport, terminated retrieval, or could not classify the reason.
WDS disconnect semantics · WDS management API
Looking for a different code? Search another status or error code.