Microsoft-Windows-iSCSITarget-Service
198 events across 2 channels
Event ID 1: The Microsoft iSCSI Target Server service.
#Event ID 1
#Description
The Microsoft iSCSI Target Server service (v.) started successfully.
Fields #
| Name | Description |
|---|---|
VersionHigh UInt16 | |
VersionLow UInt16 |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-iSCSITarget-Service",
"guid": "{13953C6E-C594-414E-8BA7-DEB4BA1878E3}",
"event_source_name": "",
"event_id": 1,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T02:17:57.4938059+00:00",
"event_record_id": 1,
"correlation": {},
"execution": {
"process_id": 4604,
"thread_id": 9684
},
"channel": "Microsoft-Windows-iSCSITarget-Service/Admin",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-18"
}
},
"event_data": {
"VersionHigh": "10",
"VersionLow": "0"
},
"message": "The Microsoft iSCSI Target Server service (v10.0) started successfully."
}
Event ID 2: The Microsoft iSCSI Target Server service could not register its handler.
#Event ID 2
#Description
The Microsoft iSCSI Target Server service could not register its handler. The operation failed with error code .
Fields #
| Name | Description |
|---|---|
ErrorCode UInt32 |
Event ID 3: The Microsoft iSCSI Target Server service received an invalid service request dwControl.
#Event ID 3
#Description
The Microsoft iSCSI Target Server service received an invalid service request .
Fields #
| Name | Description |
|---|---|
dwControl UInt32 |
Event ID 4: The Microsoft iSCSI Target Server service stopped.
#Description
The Microsoft iSCSI Target Server service stopped.
Message #
Event ID 4
#Description
The Microsoft iSCSI Target Server service stopped.
Example Event #
{
"system": {
"provider": "Microsoft-Windows-iSCSITarget-Service",
"guid": "{13953C6E-C594-414E-8BA7-DEB4BA1878E3}",
"event_source_name": "",
"event_id": 4,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T03:11:47.6361855+00:00",
"event_record_id": 6,
"correlation": {},
"execution": {
"process_id": 4604,
"thread_id": 9684
},
"channel": "Microsoft-Windows-iSCSITarget-Service/Admin",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-18"
}
},
"event_data": {},
"message": "The Microsoft iSCSI Target Server service stopped."
}
Event ID 9: The Microsoft iSCSI Target Server service could not retrieve volume information from the system.
#Event ID 9
#Description
The Microsoft iSCSI Target Server service could not retrieve volume information from the system. The operation failed with error code .
Fields #
| Name | Description |
|---|---|
hrError UInt32 |
Event ID 10: The Microsoft iSCSI Target Server service could not bind to network address IpAddress, port dwPort.
#Event ID 10
#Description
The Microsoft iSCSI Target Server service could not bind to network address , port . The operation failed with error code . Ensure that no other application is using this port.
Fields #
| Name | Description |
|---|---|
IpAddress UnicodeString | |
dwPort UInt32 | |
Error UInt32 |
Event ID 11: The iSCSI target received an invalid header digest from initiator szInitiatorName.
#Event ID 11
#Description
The iSCSI target received an invalid header digest from initiator .
Fields #
| Name | Description |
|---|---|
szInitiatorName UnicodeString |
Event ID 12: The iSCSI target received an invalid data digest from initiator szInitiatorName.
#Event ID 12
#Description
The iSCSI target received an invalid data digest from initiator .
Fields #
| Name | Description |
|---|---|
szInitiatorName UnicodeString |
Event ID 13: The Microsoft iSCSI Target Server service could not create the virtual disk using device DevicePath.
#Event ID 13
#Description
The Microsoft iSCSI Target Server service could not create the virtual disk using device . The operation failed with error code .
Fields #
| Name | Description |
|---|---|
DevicePath UnicodeString | |
hrError UInt32 |
Event ID 14: The Microsoft iSCSI Target Server service successfully initialized virtual disk VirtualDiskIndex located at DevicePath.
#Event ID 14
#Description
The Microsoft iSCSI Target Server service successfully initialized virtual disk located at .
Fields #
| Name | Description |
|---|---|
VirtualDiskIndex Int32 | |
DevicePath UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-iSCSITarget-Service",
"guid": "{13953C6E-C594-414E-8BA7-DEB4BA1878E3}",
"event_source_name": "",
"event_id": 14,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T03:12:20.0101326+00:00",
"event_record_id": 7,
"correlation": {},
"execution": {
"process_id": 2920,
"thread_id": 3148
},
"channel": "Microsoft-Windows-iSCSITarget-Service/Admin",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-18"
}
},
"event_data": {
"VirtualDiskIndex": "1322854675",
"DevicePath": "C:\\iscsivd\\lun0.vhdx"
},
"message": "The Microsoft iSCSI Target Server service successfully initialized virtual disk 1322854675 located at C:\\iscsivd\\lun0.vhdx."
}
Event ID 15: The Microsoft iSCSI Target Server service could not load virtual disk VirtualDiskIndex located at DevicePath.
#Event ID 15
#Description
The Microsoft iSCSI Target Server service could not load virtual disk located at .
Fields #
| Name | Description |
|---|---|
VirtualDiskIndex Int32 | |
DevicePath UnicodeString | |
hrErrorString UnicodeString |
Event ID 16: The iSCSI target is configured to use CHAP authentication but the iSCSI initiator szInitiatorName does not support it.
#Event ID 16
#Description
The iSCSI target is configured to use CHAP authentication but the iSCSI initiator does not support it.
Fields #
| Name | Description |
|---|---|
szInitiatorName UnicodeString |
Event ID 17: The iSCSI target only supports MD5 CHAP authentication, but the iSCSI initiator szInitiatorName does not support it.
#Event ID 17
#Description
The iSCSI target only supports MD5 CHAP authentication, but the iSCSI initiator does not support it.
Fields #
| Name | Description |
|---|---|
szInitiatorName UnicodeString |
Event ID 18: The Microsoft iSCSI Target Server service could not authenticate iSCSI initiator szInitiatorName.
#Event ID 18
#Description
The Microsoft iSCSI Target Server service could not authenticate iSCSI initiator . The challenge was incorrect.
Fields #
| Name | Description |
|---|---|
szInitiatorName UnicodeString |
Event ID 19: The iSCSI target is not configured to use authentication but iSCSI initiator szInitiatorName requested it.
#Event ID 19
#Description
The iSCSI target is not configured to use authentication but iSCSI initiator requested it.The target and the initiator are not configured to use the same authentication protocol.
Fields #
| Name | Description |
|---|---|
szInitiatorName UnicodeString |
Event ID 20: iSCSI initiator szInitiatorName successfully logged on to the iSCSI target.
#Event ID 20
#Description
iSCSI initiator successfully logged on to the iSCSI target.
Fields #
| Name | Description |
|---|---|
szInitiatorName UnicodeString |
Event ID 21: iSCSI initiator szInitiatorName logged off of the iSCSI target.
#Event ID 21
#Description
iSCSI initiator logged off of the iSCSI target.
Fields #
| Name | Description |
|---|---|
szInitiatorName UnicodeString |
Event ID 22: iSCSI initiator szInitiatorName requested an invalid iSCSI target: szTargetName.
#Event ID 22
#Description
iSCSI initiator requested an invalid iSCSI target: . The login request was rejected.
Fields #
| Name | Description |
|---|---|
szInitiatorName UnicodeString | |
szTargetName UnicodeString |
Event ID 23: iSCSI initiator szInitiatorName sent a PDU with a payload size (ActualSize bytes) larger than the maximum receive data segment length (MaximumAllowedSize bytes).
#Event ID 23
#Description
iSCSI initiator sent a PDU with a payload size ( bytes) larger than the maximum receive data segment length ( bytes).
Fields #
| Name | Description |
|---|---|
szInitiatorName UnicodeString | |
ActualSize UInt32 | |
MaximumAllowedSize UInt32 |
Event ID 24: The Microsoft iSCSI Target Server service encountered an error indicating that too many sessions are sharing device DevicePath.
#Event ID 24
#Description
The Microsoft iSCSI Target Server service encountered an error indicating that too many sessions are sharing device .
Fields #
| Name | Description |
|---|---|
DevicePath UnicodeString |
Event ID 25: Starting virtual disk VirtualDiskIndex roll back to the snapshot taken on StartTime.
#Event ID 25
#Description
Starting virtual disk roll back to the snapshot taken on .
Fields #
| Name | Description |
|---|---|
VirtualDiskIndex Int32 | |
StartTime FILETIME |
Event ID 26: Virtual disk VirtualDiskIndex roll back to the snapshot taken on StartTime completed successfully.
#Event ID 26
#Description
Virtual disk roll back to the snapshot taken on completed successfully.
Fields #
| Name | Description |
|---|---|
VirtualDiskIndex Int32 | |
StartTime FILETIME |
Event ID 27: Virtual disk VirtualDiskIndex roll back to the snapshot taken on StartTime was stopped by the user.
#Event ID 27
#Description
Virtual disk roll back to the snapshot taken on was stopped by the user.
Fields #
| Name | Description |
|---|---|
VirtualDiskIndex Int32 | |
StartTime FILETIME |
Event ID 28: The Microsoft iSCSI Target Server service could not roll back virtual disk VirtualDiskIndex to the snapshot taken on StartTime.
#Event ID 28
#Description
The Microsoft iSCSI Target Server service could not roll back virtual disk to the snapshot taken on . The operation failed with error code .
Fields #
| Name | Description |
|---|---|
VirtualDiskIndex Int32 | |
StartTime FILETIME | |
hrError UInt32 |
Event ID 32: The Microsoft iSCSI Target Server service could not open the local mount driver.
#Event ID 32
#Description
The Microsoft iSCSI Target Server service could not open the local mount driver (WTLMDrv.sys).
Fields #
| Name | Description |
|---|---|
Error Int32 |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-iSCSITarget-Service",
"guid": "{13953C6E-C594-414E-8BA7-DEB4BA1878E3}",
"event_source_name": "",
"event_id": 32,
"version": 0,
"level": 3,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T02:17:57.4953800+00:00",
"event_record_id": 2,
"correlation": {},
"execution": {
"process_id": 4604,
"thread_id": 9684
},
"channel": "Microsoft-Windows-iSCSITarget-Service/Admin",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-18"
}
},
"event_data": {
"Error": "3"
},
"message": "The Microsoft iSCSI Target Server service could not open the local mount driver (WTLMDrv.sys). 3"
}
Event ID 33: SCSI command CDBCommand directed at virtual disk LUN failed.
#Event ID 33
#Description
SCSI command directed at virtual disk failed.
Fields #
| Name | Description |
|---|---|
CDBCommand UInt8 | |
LUN UInt64 | |
Error Int32 |
Event ID 34: The Microsoft iSCSI Target Server service could not delete snapshot of virtual disk VirtualDiskIndex taken at StartTime.
#Event ID 34
#Description
The Microsoft iSCSI Target Server service could not delete snapshot of virtual disk taken at .
Fields #
| Name | Description |
|---|---|
VirtualDiskIndex Int32 | |
StartTime FILETIME | |
hrError UInt32 |
Event ID 36: Failed to load iSCSI target szTargetName settings from the registry.
#Event ID 36
#Description
Failed to load iSCSI target settings from the registry. The operation failed with error code .
Fields #
| Name | Description |
|---|---|
szTargetName UnicodeString | |
hrError UInt32 |
Event ID 37: Failed to load virtual disk VirtualDiskIndex settings from the registry.
#Event ID 37
#Description
Failed to load virtual disk settings from the registry. The operation failed with error code .
Fields #
| Name | Description |
|---|---|
VirtualDiskIndex Int32 | |
hrError UInt32 |
Event ID 38: The iSCSI initiator szInitiatorName does not have access to this iSCSI target server.
#Event ID 38
#Description
The iSCSI initiator does not have access to this iSCSI target server. To access storage services, you must create an iSCSI target for the initiator.
Fields #
| Name | Description |
|---|---|
szInitiatorName UnicodeString |
Event ID 39: Storage services for iSCSI target szTargetName is disabled.
#Event ID 39
#Description
Storage services for iSCSI target is disabled. The log on request from iSCSI initiator was rejected.
Fields #
| Name | Description |
|---|---|
szTargetName UnicodeString | |
szInitiatorName UnicodeString |
Event ID 40: Incoming connection request was rejected.
#Description
Incoming connection request was rejected. The operation failed with error code Status. StatusString.
Message #
Fields #
| Name | Description |
|---|---|
Status UInt32 | NTSTATUS reference |
StatusString UnicodeString |
Event ID 40
#Description
Incoming connection request was rejected. The operation failed with error code .
Fields #
| Name | Description |
|---|---|
Status UInt32 | NTSTATUS reference |
StatusString UnicodeString |
Event ID 41
#Event ID 44: The Microsoft iSCSI Target Server service could not create a snapshot of virtual disk VirtualDiskIndex.
#Event ID 44
#Description
The Microsoft iSCSI Target Server service could not create a snapshot of virtual disk . The operation failed with error code .
Fields #
| Name | Description |
|---|---|
VirtualDiskIndex Int32 | |
hrError UInt32 |
Event ID 45: The Microsoft iSCSI Target Server service could not create or open registry key KeyPath.
#Event ID 45
#Description
The Microsoft iSCSI Target Server service could not create or open registry key . The operation failed with error code .
Fields #
| Name | Description |
|---|---|
KeyPath UnicodeString | |
hrError UInt32 |
Event ID 46: The Microsoft iSCSI Target Server service could not locate missing registry key KeyPath.
#Event ID 46
#Description
The Microsoft iSCSI Target Server service could not locate missing registry key . The key was created.
Fields #
| Name | Description |
|---|---|
KeyPath UnicodeString |
Event ID 48: Virtual Disk VirtualDiskIndex has been disabled.
#Event ID 49: The Microsoft iSCSI Target Server service could not create a clustered virtual disk using DevicePath.
#Event ID 49
#Description
The Microsoft iSCSI Target Server service could not create a clustered virtual disk using . The operation failed with error code .
Fields #
| Name | Description |
|---|---|
DevicePath UnicodeString | |
hrError UInt32 |
Event ID 50: The Microsoft iSCSI Target Server service could not delete virtual disk VirtualDiskIndex.
#Event ID 50
#Description
The Microsoft iSCSI Target Server service could not delete virtual disk .
Fields #
| Name | Description |
|---|---|
VirtualDiskIndex Int32 | |
hrErrorString UnicodeString |
Event ID 51: The Microsoft iSCSI Target Server service could not open virtual disk VirtualDiskIndex.
#Event ID 51
#Description
The Microsoft iSCSI Target Server service could not open virtual disk . The operation failed with error code .
Fields #
| Name | Description |
|---|---|
VirtualDiskIndex Int32 | |
hrError UInt32 |
Event ID 52: The Microsoft iSCSI Target Server service could not assign virtual disk VirtualDiskIndex to iSCSI target szTargetName.
#Event ID 52
#Description
The Microsoft iSCSI Target Server service could not assign virtual disk to iSCSI target . The operation failed with error code .
Fields #
| Name | Description |
|---|---|
VirtualDiskIndex Int32 | |
szTargetName UnicodeString | |
hrError UInt32 |
Event ID 53: The Microsoft iSCSI Target Server service detected conflicting virtual disk index VirtualDiskIndex assigned to FirstVirtualDisk and SecondVirtualDisk.
#Event ID 53
#Fields #
| Name | Description |
|---|---|
VirtualDiskIndex Int32 | |
FirstVirtualDisk UnicodeString | |
SecondVirtualDisk UnicodeString | |
SecondVirtualDiskIndex UInt32 |
Event ID 64: The Microsoft iSCSI Target Server service could not create target szTargetName.
#Event ID 64
#Description
The Microsoft iSCSI Target Server service could not create target .
Fields #
| Name | Description |
|---|---|
szTargetName UnicodeString | |
hrError UInt32 |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-iSCSITarget-Service",
"guid": "{13953C6E-C594-414E-8BA7-DEB4BA1878E3}",
"event_source_name": "",
"event_id": 64,
"version": 0,
"level": 2,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T02:22:29.7735399+00:00",
"event_record_id": 5,
"correlation": {
"ActivityID": "{1AB7EF36-8292-4507-9136-D92922030D87}"
},
"execution": {
"process_id": 4604,
"thread_id": 12304
},
"channel": "Microsoft-Windows-iSCSITarget-Service/Admin",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-18"
}
},
"event_data": {
"szTargetName": "labtarget-conflict",
"hrError": "2147942480"
},
"message": "The Microsoft iSCSI Target Server service could not create target labtarget-conflict. 2147942480"
}
Event ID 65: The Microsoft iSCSI Target Server service could not create iSCSI target szTargetName for the cluster resource group.
#Event ID 65
#Description
The Microsoft iSCSI Target Server service could not create iSCSI target for the cluster resource group. The operation failed with error code .
Fields #
| Name | Description |
|---|---|
szTargetName UnicodeString | |
hrError UInt32 |
Event ID 66: The Microsoft iSCSI Target Server service could not open iSCSI target szTargetName.
#Event ID 66
#Description
The Microsoft iSCSI Target Server service could not open iSCSI target . The operation failed with error code .
Fields #
| Name | Description |
|---|---|
szTargetName UnicodeString | |
hrError UInt32 |
Event ID 67: The Microsoft iSCSI Target Server service could not delete iSCSI target szTargetName.
#Event ID 67
#Description
The Microsoft iSCSI Target Server service could not delete iSCSI target . The operation failed with error code .
Fields #
| Name | Description |
|---|---|
szTargetName UnicodeString | |
hrError UInt32 |
Event ID 68: The Microsoft iSCSI Target Server service successfully initialized iSCSI target szTargetName.
#Event ID 68
#Description
The Microsoft iSCSI Target Server service successfully initialized iSCSI target .
Fields #
| Name | Description |
|---|---|
szTargetName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-iSCSITarget-Service",
"guid": "{13953C6E-C594-414E-8BA7-DEB4BA1878E3}",
"event_source_name": "",
"event_id": 68,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T02:22:29.6909406+00:00",
"event_record_id": 4,
"correlation": {
"ActivityID": "{530B66BC-533D-491C-ACA0-2190528D4150}"
},
"execution": {
"process_id": 4604,
"thread_id": 12304
},
"channel": "Microsoft-Windows-iSCSITarget-Service/Admin",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-18"
}
},
"event_data": {
"szTargetName": "labtarget-conflict"
},
"message": "The Microsoft iSCSI Target Server service successfully initialized iSCSI target labtarget-conflict."
}
Event ID 71: The Microsoft iSCSI Target Server service failed to complete service initialization due to reason LineNumber.
#Event ID 71
#Description
The Microsoft iSCSI Target Server service failed to complete service initialization due to reason . The operation failed with error code .
Fields #
| Name | Description |
|---|---|
LineNumber UInt32 | |
Error Int32 | |
ErrorString UnicodeString |
Event ID 73: The Microsoft iSCSI Target Server service could not online iSCSI target szTargetName.
#Event ID 74
#Event ID 117: iSCSI initiator szInitiatorName has committed a protocol error.
#Event ID 117
#Description
iSCSI initiator has committed a protocol error.
Fields #
| Name | Description |
|---|---|
szInitiatorName UnicodeString |
Event ID 118: The Cluster Service that the Microsoft iSCSI Target Server service depends on is either disabled or not running.
#Description
The Cluster Service that the Microsoft iSCSI Target Server service depends on is either disabled or not running. Use the Services snap-in to start the Cluster Service.
Message #
Event ID 118
#Description
The Cluster Service that the Microsoft iSCSI Target Server service depends on is either disabled or not running. Use the Services snap-in to start the Cluster Service.
Event ID 120: A target could not be initialized from its configuration settings.
#Event ID 121: The CHAP of the target szTargetName could not be decrypted, the initiator will not be able to connect to the target.
#Event ID 256: SNAPSHOT_STATE_MACHINE
#Fields #
| Name | Description |
|---|---|
SnapshotId GUID | |
OriginalDiskId UInt32 | |
State UInt32 |
Event ID 257: DISKMGR_CREATEDISKStart
#Fields #
| Name | Description |
|---|---|
VirtualDiskIndex UInt32 | |
DevicePath UnicodeString |
Event ID 260: DISKMGR_CREATEDISKStop260
#Fields #
| Name | Description |
|---|---|
hResult UInt32 | |
VirtualDiskIndex UInt32 |
Event ID 263: ISCSIRESOURCECOLLECTION_LIFETIME
#Fields #
| Name | Description |
|---|---|
pResource Pointer | |
AddOrRemove Boolean |
Event ID 264: ISCSIRESOURCECOLLECTION_LIFETIME264
#Fields #
| Name | Description |
|---|---|
pResource Pointer | |
AddOrRemove Boolean |
Event ID 265: ISCSIRESOURCECOLLECTION_LIFETIME265
#Fields #
| Name | Description |
|---|---|
pResource Pointer | |
AddOrRemove Boolean |
Event ID 266: ISCSITGT_ERROR_TRACE
#Fields #
| Name | Description |
|---|---|
Line UInt32 | |
Error UInt32 | |
NumTraces UInt32 | |
ReturnAddresses Int16 | |
FileAndFunction AnsiString |
Event ID 267: TARGETMGR_CREATETARGETStart
#Fields #
| Name | Description |
|---|---|
TargetName UnicodeString | |
ResourceGroup UnicodeString |
Event ID 273: DISKMGR_CREATEDISKStart273
#Fields #
| Name | Description |
|---|---|
VirtualDiskIndex UInt32 | |
DevicePath UnicodeString |
Event ID 274: DISKMGR_CREATEDISKStop274
#Fields #
| Name | Description |
|---|---|
hResult UInt32 | |
VirtualDiskIndex UInt32 |
Event ID 277: SNAPSHOTMGR_NOTIFYStart
#Fields #
| Name | Description |
|---|---|
VirtualDiskIndex UInt32 | |
ResourceGuid GUID |
Event ID 279: DISKMGR_CREATEDISKStart279
#Event ID 280: DISKMGR_CREATEDISKStop280
#Fields #
| Name | Description |
|---|---|
hResult UInt32 | |
VirtualDiskIndex UInt32 |
Event ID 281: DISKMGR_DELETEDISKStart
#Event ID 286: ISCSI_PROTOCOL_LIFETIMEStop
#Fields #
| Name | Description |
|---|---|
Connection Pointer | |
OldState UInt32 | |
NewState UInt32 |
Event ID 289: SNAPSHOTMGR_NOTIFYStop289
#Event ID 290: ISCSITARGETRESOURCE_LIFETIME
#Fields #
| Name | Description |
|---|---|
pEntity Pointer | |
EntityId GUID | |
VirtualDiskIndex UInt32 | |
DevicePath UnicodeString |
Event ID 291: ISCSITARGETRESOURCE_LIFETIME291
#Fields #
| Name | Description |
|---|---|
pEntity Pointer | |
EntityId GUID | |
OriginalVirtualDiskIndex UInt32 |
Event ID 292: ISCSITARGETRESOURCE_LIFETIME292
#Fields #
| Name | Description |
|---|---|
pEntity Pointer | |
EntityId GUID | |
TargetName UnicodeString |
Event ID 294: SNAPSHOT_OPERATIONStop
#Fields #
| Name | Description |
|---|---|
pEntity Pointer | |
hResult UInt32 | |
ExportedVirtualDiskIndex UInt32 |
Event ID 313: ISCSI_PROTOCOL_LIFETIME
#Fields #
| Name | Description |
|---|---|
LocalAddressLength UInt32 | |
LocalAddress Binary | |
RemoteAddressLength UInt32 | |
RemoteAddress Binary |
Event ID 314: ISCSI_PROTOCOL_LIFETIME314
#Fields #
| Name | Description |
|---|---|
TSIH UInt16 | |
ISID UInt16 | |
CID UInt16 | |
InitiatorTaskTag UInt32 | |
InitiatorIQN UnicodeString | |
TargetIQN UnicodeString |
Event ID 315: ISCSI_PROTOCOL_LIFETIMEStart315
#Fields #
| Name | Description |
|---|---|
Session Pointer | |
Connection Pointer | |
RemoteAddressLength UInt32 | |
RemoteAddress Binary |
Event ID 316: ISCSI_PROTOCOL_LIFETIMEStop316
#Fields #
| Name | Description |
|---|---|
Session Pointer | |
Connection Pointer |
Event ID 330: DEVMGR_OPERATIONStart330
#Fields #
| Name | Description |
|---|---|
Path UnicodeString | |
ParentPath UnicodeString |
Event ID 339: PDU_PROCESSING339
#Fields #
| Name | Description |
|---|---|
Connection Pointer | |
PayloadSize UInt32 | |
PduPayload Int8 |
Event ID 342: PDU_PROCESSING342
#Fields #
| Name | Description |
|---|---|
Connection Pointer | |
PayloadSize UInt32 | |
PduPayload Int8 |
Event ID 347: VIRTUALDISK_OPERATION
#Fields #
| Name | Description |
|---|---|
pResource Pointer | |
hResult UInt32 | |
Enabled Boolean |
Event ID 4096: UNIFIED_TRACING
#Provenance
Where this provider's schema came from, and which Windows build it was observed on. Windows can change a provider's event schema between builds, so use this to judge whether it matches the build you collect from.
ETW provider GUID 13953c6e-c594-414e-8ba7-deb4ba1878e3
Defined in iscsitgt.dll, which carries the event manifest.
Observed on:
- WS2022-20348.4893, schema read from the registered manifest, binary version 10.0.20348.1, captured 2026-06-02