Resource Monitor stops responding and then restarts when there is a deadlock condition in Windows Server 2003

The Resource Monitor deadlock detection feature in Microsoft Windows Server 2003 detects a deadlock condition. Then, Resource Monitor stops responding (hangs) and then restarts. However, you lose all the Volume Shadow Copy Service (VSS) snapshots. Additionally, you cannot detect the reason for the deadlock condition.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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

To apply this hotfix, you must have Windows Server 2003 Service Pack 1 installed on the computer.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.

Windows Server 2003, x86-based versions

Microsoft Windows Server 2003, Itanium-based versions

Windows Server 2003, x64-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

The Resource Monitor process (Resrcmon.exe) is a child process of the Cluster service process (Clussvc.exe). The hotfix that is mentioned in the "Resolution" section lets you generate user dump files for Resrcmon.exe and for Clussvc.exe when Resource Monitor detects a deadlock. These dump files are located in the %Systemroot%\Cluster folder. The user dump file for Resrcmon.exe is named "Resrcmon.dmp." The user dump file for Clussvc.exe is named "Clussvc.dmp."

The ResourceDllDeadlockThreshold value affects dump file generation as follows:

• If the ResourceDllDeadlockThreshold value equals zero, dump files are generated for Resrcmon.exe and for Clussvc.exe.
• If the ResourceDllDeadlockThreshold value is more than zero, a user dump file is generated for Resrcmon.exe. However, a user dump file for Clussvc.exe is generated only when the deadlock time exceeds the ResourceDllDeadlockThreshold value.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: For more information about how to enable user mode hang detection on a server cluster, click the following article number to view the article in the Microsoft Knowledge Base: