Tracing is inefficient when you diagnose issues that are related to iSCSI Initiator in Windows Server 2008 R2 or in Windows 7

You enable the Event Tracing for Windows (ETW) feature for Microsoft iSCSI Initiator. This feature only supports level-based filters. When you use the ETW feature to diagnose issues that are related to iSCSI Initiator in Windows Server 2008 R2 or in Windows 7, you find that the log file information about the ETW feature does not contain enough details. Therefore, tracing is inefficient.

Note Level-based filters are used for filtering error messages, warning messages, or informational messages.

After you install the hotfix, the ETW feature for iSCSI Initiator adds tracing information that contains more details into the log file. Additionally, the hotfix enables the ETW feature to support component-based filters.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows 7 or Windows Server 2008 R2 on the computer.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 7 and Windows Server 2008 R2 file information notes

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

• The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows 7

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

For all supported IA-64-based versions of Windows Server 2008 R2

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

The new set of iSCSI Initiator tracing flags and levels:

iSCSI provider GUID:

1babefb4-59cb-49e5-9698-fd38ac830a91


iSCSI trace flags:


iScsiFlagGeneral                         bit 0 = 0x00000001 

iScsiFlagAdapter                         bit 1 = 0x00000002 

iScsiFlagUnit                              bit 2 = 0x00000004 

iScsiFlagPnP                               bit 3 = 0x00000008 

iScsiFlagPower                           bit 4 = 0x00000010 

iScsiFlagIoctl                              bit 5 = 0x00000020 

iScsiFlagQueue                           bit 6 = 0x00000040 

iScsiFlagWmi                             bit 7 = 0x00000080 

iScsiFlagTimer                           bit 8 = 0x00000100 

iScsiFlagInit                               bit 9 = 0x00000200 

iScsiFlagLock                             bit 10 = 0x00000400 

iScsiFlagIsr                                bit 11 = 0x00000800 

iScsiFlagEnum                            bit 12 = 0x00001000 

iScsiFlagBoot                             bit 13 = 0x00002000 

iScsiFlagErl                                bit 14 = 0x00004000 

iScsiFlagNetwork                        bit 15 = 0x00008000 

iScsiFlagRadius                          bit 16 = 0x00010000 

iScsiFlagSockets                         bit 17 = 0x00020000 

iScsiFlagScsi                              bit 18 = 0x00040000 

iScsiFlagScsiDataIO                    bit 19 = 0x00080000 

iScsiFlagProtocolLogInOut           bit 20 = 0x00100000 

iScsiFlagProtocolTMF                  bit 21 = 0x00200000 

iScsiFlagProtocolTransfer            bit 22 = 0x00400000 

iScsiFlagCHAP                            bit 23 = 0x00800000 

iScsiFlagDigest                           bit 24 = 0x01000000 

iScsiFlagIpSec                            bit 25 = 0x02000000 


iSCSI trace levels:


iScsiLevelError   1

iScsiLevelWarning 2

iScsiLevelTrace   3

iScsiLevelInfo    4



To enable the ETW feature for iSCSI Initiator using Computer Management, follow these steps: 

1. Click Start, point to Control Panel, point to Administrative Tools, and then click Computer Management.
2. Expand Performance under System Tools, and then expand System.
3. Right-click Event Trace Sessions, and then click Data Collect Set on the New menu.
4. When a Create new Data Collect Set window appears, select Create manually (Advanced), and then click Next.
5. Click Add, and then select the msiscsi_iScsi item in the Event Trace Providers window. Then, click OK.
6. Click Edit to edit the properties of the msiscsi_iScsi item.
7. Click Next repeatedly until you complete the procedure.

To enable using a command-line, the integrated logman.exe tool can be used. This is an example using the provider name: 

Logman start iSCSITrace -p msiscsi_iScsi -o iSCSITrace.etl -ets -nb 8 512 -bs 64

Or using the provider GUID:

Logman start iSCSITrace -p {1BABEFB4-59CB-49E5-9698-FD38AC830A91} -o iSCSITrace.etl -ets -nb 8 512 -bs 64

And then to stop the trace:

Logman stop iSCSITrace -ets

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

Additional files for all supported IA-64-based versions of Windows Server 2008 R2