| Previous | Next |
| VDS_E_PROVIDER_CACHE_CORRUPT | VDS_E_PROVIDER_VOL_DEVICE_NAME_NOT_FOUND |
VDS_E_DMADMIN_METHOD_CALL_FAILED
VDS_E_DMADMIN_METHOD_CALL_FAILED This error is returned when the VDS provider made a method call to the Logical Disk Manager administrative service and that call failed. It should be separated from VDS_E_DMADMIN_SERVICE_CONNECTION_FAILED: the latter describes inability to establish the service connection, whereas this code says the administrative call path was reached but did not complete successfully.
What the VDS state means
The HRESULT does not identify which disk-management method failed. The calling application must preserve the VDS operation, target object GUID, provider, and any asynchronous result. VDS methods can also return converted system errors or provider-specific failures, so flattening everything to the symbolic HRESULT loses the information needed to find the failed layer.
Diagnostic focus
- Log the exact VDS interface and method, the pack/disk/volume identifier, and all input parameters that preceded the failure.
- For asynchronous calls, inspect both the HRESULT returned by
IVdsAsync::Waitand the operation HRESULT inpHrResult; Microsoft requires callers to examine both. - Check VDS/LDM events and compare the object state after the failure rather than assuming the operation was atomic.
- Retry only after determining whether the object is stale or the service reported a transient condition; an unconditional loop can repeatedly issue the same invalid state transition.
Technical references
VDS common return codes · MS-VDS error codes · IVdsAsync::Wait · IVdsPack · IVdsVolume
Looking for a different code? Search another status or error code.