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.

Cluster servers may experience connection timeouts to drives after you install or upgrade to the Windows Clustering feature in Windows Server 2003


View products that this article applies to.

Symptoms

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.

↑ Back to the top


Cause

This problem occurs because Windows Clustering in Windows Server 2003 sets the
TimeOutValue
registry value in the following registry key to 20 seconds when it is installed:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Disk
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.

↑ Back to the top


Resolution

Hotfix information

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

Prerequisites

No prerequisites are required.

Restart requirement

You 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 information

This hotfix does not replace any other hotfixes.

File information

The 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

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

↑ Back to the top


Workaround

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 1

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

Change the
TimeOutValue
registry value (this is a DWORD value) in the following registry subkey to the previous value:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Disk

Method 2

Reinstall the driver for the HBA or the RAID controller that requires the longer time-out value. When you reinstall the drivers, the
TimeOutValue
registry value is overwritten with the value that those drivers need. You may have to contact the hardware vendor to find out the correct
TimeOutValue
registry value for your configuration.

↑ Back to the top


Keywords: kbhotfixserver, kbqfe, kbbug, kbfix, kbqfe, kbwinserv2003presp1fix, kbautohotfix, KB818877

↑ Back to the top

Article Info
Article ID : 818877
Revision : 21
Created on : 7/24/2007
Published on : 7/24/2007
Exists online : False
Views : 134