Symptoms
Consider the following scenario:
-
You have a computer that is running one of the following operating systems:
-
Windows Vista
-
Windows Server 2008
-
Windows 7
-
Windows Server 2008 R2
-
-
You set up an iSCSI storage device on the computer. Then, you configure the persistent logon setting and Challenge Handshake Authentication Protocol (CHAP) authentication setting for the device.
-
You disconnect the network connection on the computer, and then you restart the computer.
-
You wait at least 30 seconds, and then you reestablish the network connection.
-
The iSCSI initiator user interface displays the connection state as Reconnecting.
In this scenario, the iscsicpl.exe process stops responding. Additionally, you cannot disconnect the storage device from the computer. To reestablish the connection between the storage device and the computer, you must restart the computer.
Cause
This issue occurs because the session between the storage device and the computer is locked when the iSCSI initiator tries to log on. However, the iSCSI initiator does not try to log on after 10 failed log on attempts. Therefore, the session is not released.
Resolution
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 website:http://support.microsoft.com/contactus/?ws=supportNote 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 one of the following operating systems:
-
Windows Vista Service Pack 2 (SP2)
-
Windows Server 2008 Service Pack 2 (SP2)
-
Windows 7
-
Windows 7 Service Pack 1 (SP1)
-
Windows Server 2008 R2
-
Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:
935791How to obtain the latest Windows Vista service pack For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
968849How to obtain the latest service pack for Windows Server 2008 For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Registry information
To use the hotfix, you do not have to make any changes to the registry.
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 Vista and Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
-
The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Version
Product
SR_Level
Service branch
6.0.600
2. 22xxxWindows Vista and Windows Server 2008
SP2
LDR
-
Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
-
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 and for Windows Vista" section. MUM files 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 Server 2008 and of Windows Vista
File name |
File version |
File size |
Date |
Time |
---|---|---|---|---|
Iscsilog.dll |
6.0.6002.22814 |
16,384 |
08-Mar-2012 |
13:39 |
Msiscsi.sys |
6.0.6002.22814 |
182,144 |
09-Mar-2012 |
6:20 |
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
File name |
File version |
File size |
Date |
Time |
---|---|---|---|---|
Iscsilog.dll |
6.0.6002.22814 |
16,384 |
08-Mar-2012 |
14:21 |
Msiscsi.sys |
6.0.6002.22814 |
218,496 |
09-Mar-2012 |
6:16 |
For all supported IA-64-based versions of Windows Server 2008
File name |
File version |
File size |
Date |
Time |
---|---|---|---|---|
Iscsilog.dll |
6.0.6002.22814 |
16,384 |
08-Mar-2012 |
13:21 |
Msiscsi.sys |
6.0.6002.22814 |
505,216 |
09-Mar-2012 |
6:12 |
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 files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Version
Product
Milestone
Service branch
6.1.760
0.16xxxWindows 7 and Windows Server 2008 R2
RTM
GDR
6.1.760
0.21xxxWindows 7 and Windows Server 2008 R2
RTM
LDR
6.1.760
1.17xxxWindows 7 and Windows Server 2008 R2
SP1
GDR
6.1.760
1.21xxxWindows 7 and Windows Server 2008 R2
SP1
LDR
-
GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
-
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 and of Windows Server 2008 R2
File name |
File version |
File size |
Date |
Time |
---|---|---|---|---|
Iscsilog.dll |
6.1.7600.16385 |
16,384 |
14-Jul-2009 |
1:06 |
Msiscsi.sys |
6.1.7600.16975 |
186,736 |
08-Mar-2012 |
6:00 |
Iscsilog.dll |
6.1.7600.16385 |
16,384 |
14-Jul-2009 |
1:06 |
Msiscsi.sys |
6.1.7600.21165 |
233,840 |
08-Mar-2012 |
5:42 |
Iscsilog.dll |
6.1.7600.16385 |
16,384 |
14-Jul-2009 |
1:06 |
Msiscsi.sys |
6.1.7601.17792 |
233,840 |
08-Mar-2012 |
5:47 |
Iscsilog.dll |
6.1.7600.16385 |
16,384 |
14-Jul-2009 |
1:06 |
Msiscsi.sys |
6.1.7601.21938 |
233,840 |
08-Mar-2012 |
5:48 |
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File name |
File version |
File size |
Date |
Time |
---|---|---|---|---|
Iscsilog.dll |
6.1.7600.16385 |
16,384 |
14-Jul-2009 |
1:28 |
Msiscsi.sys |
6.1.7600.16975 |
225,136 |
08-Mar-2012 |
6:38 |
Iscsilog.dll |
6.1.7600.16385 |
16,384 |
14-Jul-2009 |
1:28 |
Msiscsi.sys |
6.1.7600.21165 |
274,288 |
08-Mar-2012 |
6:35 |
Iscsilog.dll |
6.1.7600.16385 |
16,384 |
14-Jul-2009 |
1:28 |
Msiscsi.sys |
6.1.7601.17792 |
274,288 |
08-Mar-2012 |
6:46 |
Iscsilog.dll |
6.1.7600.16385 |
16,384 |
14-Jul-2009 |
1:28 |
Msiscsi.sys |
6.1.7601.21938 |
274,288 |
08-Mar-2012 |
6:24 |
For all supported IA-64-based versions of Windows Server 2008 R2
File name |
File version |
File size |
Date |
Time |
---|---|---|---|---|
Iscsilog.dll |
6.1.7600.16385 |
16,384 |
14-Jul-2009 |
1:36 |
Msiscsi.sys |
6.1.7600.16975 |
514,416 |
08-Mar-2012 |
5:31 |
Iscsilog.dll |
6.1.7600.16385 |
16,384 |
14-Jul-2009 |
1:36 |
Msiscsi.sys |
6.1.7600.21165 |
682,352 |
08-Mar-2012 |
5:39 |
Iscsilog.dll |
6.1.7600.16385 |
16,384 |
14-Jul-2009 |
1:36 |
Msiscsi.sys |
6.1.7601.17792 |
681,840 |
08-Mar-2012 |
5:20 |
Iscsilog.dll |
6.1.7600.16385 |
16,384 |
14-Jul-2009 |
1:36 |
Msiscsi.sys |
6.1.7601.21938 |
682,352 |
08-Mar-2012 |
5:34 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
For more information about the RAIL feature, visit the following Microsoft website:
General information about the RAIL featureFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684Description of the standard terminology that is used to describe Microsoft software updates
Additional file information
Additional file information for Windows Vista and for Windows Server 2008
Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008
File name |
X86_iscsi.inf_31bf3856ad364e35_6.0.6002.22814_none_3f2d189f09ef0bef.manifest |
File version |
Not applicable |
File size |
2,250 |
Date (UTC) |
09-Mar-2012 |
Time (UTC) |
6:24 |
Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008
File name |
Amd64_iscsi.inf_31bf3856ad364e35_6.0.6002.22814_none_9b4bb422c24c7d25.manifest |
File version |
Not applicable |
File size |
2,252 |
Date (UTC) |
09-Mar-2012 |
Time (UTC) |
6:24 |
Additional files for all supported IA-64-based versions of Windows Vista and of Windows Server 2008
File name |
Ia64_iscsi.inf_31bf3856ad364e35_6.0.6002.22814_none_3f2ebc9509ed14eb.manifest |
File version |
Not applicable |
File size |
2,251 |
Date (UTC) |
09-Mar-2012 |
Time (UTC) |
6:24 |
Additional file information for Windows 7 and for Windows Server 2008 R2
Additional files for all supported x86-based versions of Windows 7
File name |
X86_iscsi.inf_31bf3856ad364e35_6.1.7600.16975_none_3ca4f72754f21a98.manifest |
File version |
Not applicable |
File size |
2,456 |
Date (UTC) |
08-Mar-2012 |
Time (UTC) |
12:30 |
File name |
X86_iscsi.inf_31bf3856ad364e35_6.1.7600.21165_none_3d393c006e07d1b3.manifest |
File version |
Not applicable |
File size |
2,456 |
Date (UTC) |
08-Mar-2012 |
Time (UTC) |
12:30 |
File name |
X86_iscsi.inf_31bf3856ad364e35_6.1.7601.17792_none_3e72b377522b7261.manifest |
File version |
Not applicable |
File size |
2,456 |
Date (UTC) |
08-Mar-2012 |
Time (UTC) |
12:30 |
File name |
X86_iscsi.inf_31bf3856ad364e35_6.1.7601.21938_none_3f43336c6b12ffb6.manifest |
File version |
Not applicable |
File size |
2,456 |
Date (UTC) |
08-Mar-2012 |
Time (UTC) |
12:30 |
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File name |
Amd64_iscsi.inf_31bf3856ad364e35_6.1.7600.16975_none_98c392ab0d4f8bce.manifest |
File version |
Not applicable |
File size |
2,460 |
Date (UTC) |
08-Mar-2012 |
Time (UTC) |
12:51 |
File name |
Amd64_iscsi.inf_31bf3856ad364e35_6.1.7600.21165_none_9957d784266542e9.manifest |
File version |
Not applicable |
File size |
2,460 |
Date (UTC) |
08-Mar-2012 |
Time (UTC) |
12:51 |
File name |
Amd64_iscsi.inf_31bf3856ad364e35_6.1.7601.17792_none_9a914efb0a88e397.manifest |
File version |
Not applicable |
File size |
2,460 |
Date (UTC) |
08-Mar-2012 |
Time (UTC) |
12:51 |
File name |
Amd64_iscsi.inf_31bf3856ad364e35_6.1.7601.21938_none_9b61cef0237070ec.manifest |
File version |
Not applicable |
File size |
2,460 |
Date (UTC) |
08-Mar-2012 |
Time (UTC) |
12:51 |
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File name |
Ia64_iscsi.inf_31bf3856ad364e35_6.1.7600.16975_none_3ca69b1d54f02394.manifest |
File version |
Not applicable |
File size |
2,458 |
Date (UTC) |
08-Mar-2012 |
Time (UTC) |
12:27 |
File name |
Ia64_iscsi.inf_31bf3856ad364e35_6.1.7600.21165_none_3d3adff66e05daaf.manifest |
File version |
Not applicable |
File size |
2,458 |
Date (UTC) |
08-Mar-2012 |
Time (UTC) |
12:27 |
File name |
Ia64_iscsi.inf_31bf3856ad364e35_6.1.7601.17792_none_3e74576d52297b5d.manifest |
File version |
Not applicable |
File size |
2,458 |
Date (UTC) |
08-Mar-2012 |
Time (UTC) |
12:27 |
File name |
Ia64_iscsi.inf_31bf3856ad364e35_6.1.7601.21938_none_3f44d7626b1108b2.manifest |
File version |
Not applicable |
File size |
2,458 |
Date (UTC) |
08-Mar-2012 |
Time (UTC) |
12:27 |