What does HRESULT 0x80042900 (VDS_E_INITIATOR_ADAPTER_NOT_FOUND) mean?

 
Previous Next
VDS_E_SECTOR_SIZE_ERROR VDS_E_TARGET_PORTAL_NOT_FOUND

VDS_E_INITIATOR_ADAPTER_NOT_FOUND

This HRESULT is tied to path endpoint identity. VDS_PATH_INFO represents a LUN path and, for an iSCSI path, carries an initiatorAdapterId on the local endpoint. If the provider or service returns a path whose adapter object no longer exists in the current VDS view, GetPathInfo cannot build a coherent endpoint description.

Why this state matters

The missing object should not be inferred from the IP address alone. The initiator adapter is a VDS object, while the initiator portal address is another piece of path information. Adapter removal, stale provider cache, or a race with device reconfiguration can invalidate the object ID even when an interface address still exists.

Diagnostic focus

  • Capture the path ID and initiator adapter object ID from the failing path information.
  • Re-enumerate IVdsServiceIscsi::QueryInitiatorAdapters and compare the returned object IDs with the path endpoint.
  • Check recent HBA/initiator service and Plug and Play changes before editing target configuration.
  • Refresh or re-enumerate provider state and reacquire the LUN/path objects instead of continuing to use stale COM object references.

Technical references

VDS_PATH_INFO · IVdsLunMpio · IVdsServiceIscsi · IVdsIscsiInitiatorAdapter · MS-VDS error codes


Looking for a different code? Search another status or error code.