Select the product you need help with

Access to an MPIO-controlled storage device fails after you disconnect all data cables in Windows Server 2003

Article ID: 982109 - View products that this article applies to.

Hotfix Download Available

Expand all | Collapse all

SYMPTOMS

Consider the following scenario:

You connect a storage device that is controlled by Microsoft Multipath I/O (MPIO) to a computer that is running Windows Server 2003.
You use a Microsoft or a third-party device specific module for MPIO.
All data connections to the storage device are removed.

In this scenario, you cannot access the storage device even when the cables are reconnected. Additionally, the applications that try to access the storage device may stop responding. This issue persists until you restart the computer.

Back to the top | Give Feedback

CAUSE

This issue occurs because the Mpio.sys driver moves the disks or pseudo-logical unit numbers (LUNs) to an incorrect state queue when all MPIO paths fail. This behavior causes the I/O requests (IRPs) that are through the iSCSI targets to be delayed until the computer is restarted.

Back to the top | Give Feedback

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 Web site:

http://support.microsoft.com/contactus/?ws=support

(http://support.microsoft.com/contactus/?ws=support)

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 Server 2003 Service Pack 2 (SP2).

For more information about how to obtain a Windows Server 2003 service pack or a Windows XP Professional x64 Edition service pack, click the following article number to view the article in the Microsoft Knowledge Base:

889100

(http://support.microsoft.com/kb/889100/ )

How to obtain the latest service pack for Windows Server 2003

Registry information

To use the hotfix in this package, 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 English (United States) 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 Server 2003 file information notes

In addition to the files that are listed in these tables, this hotfix also installs an associated security catalog file (KBnumber.cat) that is signed with a Microsoft digital signature.