| Previous | Next |
| WDSTPC_E_ALREADY_IN_PROGRESS | WDSTPC_E_NOT_INITIALIZED |
WDSTPC_E_UNKNOWN_ERROR
WDSTPC_E_UNKNOWN_ERROR provides no subsystem-specific cause in the HRESULT itself. The useful diagnosis therefore comes from WDS transport context: the session-completion status, callback order, server/namespace/object request, and server diagnostics for the same transfer.
Preserve the first concrete failure around the unknown status
- Log every transport-client API return value before the final unknown error; a prior initialization or callback failure may be more specific.
- Record the request fields from
WDS_TRANSPORTCLIENT_REQUEST, including server, namespace, object name, protocol, authentication mode, and API version. - Correlate the client completion callback with WDS transport diagnostics/event logging on the server.
The request structure can be rejected based on API version and includes provider-dependent object naming, authentication mode, cache size, and protocol selection. An unknown terminal code should not trigger speculative configuration changes. Reproduce with a minimal request and retain the exact session timeline. If a later callback supplies a nonrecoverable completion status, report that value as the primary cause and keep this code as the transport wrapper outcome.
Transport request structure · WDS diagnostics/API overview · Transport client functions
Looking for a different code? Search another status or error code.