Microsoft-Windows-iSCSITarget-Service

198 events across 2 channels

Event ID	Title	Channel
1		Operational
1	The Microsoft iSCSI Target Server service.	Admin
2		Operational
2	The Microsoft iSCSI Target Server service could not register its handler.	Admin
3		Operational
3	The Microsoft iSCSI Target Server service received an invalid service request …	Admin
4		Operational
4	The Microsoft iSCSI Target Server service stopped.	Admin
9		Operational
9	The Microsoft iSCSI Target Server service could not retrieve volume information …	Admin
10		Operational
10	The Microsoft iSCSI Target Server service could not bind to network address %1, …	Admin
11		Operational
11	The iSCSI target received an invalid header digest from initiator %1.	Admin
12		Operational
12	The iSCSI target received an invalid data digest from initiator %1.	Admin
13		Operational
13	The Microsoft iSCSI Target Server service could not create the virtual disk …	Admin
14		Operational
14	The Microsoft iSCSI Target Server service successfully initialized virtual disk …	Admin
15		Operational
15	The Microsoft iSCSI Target Server service could not load virtual disk %1 located …	Admin
16		Operational
16	The iSCSI target is configured to use CHAP authentication but the iSCSI …	Admin
17		Operational
17	The iSCSI target only supports MD5 CHAP authentication, but the iSCSI initiator …	Admin
18		Operational
18	The Microsoft iSCSI Target Server service could not authenticate iSCSI initiator …	Admin
19		Operational
19	The iSCSI target is not configured to use authentication but iSCSI initiator %1 …	Admin
20		Operational
20	iSCSI initiator %1 successfully logged on to the iSCSI target.	Admin
21		Operational
21	iSCSI initiator %1 logged off of the iSCSI target.	Admin
22		Operational
22	iSCSI initiator %1 requested an invalid iSCSI target: %2.	Admin
23		Operational
23	iSCSI initiator %1 sent a PDU with a payload size (%2 bytes) larger than the …	Admin
24		Operational
24	The Microsoft iSCSI Target Server service encountered an error indicating that …	Admin
25		Operational
25	Starting virtual disk %1 roll back to the snapshot taken on %2.	Admin
26		Operational
26	Virtual disk %1 roll back to the snapshot taken on %2 completed successfully.	Admin
27		Operational
27	Virtual disk %1 roll back to the snapshot taken on %2 was stopped by the user.	Admin
28		Operational
28	The Microsoft iSCSI Target Server service could not roll back virtual disk %1 to …	Admin
32		Operational
32	The Microsoft iSCSI Target Server service could not open the local mount driver.	Admin
33		Operational
33	SCSI command %1 directed at virtual disk %2 failed.	Admin
34		Operational
34	The Microsoft iSCSI Target Server service could not delete snapshot of virtual …	Admin
36		Operational
36	Failed to load iSCSI target %1 settings from the registry.	Admin
37		Operational
37	Failed to load virtual disk %1 settings from the registry.	Admin
38		Operational
38	The iSCSI initiator %1 does not have access to this iSCSI target server.	Admin
39		Operational
39	Storage services for iSCSI target %1 is disabled.	Admin
40		Operational
40	Incoming connection request was rejected.	Admin
41		Operational
41	The iSCSI target rejected a connection request from the local computer.	Admin
44		Operational
44	The Microsoft iSCSI Target Server service could not create a snapshot of virtual …	Admin
45		Operational
45	The Microsoft iSCSI Target Server service could not create or open registry key …	Admin
46		Operational
46	The Microsoft iSCSI Target Server service could not locate missing registry key …	Admin
48		Operational
48	Virtual Disk %1 has been disabled.	Admin
49		Operational
49	The Microsoft iSCSI Target Server service could not create a clustered virtual …	Admin
50		Operational
50	The Microsoft iSCSI Target Server service could not delete virtual disk %1.	Admin
51		Operational
51	The Microsoft iSCSI Target Server service could not open virtual disk %1.	Admin
52		Operational
52	The Microsoft iSCSI Target Server service could not assign virtual disk %1 to …	Admin
53		Operational
53	The Microsoft iSCSI Target Server service detected conflicting virtual disk …	Admin
64		Operational
64	The Microsoft iSCSI Target Server service could not create target %1.	Admin
65		Operational
65	The Microsoft iSCSI Target Server service could not create iSCSI target %1 for …	Admin
66		Operational
66	The Microsoft iSCSI Target Server service could not open iSCSI target %1.	Admin
67		Operational
67	The Microsoft iSCSI Target Server service could not delete iSCSI target %1.	Admin
68		Operational
68	The Microsoft iSCSI Target Server service successfully initialized iSCSI target …	Admin
71		Operational
71	The Microsoft iSCSI Target Server service failed to complete service …	Admin
73		Operational
73	The Microsoft iSCSI Target Server service could not online iSCSI target %1.	Admin
74		Operational
74	The Wintarget service has detected the creation of a failover cluster.	Admin
117		Operational
117	iSCSI initiator %1 has committed a protocol error.	Admin
118		Operational
118	The Cluster Service that the Microsoft iSCSI Target Server service depends on is …	Admin
120		Operational
120	A target could not be initialized from its configuration settings.	Admin
121		Operational
121	The CHAP of the target %1 could not be decrypted, the initiator will not be able …	Admin
256		Operational
257		Operational
258		Operational
259		Operational
260		Operational
261		Operational
262		Operational
263		Operational
264		Operational
265		Operational
266		Operational
267		Operational
268		Operational
269		Operational
270		Operational
271		Operational
272		Operational
273		Operational
274		Operational
275		Operational
276		Operational
277		Operational
278		Operational
279		Operational
280		Operational
281		Operational
282		Operational
283		Operational
284		Operational
285		Operational
286		Operational
287		Operational
288		Operational
289		Operational
290		Operational
291		Operational
292		Operational
293		Operational
294		Operational
295		Operational
296		Operational
297		Operational
298		Operational
299		Operational
300		Operational
301		Operational
302		Operational
303		Operational
304		Operational
305		Operational
306		Operational
307		Operational
308		Operational
309		Operational
310		Operational
311		Operational
312		Operational
313		Operational
314		Operational
315		Operational
316		Operational
318		Operational
319		Operational
320		Operational
321		Operational
322		Operational
323		Operational
324		Operational
325		Operational
326		Operational
327		Operational
330		Operational
331		Operational
332		Operational
333		Operational
334		Operational
335		Operational
336		Operational
337		Operational
338		Operational
339		Operational
340		Operational
341		Operational
342		Operational
343		Operational
344		Operational
345		Operational
346		Operational
347		Operational
4096		Operational

Event ID 1 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`VersionHigh`	—
`VersionLow`	—

Event ID 1 — The Microsoft iSCSI Target Server service.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service (v%1.%2) started successfully.

Fields

Name	Description
`VersionHigh`	—
`VersionLow`	—

Event ID 2 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`ErrorCode`	—

Event ID 2 — The Microsoft iSCSI Target Server service could not register its handler.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service could not register its handler. The operation failed with error code %1.

Fields

Name	Description
`ErrorCode`	—

Event ID 3 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`dwControl`	—

Event ID 3 — The Microsoft iSCSI Target Server service received an invalid service request %1.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service received an invalid service request %1.

Fields

Name	Description
`dwControl`	—

Event ID 4 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Event ID 4 — The Microsoft iSCSI Target Server service stopped.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service stopped.

Event ID 9 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hrError`	—

Event ID 9 — The Microsoft iSCSI Target Server service could not retrieve volume information from the system.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service could not retrieve volume information from the system. The operation failed with error code %1.

Fields

Name	Description
`hrError`	—

Event ID 10 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`IpAddress`	—
`dwPort`	—
`Error`	—

Event ID 10 — The Microsoft iSCSI Target Server service could not bind to network address %1, port %2.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service could not bind to network address %1, port %2. The operation failed with error code %3. Ensure that no other application is using this port.

Fields

Name	Description
`IpAddress`	—
`dwPort`	—
`Error`	—

Event ID 11 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`szInitiatorName`	—

Event ID 11 — The iSCSI target received an invalid header digest from initiator %1.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The iSCSI target received an invalid header digest from initiator %1.

Fields

Name	Description
`szInitiatorName`	—

Event ID 12 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`szInitiatorName`	—

Event ID 12 — The iSCSI target received an invalid data digest from initiator %1.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The iSCSI target received an invalid data digest from initiator %1.

Fields

Name	Description
`szInitiatorName`	—

Event ID 13 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`DevicePath`	—
`hrError`	—

Event ID 13 — The Microsoft iSCSI Target Server service could not create the virtual disk using device %1.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service could not create the virtual disk using device %1. The operation failed with error code %2.

Fields

Name	Description
`DevicePath`	—
`hrError`	—

Event ID 14 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`VirtualDiskIndex`	—
`DevicePath`	—

Event ID 14 — The Microsoft iSCSI Target Server service successfully initialized virtual disk %1 located at %2.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service successfully initialized virtual disk %1 located at %2.

Fields

Name	Description
`VirtualDiskIndex`	—
`DevicePath`	—

Event ID 15 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`VirtualDiskIndex`	—
`DevicePath`	—
`hrErrorString`	—

Event ID 15 — The Microsoft iSCSI Target Server service could not load virtual disk %1 located at %2.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service could not load virtual disk %1 located at %2. %3

Fields

Name	Description
`VirtualDiskIndex`	—
`DevicePath`	—
`hrErrorString`	—

Event ID 16 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`szInitiatorName`	—

Event ID 16 — The iSCSI target is configured to use CHAP authentication but the iSCSI initiator %1 does not support it.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The iSCSI target is configured to use CHAP authentication but the iSCSI initiator %1 does not support it.

Fields

Name	Description
`szInitiatorName`	—

Event ID 17 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`szInitiatorName`	—

Event ID 17 — The iSCSI target only supports MD5 CHAP authentication, but the iSCSI initiator %1 does not support it.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The iSCSI target only supports MD5 CHAP authentication, but the iSCSI initiator %1 does not support it.

Fields

Name	Description
`szInitiatorName`	—

Event ID 18 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`szInitiatorName`	—

Event ID 18 — The Microsoft iSCSI Target Server service could not authenticate iSCSI initiator %1.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service could not authenticate iSCSI initiator %1. The challenge was incorrect.

Fields

Name	Description
`szInitiatorName`	—

Event ID 19 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`szInitiatorName`	—

Event ID 19 — The iSCSI target is not configured to use authentication but iSCSI initiator %1 requested it.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The iSCSI target is not configured to use authentication but iSCSI initiator %1 requested it.The target and the initiator are not configured to use the same authentication protocol.

Fields

Name	Description
`szInitiatorName`	—

Event ID 20 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`szInitiatorName`	—

Event ID 20 — iSCSI initiator %1 successfully logged on to the iSCSI target.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

iSCSI initiator %1 successfully logged on to the iSCSI target.

Fields

Name	Description
`szInitiatorName`	—

Event ID 21 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`szInitiatorName`	—

Event ID 21 — iSCSI initiator %1 logged off of the iSCSI target.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

iSCSI initiator %1 logged off of the iSCSI target.

Fields

Name	Description
`szInitiatorName`	—

Event ID 22 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`szInitiatorName`	—
`szTargetName`	—

Event ID 22 — iSCSI initiator %1 requested an invalid iSCSI target: %2.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

iSCSI initiator %1 requested an invalid iSCSI target: %2. The login request was rejected.

Fields

Name	Description
`szInitiatorName`	—
`szTargetName`	—

Event ID 23 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`szInitiatorName`	—
`ActualSize`	—
`MaximumAllowedSize`	—

Event ID 23 — iSCSI initiator %1 sent a PDU with a payload size (%2 bytes) larger than the maximum receive data segment length (%3 bytes).

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

iSCSI initiator %1 sent a PDU with a payload size (%2 bytes) larger than the maximum receive data segment length (%3 bytes).

Fields

Name	Description
`szInitiatorName`	—
`ActualSize`	—
`MaximumAllowedSize`	—

Event ID 24 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`DevicePath`	—

Event ID 24 — The Microsoft iSCSI Target Server service encountered an error indicating that too many sessions are sharing device %1.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service encountered an error indicating that too many sessions are sharing device %1.

Fields

Name	Description
`DevicePath`	—

Event ID 25 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`VirtualDiskIndex`	—
`StartTime`	—

Event ID 25 — Starting virtual disk %1 roll back to the snapshot taken on %2.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

Starting virtual disk %1 roll back to the snapshot taken on %2.

Fields

Name	Description
`VirtualDiskIndex`	—
`StartTime`	—

Event ID 26 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`VirtualDiskIndex`	—
`StartTime`	—

Event ID 26 — Virtual disk %1 roll back to the snapshot taken on %2 completed successfully.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

Virtual disk %1 roll back to the snapshot taken on %2 completed successfully.

Fields

Name	Description
`VirtualDiskIndex`	—
`StartTime`	—

Event ID 27 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`VirtualDiskIndex`	—
`StartTime`	—

Event ID 27 — Virtual disk %1 roll back to the snapshot taken on %2 was stopped by the user.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

Virtual disk %1 roll back to the snapshot taken on %2 was stopped by the user.

Fields

Name	Description
`VirtualDiskIndex`	—
`StartTime`	—

Event ID 28 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`VirtualDiskIndex`	—
`StartTime`	—
`hrError`	—

Event ID 28 — The Microsoft iSCSI Target Server service could not roll back virtual disk %1 to the snapshot taken on %2.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service could not roll back virtual disk %1 to the snapshot taken on %2. The operation failed with error code %3.

Fields

Name	Description
`VirtualDiskIndex`	—
`StartTime`	—
`hrError`	—

Event ID 32 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`Error`	—

Event ID 32 — The Microsoft iSCSI Target Server service could not open the local mount driver.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service could not open the local mount driver (WTLMDrv.sys). %1

Fields

Name	Description
`Error`	—

Event ID 33 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`CDBCommand`	—
`LUN`	—
`Error`	—

Event ID 33 — SCSI command %1 directed at virtual disk %2 failed.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

SCSI command %1 directed at virtual disk %2 failed. %3

Fields

Name	Description
`CDBCommand`	—
`LUN`	—
`Error`	—

Event ID 34 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`VirtualDiskIndex`	—
`StartTime`	—
`hrError`	—

Event ID 34 — The Microsoft iSCSI Target Server service could not delete snapshot of virtual disk %1 taken at %2.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service could not delete snapshot of virtual disk %1 taken at %2. %3

Fields

Name	Description
`VirtualDiskIndex`	—
`StartTime`	—
`hrError`	—

Event ID 36 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`szTargetName`	—
`hrError`	—

Event ID 36 — Failed to load iSCSI target %1 settings from the registry.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

Failed to load iSCSI target %1 settings from the registry. The operation failed with error code %2.

Fields

Name	Description
`szTargetName`	—
`hrError`	—

Event ID 37 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`VirtualDiskIndex`	—
`hrError`	—

Event ID 37 — Failed to load virtual disk %1 settings from the registry.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

Failed to load virtual disk %1 settings from the registry. The operation failed with error code %2.

Fields

Name	Description
`VirtualDiskIndex`	—
`hrError`	—

Event ID 38 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`szInitiatorName`	—

Event ID 38 — The iSCSI initiator %1 does not have access to this iSCSI target server.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The iSCSI initiator %1 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`	—

Event ID 39 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`szTargetName`	—
`szInitiatorName`	—

Event ID 39 — Storage services for iSCSI target %1 is disabled.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

Storage services for iSCSI target %1 is disabled. The log on request from iSCSI initiator %2 was rejected.

Fields

Name	Description
`szTargetName`	—
`szInitiatorName`	—

Event ID 40 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`Status`	—
`StatusString`	—

Event ID 40 — Incoming connection request was rejected.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

Incoming connection request was rejected. The operation failed with error code %1. %2

Fields

Name	Description
`Status`	—
`StatusString`	—

Event ID 41 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Event ID 41 — The iSCSI target rejected a connection request from the local computer.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The iSCSI target rejected a connection request from the local computer. To access the virtual disk from the local computer, use the Disk Access feature in the management console to mount the disk locally.

Event ID 44 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`VirtualDiskIndex`	—
`hrError`	—

Event ID 44 — The Microsoft iSCSI Target Server service could not create a snapshot of virtual disk %1.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service could not create a snapshot of virtual disk %1. The operation failed with error code %2.

Fields

Name	Description
`VirtualDiskIndex`	—
`hrError`	—

Event ID 45 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`KeyPath`	—
`hrError`	—

Event ID 45 — The Microsoft iSCSI Target Server service could not create or open registry key %1.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service could not create or open registry key %1. The operation failed with error code %2.

Fields

Name	Description
`KeyPath`	—
`hrError`	—

Event ID 46 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`KeyPath`	—

Event ID 46 — The Microsoft iSCSI Target Server service could not locate missing registry key %1.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service could not locate missing registry key %1. The key was created.

Fields

Name	Description
`KeyPath`	—

Event ID 48 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`VirtualDiskIndex`	—

Event ID 48 — Virtual Disk %1 has been disabled.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

Virtual Disk %1 has been disabled.

Fields

Name	Description
`VirtualDiskIndex`	—

Event ID 49 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`DevicePath`	—
`hrError`	—

Event ID 49 — The Microsoft iSCSI Target Server service could not create a clustered virtual disk using %1.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service could not create a clustered virtual disk using %1. The operation failed with error code %2.

Fields

Name	Description
`DevicePath`	—
`hrError`	—

Event ID 50 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`VirtualDiskIndex`	—
`hrErrorString`	—

Event ID 50 — The Microsoft iSCSI Target Server service could not delete virtual disk %1.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service could not delete virtual disk %1. %2

Fields

Name	Description
`VirtualDiskIndex`	—
`hrErrorString`	—

Event ID 51 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`VirtualDiskIndex`	—
`hrError`	—

Event ID 51 — The Microsoft iSCSI Target Server service could not open virtual disk %1.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service could not open virtual disk %1. The operation failed with error code %2.

Fields

Name	Description
`VirtualDiskIndex`	—
`hrError`	—

Event ID 52 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`VirtualDiskIndex`	—
`szTargetName`	—
`hrError`	—

Event ID 52 — The Microsoft iSCSI Target Server service could not assign virtual disk %1 to iSCSI target %2.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service could not assign virtual disk %1 to iSCSI target %2. The operation failed with error code %3.

Fields

Name	Description
`VirtualDiskIndex`	—
`szTargetName`	—
`hrError`	—

Event ID 53 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`VirtualDiskIndex`	—
`FirstVirtualDisk`	—
`SecondVirtualDisk`	—
`SecondVirtualDiskIndex`	—

Event ID 53 — The Microsoft iSCSI Target Server service detected conflicting virtual disk index %1 assigned to %2 and %3.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service detected conflicting virtual disk index %1 assigned to %2 and %3. The service automatically updated the virtual disk index of %3 to %4. If this is a snapshot LUN made for a transportable snapshot, it cannot be imported on a different initiator machine automatically. However, it can be manually assigned to a target the initiator connects to.

Fields

Name	Description
`VirtualDiskIndex`	—
`FirstVirtualDisk`	—
`SecondVirtualDisk`	—
`SecondVirtualDiskIndex`	—

Event ID 64 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`szTargetName`	—
`hrError`	—

Event ID 64 — The Microsoft iSCSI Target Server service could not create target %1.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service could not create target %1. %2

Fields

Name	Description
`szTargetName`	—
`hrError`	—

Event ID 65 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`szTargetName`	—
`hrError`	—

Event ID 65 — The Microsoft iSCSI Target Server service could not create iSCSI target %1 for the cluster resource group.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service could not create iSCSI target %1 for the cluster resource group. The operation failed with error code %2.

Fields

Name	Description
`szTargetName`	—
`hrError`	—

Event ID 66 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`szTargetName`	—
`hrError`	—

Event ID 66 — The Microsoft iSCSI Target Server service could not open iSCSI target %1.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service could not open iSCSI target %1. The operation failed with error code %2.

Fields

Name	Description
`szTargetName`	—
`hrError`	—

Event ID 67 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`szTargetName`	—
`hrError`	—

Event ID 67 — The Microsoft iSCSI Target Server service could not delete iSCSI target %1.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service could not delete iSCSI target %1. The operation failed with error code %2.

Fields

Name	Description
`szTargetName`	—
`hrError`	—

Event ID 68 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`szTargetName`	—

Event ID 68 — The Microsoft iSCSI Target Server service successfully initialized iSCSI target %1.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service successfully initialized iSCSI target %1.

Fields

Name	Description
`szTargetName`	—

Event ID 71 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`LineNumber`	—
`Error`	—
`ErrorString`	—

Event ID 71 — The Microsoft iSCSI Target Server service failed to complete service initialization due to reason %1.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service failed to complete service initialization due to reason %1. The operation failed with error code %2. %3

Fields

Name	Description
`LineNumber`	—
`Error`	—
`ErrorString`	—

Event ID 73 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`szTargetName`	—

Event ID 73 — The Microsoft iSCSI Target Server service could not online iSCSI target %1.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Microsoft iSCSI Target Server service could not online iSCSI target %1. Another target with the same name is already online on this cluster node. This can happen when the two targets are created on two different nodes at the same time. To resolve name conflict, move the target's resource group to another node and delete the target. Create a new target with a different name.

Fields

Name	Description
`szTargetName`	—

Event ID 74 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Event ID 74 — The Wintarget service has detected the creation of a failover cluster.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The Wintarget service has detected the creation of a failover cluster. Any existing iSCSI Target and Virtual Disk objects that were created in standalone mode are no longer accessible. Restart the Wintarget service on any cluster nodes that were running iSCSI Target Server in standalone mode.

Event ID 117 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`szInitiatorName`	—

Event ID 117 — iSCSI initiator %1 has committed a protocol error.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

iSCSI initiator %1 has committed a protocol error.

Fields

Name	Description
`szInitiatorName`	—

Event ID 118 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Event ID 118 — The Cluster Service that the Microsoft iSCSI Target Server service depends on is either disabled or not running.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

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 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hrError`	—

Event ID 120 — A target could not be initialized from its configuration settings.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

A target could not be initialized from its configuration settings. The operation failed with error code %1. This can be caused by corruption in its configuration settings. The target needs to be recreated.

Fields

Name	Description
`hrError`	—

Event ID 121 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`szTargetName`	—

Event ID 121 — The CHAP of the target %1 could not be decrypted, the initiator will not be able to connect to the target.

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Admin

Message

The CHAP of the target %1 could not be decrypted, the initiator will not be able to connect to the target. To ensure the security of the access, the target has been disabled. You will need to enable the target and reconfigure the CHAP information.

Fields

Name	Description
`szTargetName`	—

Event ID 256 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`SnapshotId`	—
`OriginalDiskId`	—
`State`	—

Event ID 257 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`VirtualDiskIndex`	—
`DevicePath`	—

Event ID 258 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—
`VirtualDiskIndex`	—

Event ID 259 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`ResourceGuid`	—

Event ID 260 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—
`VirtualDiskIndex`	—

Event ID 261 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`pResource`	—
`Type`	—

Event ID 262 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`pResource`	—
`Type`	—

Event ID 263 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`pResource`	—
`AddOrRemove`	—

Event ID 264 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`pResource`	—
`AddOrRemove`	—

Event ID 265 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`pResource`	—
`AddOrRemove`	—

Event ID 266 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`Line`	—
`Error`	—
`NumTraces`	—
`ReturnAddresses`	—
`FileAndFunction`	—

Event ID 267 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`TargetName`	—
`ResourceGroup`	—

Event ID 268 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—
`pThis`	—

Event ID 269 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`TargetName`	—

Event ID 270 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—

Event ID 271 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`VirtualDiskIndex`	—

Event ID 272 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—
`pThis`	—

Event ID 273 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`VirtualDiskIndex`	—
`DevicePath`	—

Event ID 274 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—
`VirtualDiskIndex`	—

Event ID 275 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`DevicePath`	—

Event ID 276 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—
`pThis`	—

Event ID 277 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`VirtualDiskIndex`	—
`ResourceGuid`	—

Event ID 278 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—

Event ID 279 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Event ID 280 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—
`VirtualDiskIndex`	—

Event ID 281 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Event ID 282 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—
`VirtualDiskIndex`	—

Event ID 283 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`TargetName`	—

Event ID 284 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—
`pThis`	—

Event ID 285 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`pEntity`	—
`Type`	—

Event ID 286 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`Connection`	—
`OldState`	—
`NewState`	—

Event ID 287 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`pEntity`	—
`Type`	—

Event ID 288 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`VirtualDiskIndex`	—

Event ID 289 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Event ID 290 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`pEntity`	—
`EntityId`	—
`VirtualDiskIndex`	—
`DevicePath`	—

Event ID 291 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`pEntity`	—
`EntityId`	—
`OriginalVirtualDiskIndex`	—

Event ID 292 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`pEntity`	—
`EntityId`	—
`TargetName`	—

Event ID 293 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`pEntity`	—

Event ID 294 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`pEntity`	—
`hResult`	—
`ExportedVirtualDiskIndex`	—

Event ID 295 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`SnapshotId`	—

Event ID 296 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—

Event ID 297 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`VirtualDiskIndex`	—

Event ID 298 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—
`SnapshotId`	—

Event ID 299 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`SnapshotSetId`	—

Event ID 300 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—

Event ID 301 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`SnapshotSetId`	—

Event ID 302 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—

Event ID 303 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`SnapshotSetId`	—

Event ID 304 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—

Event ID 305 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`SnapshotSetId`	—

Event ID 306 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—

Event ID 307 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`SnapshotSetId`	—

Event ID 308 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—

Event ID 309 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`SnapshotSetId`	—

Event ID 310 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—

Event ID 311 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`SnapshotId`	—

Event ID 312 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—
`pSnapshot`	—

Event ID 313 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`LocalAddressLength`	—
`LocalAddress`	—
`RemoteAddressLength`	—
`RemoteAddress`	—

Event ID 314 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`TSIH`	—
`ISID`	—
`CID`	—
`InitiatorTaskTag`	—
`InitiatorIQN`	—
`TargetIQN`	—

Event ID 315 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`Session`	—
`Connection`	—
`RemoteAddressLength`	—
`RemoteAddress`	—

Event ID 316 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`Session`	—
`Connection`	—

Event ID 318 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`ResourceGuid`	—
`ControlCode`	—

Event ID 319 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—

Event ID 320 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`ResourceGuid`	—
`ControlCode`	—

Event ID 321 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—

Event ID 322 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`ResourceGuid`	—

Event ID 323 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—

Event ID 324 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`pEntity`	—

Event ID 325 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`pEntity`	—
`hResult`	—

Event ID 326 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`Path`	—

Event ID 327 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—

Event ID 330 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`Path`	—
`ParentPath`	—

Event ID 331 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—

Event ID 332 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`pEntity`	—

Event ID 333 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`pEntity`	—
`hResult`	—

Event ID 334 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`pEntity`	—

Event ID 335 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`pEntity`	—
`hResult`	—

Event ID 336 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`pEntity`	—

Event ID 337 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`pEntity`	—
`hResult`	—

Event ID 338 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`Connection`	—
`Pdu`	—

Event ID 339 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`Connection`	—
`PayloadSize`	—
`PduPayload`	—

Event ID 340 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`Target`	—
`Cdb`	—

Event ID 341 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`Connection`	—
`Pdu`	—

Event ID 342 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`Connection`	—
`PayloadSize`	—
`PduPayload`	—

Event ID 343 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`PhysicalDiskResGuid`	—

Event ID 344 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—

Event ID 345 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`PhysicalDiskResGuid`	—

Event ID 346 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`hResult`	—

Event ID 347 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational

Fields

Name	Description
`pResource`	—
`hResult`	—
`Enabled`	—

Event ID 4096 —

Provider: Microsoft-Windows-iSCSITarget-Service
Channel: Operational