| Previous | Next |
| VDS_E_INITIATOR_SPECIFIC_NOT_SUPPORTED | VDS_E_ISCSI_LOGOUT_FAILED |
VDS_E_ISCSI_LOGIN_FAILED
This HRESULT marks failure of the VDS login operation, whose input includes target and portal object IDs, initiator portal, login type, digest options, authentication type, and login flags. It does not by itself identify whether the lower-layer cause was name resolution, TCP reachability, iSCSI login negotiation, authentication, digest negotiation, or another initiator-service error.
Why this state matters
iSCSI separates a node name from the network address used to reach it. RFC 3721 emphasizes that a node can keep one stable iSCSI name while its addresses change. Diagnostics should therefore preserve both the target name and the selected portal endpoint. A successful TCP connect alone does not prove that the iSCSI login phase or CHAP authentication can complete.
Diagnostic focus
- Capture the target ID/name, target portal ID, initiator portal ID, authentication type, digest settings, and login flags used in the failed call.
- Test reachability to the selected portal, but also collect initiator-service status because login negotiation occurs after transport connectivity.
- Validate CHAP direction and remembered secrets when authentication is enabled; one-way and mutual CHAP require different secret placement.
- Wait for the returned
IVdsAsyncresult and preserve its final HRESULT instead of reporting only that the asynchronous login was started.
Technical references
IVdsIscsiInitiatorAdapter::LoginToTarget · VDS_ASYNC_OUTPUT_TYPE · VDS_ISCSI_TARGET_PROP · RFC 7143: iSCSI · RFC 3721: iSCSI naming and discovery
Looking for a different code? Search another status or error code.
