| Previous | Next |
| VDS_E_INITIATOR_ADAPTER_NOT_FOUND | VDS_E_INVALID_PORT_PATH |
VDS_E_TARGET_PORTAL_NOT_FOUND
The target-side endpoint of an iSCSI VDS path is represented by a target portal object ID. VDS_PATH_INFO uses that identity for iSCSI paths. This HRESULT means the path information cannot be resolved to the portal object expected at the remote endpoint; it is not simply “TCP port 3260 is closed.”
Why this state matters
iSCSI naming and addressing are intentionally separate. The same target name can be reachable through multiple changing addresses, and a portal is an address endpoint rather than the target node identity itself. A stale portal object after failover or discovery changes can therefore produce this error while the target remains reachable through another portal.
Diagnostic focus
- Record the target portal object ID and path ID from the failed
GetPathInforesult. - Enumerate current target portals and compare object identities as well as IP address and TCP port.
- Check whether the target moved or failed over to a different portal while VDS or the provider retained stale path information.
- Reacquire path information after provider refresh; do not patch a target portal ID by matching only a familiar IP address.
Technical references
VDS_PATH_INFO · IVdsLunMpio · VDS_IPADDRESS · RFC 3721: iSCSI naming and discovery · MS-VDS error codes
Looking for a different code? Search another status or error code.