NTSTATUS 0xC0000477 (STATUS_INVALID_INITIATOR_TARGET

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: STATUS_INVALID_INITIATOR_TARGET_PATH {Invalid I_T Nexus} An attempt was made to send down the command via an invalid path to the target device.

Previous	Next
STATUS_OPERATION_IN_PROGRESS	STATUS_SCRUB_DATA_DISABLED

STATUS_INVALID_INITIATOR_TARGET_PATH

The invalid path is the storage I_T relationship

STATUS_INVALID_INITIATOR_TARGET_PATH names an invalid I_T nexus: the relationship between the initiator side and the target side used to carry a command. It is a transport and topology concept, not a malformed Windows file path.

Windows storage class drivers build storage requests while lower storage port and bus layers provide target addressing. In multipath environments, MPIO and a device-specific module can maintain several paths to the same logical storage. A cached target mapping, path loss, ALUA state change, or inconsistent path selection can therefore make one command route invalid while the device remains reachable through another path.

Record stable target identifiers and path state before forcing a rescan or failover. The T10 ASC/ASCQ list contains several I_T nexus and path-related conditions, so preserving full protocol status is essential. Do not reduce the incident to “device not found” unless the logical target is actually absent on all valid paths.

What to inspect

Initiator port, target port, LUN, and stable device identifiers used for the failing request.
MPIO or DSM path states, recent path loss or failover events, and controller/fabric changes.
Complete transport and sense status from the failed path and the result of the same logical target on other valid paths.

References

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