Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

A 32-bit iSCSI provider cannot retrieve an instance of MSiSCSIInitiator_PersistentDevice in 64-bit versions of Windows 7 or of Windows Server 2008 R2


View products that this article applies to.

Symptoms

You run a 32-bit Internet SCSI (iSCSI) provider on a computer that is running a 64-bit version of Windows 7 or of Windows Server 2008 R2.

In this scenario, the application does not retrieve the instance of MSiSCSIInitiator_PersistentDevice.

For example, in Windows Server 2008 R2, you run wbemtest32.exe, and this file is copied from a 32-bit version of the Windows Server 2003 operating system.

↑ Back to the top


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: 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.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You have to 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) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MANIFEST files and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. 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
File nameFile versionFile sizeDateTimePlatform
Iscsicli.exe6.1.7600.20798144,89611-Sep-201007:21x86
Iscsidsc.dll6.1.7600.2079850,68811-Sep-201007:22x86
Iscsied.dll6.1.7600.207988,19211-Sep-201007:22x86
Iscsiexe.dll6.1.7600.20798114,68811-Sep-201007:22x86
Iscsium.dll6.1.7600.2079828,67211-Sep-201007:22x86
Iscsiwmi.dll6.1.7600.2079866,04811-Sep-201007:22x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Iscsicli.exe6.1.7600.20798152,06411-Sep-201008:40x64
Iscsidsc.dll6.1.7600.2079877,31211-Sep-201008:44x64
Iscsied.dll6.1.7600.2079810,24011-Sep-201008:44x64
Iscsiexe.dll6.1.7600.20798156,67211-Sep-201008:44x64
Iscsium.dll6.1.7600.2079837,37611-Sep-201008:44x64
Iscsiwmi.dll6.1.7600.2079889,08811-Sep-201008:44x64
Iscsicli.exe6.1.7600.20798144,89611-Sep-201007:21x86
Iscsidsc.dll6.1.7600.2079850,68811-Sep-201007:22x86
Iscsied.dll6.1.7600.207988,19211-Sep-201007:22x86
Iscsium.dll6.1.7600.2079828,67211-Sep-201007:22x86
Iscsiwmi.dll6.1.7600.2079866,04811-Sep-201007:22x86
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Iscsicli.exe6.1.7600.20798196,60811-Sep-201007:03IA-64
Iscsidsc.dll6.1.7600.20798143,87211-Sep-201007:04IA-64
Iscsied.dll6.1.7600.2079816,38411-Sep-201007:04IA-64
Iscsiexe.dll6.1.7600.20798315,39211-Sep-201007:04IA-64
Iscsium.dll6.1.7600.2079878,33611-Sep-201007:04IA-64
Iscsiwmi.dll6.1.7600.20798182,78411-Sep-201007:04IA-64
Iscsicli.exe6.1.7600.20798144,89611-Sep-201007:21x86
Iscsidsc.dll6.1.7600.2079850,68811-Sep-201007:22x86
Iscsied.dll6.1.7600.207988,19211-Sep-201007:22x86
Iscsium.dll6.1.7600.2079828,67211-Sep-201007:22x86
Iscsiwmi.dll6.1.7600.2079866,04811-Sep-201007:22x86

↑ Back to the top


Workaround

Workaround for Windows 7 and for Windows Server 2008 R2

To work around this issue, you can specify the two following context flags to change the default behavior:
  • __ProviderArchitecture
  • __RequiredArchitecture
For more information, visit the following Microsoft webpage:

↑ Back to the top


Status

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

↑ Back to the top


More Information

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

824684 Description of the standard terminology that is used to describe Microsoft software updates

For more information, visit the following Microsoft webpages:

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
File nameX86_8a9f892124abf6bcc6c53cedd846e845_31bf3856ad364e35_6.1.7600.20798_none_a0752e44f16884f9.manifest
File versionNot applicable
File size711
Date (UTC)11-Sep-2010
Time (UTC)11:46
PlatformNot applicable
File nameX86_microsoft-windows-i..i_initiator_service_31bf3856ad364e35_6.1.7600.20798_none_dacbd4d08f8e84eb.manifest
File versionNot applicable
File size22,990
Date (UTC)11-Sep-2010
Time (UTC)07:52
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_7bbd5b27984fecb8cf1dc16527a8bea4_31bf3856ad364e35_6.1.7600.20798_none_585b712325848228.manifest
File versionNot applicable
File size715
Date (UTC)11-Sep-2010
Time (UTC)11:46
PlatformNot applicable
File nameAmd64_b10a463a67bb6651aed7c6063226f763_31bf3856ad364e35_6.1.7600.20798_none_3f4abcba2008fdd7.manifest
File versionNot applicable
File size1,072
Date (UTC)11-Sep-2010
Time (UTC)11:46
PlatformNot applicable
File nameAmd64_c6bbfed520e0a7834858a2da93d4966b_31bf3856ad364e35_6.1.7600.20798_none_1c2b23bae7ddd07a.manifest
File versionNot applicable
File size715
Date (UTC)11-Sep-2010
Time (UTC)11:46
PlatformNot applicable
File nameAmd64_microsoft-windows-i..i_initiator_service_31bf3856ad364e35_6.1.7600.20798_none_36ea705447ebf621.manifest
File versionNot applicable
File size22,994
Date (UTC)11-Sep-2010
Time (UTC)09:18
PlatformNot applicable
File nameWow64_microsoft-windows-i..i_initiator_service_31bf3856ad364e35_6.1.7600.20798_none_413f1aa67c4cb81c.manifest
File versionNot applicable
File size8,503
Date (UTC)11-Sep-2010
Time (UTC)07:44
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_274fc7954d048882ccaa35c18ee513b5_31bf3856ad364e35_6.1.7600.20798_none_c651225689affe54.manifest
File versionNot applicable
File size713
Date (UTC)11-Sep-2010
Time (UTC)11:46
PlatformNot applicable
File nameIa64_7bbd5b27984fecb8cf1dc16527a8bea4_31bf3856ad364e35_6.1.7600.20798_none_fc3e79956d2519ee.manifest
File versionNot applicable
File size714
Date (UTC)11-Sep-2010
Time (UTC)11:46
PlatformNot applicable
File nameIa64_microsoft-windows-i..i_initiator_service_31bf3856ad364e35_6.1.7600.20798_none_dacd78c68f8c8de7.manifest
File versionNot applicable
File size22,992
Date (UTC)11-Sep-2010
Time (UTC)08:47
PlatformNot applicable
File nameWow64_microsoft-windows-i..i_initiator_service_31bf3856ad364e35_6.1.7600.20798_none_413f1aa67c4cb81c.manifest
File versionNot applicable
File size8,503
Date (UTC)11-Sep-2010
Time (UTC)07:44
PlatformNot applicable

↑ Back to the top


Keywords: kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 2410263
Revision : 2
Created on : 9/20/2018
Published on : 9/20/2018
Exists online : False
Views : 226