| Previous | Next |
| VDS_E_ISCSI_CHAP_SECRET | VDS_E_REBOOT_REQUIRED |
VDS_E_INVALID_IP_ADDRESS
VDS does not represent every network endpoint as a plain string. VDS_IPADDRESS has a tagged address type plus separate IPv4, IPv6, text-address, IPv6 flow/scope, and TCP port fields. The validity of the remaining fields depends on the selected VDS_IPADDRESS_TYPE. This HRESULT can therefore indicate a malformed structure or inconsistent type/data combination, not only a typographical error in dotted-decimal text.
Why this state matters
iSCSI also separates node identity from address. Fixing an invalid portal address does not change the target iSCSI name, and replacing the target name with an IP address is not correct. Validate the endpoint structure at the VDS boundary before troubleshooting login negotiation.
Diagnostic focus
- Log the address type and which representation fields were populated, while avoiding assumptions that
wszTextAddressis always authoritative. - For IPv6, preserve scope ID and port information; link-local addresses can be ambiguous without scope.
- Compare the portal address with the target name separately because RFC 3721 treats them as different concepts.
- Check provider marshaling and structure initialization if the same physical endpoint works in other tools but the VDS call rejects it.
Technical references
VDS_IPADDRESS · VDS_PATH_INFO · RFC 3721: iSCSI naming and discovery · RFC 7143: iSCSI · MS-VDS error codes
Looking for a different code? Search another status or error code.
