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

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.

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 now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

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

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

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

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, theTimeOutValue 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.