Cluster servers may experience connection timeouts to drives after you install or upgrade to the Windows Clustering feature in Windows Server 2003
This article has been archived. It is offered "as is" and will no longer be updated.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
When you install the Windows Clustering feature in Windows Server 2003 on your cluster servers or when you upgrade your cluster servers to the Windows Clustering feature in Windows Server 2003 from an earlier cluster installation, the disk time-out values in the registry are overwritten. This process may cause the storage system to be unstable and to not function correctly. Some host bus adapters (HBAs) use a port-down retry count of 45 seconds. This means that Windows Server 2003 begins issuing resets (logical unit number [LUN], target, bus) before the HBA can time out and then start its recovery process for a port that is down (for example, a bad switch port or a cable removal). This may prevent a multiple path failover, or it may cause the cluster to lose its reservation on that node.
This problem occurs because Windows Clustering in Windows Server 2003 sets the
TimeOutValueregistry value in the following registry key to 20 seconds when it is installed:
This setting tells the storage drivers how long to wait with an input/output (I/O) before treating it as failed and then flushing the I/O by using a bus reset.
Hotfix informationNote If the Cluster service is already installed, if you apply this fix or Windows Server 2003 Service Pack 1 (SP1), you must also use one of the workarounds that is described later in this article.
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 this specific problem. 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.
PrerequisitesNo prerequisites are required.
Restart requirementYou do not have to restart your computer after you apply this hotfix. However, if you are also using one of the workaround methods that are described later in this article, you must restart your computer after you change the registry value or after you reinstall the drivers for the changes to take effect.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Size File name ---------------------------------------------- 29-May-2003 21:39 16,247 Clcfgsrv.inf 29-May-2003 21:41 18,525 Clusocm.inf
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
To work around this problem, use either of the methods that follow. Use these methods only if your computer is experiencing the problem that is described in the "Symptoms" section of this article.
Method 1WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
TimeOutValueregistry value (this is a DWORD value) in the following registry subkey to the previous value:
Method 2Reinstall the driver for the HBA or the RAID controller that requires the longer time-out value. When you reinstall the drivers, the
TimeOutValueregistry value is overwritten with the value that those drivers need. You may have to contact the hardware vendor to find out the correct
TimeOutValueregistry value for your configuration.
Win2k3 Win2003 Dell EMC Powervault
Article ID: 818877 - Last Review: 02/27/2014 21:18:40 - Revision: 10.11
Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Datacenter Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise x64 Edition, Microsoft Windows Server 2003, 64-Bit Datacenter Edition
- kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbbug kbfix kbqfe kbwinserv2003presp1fix KB818877