You configure a failover cluster on some computers that are running Windows Server 2008 Service Pack 2 (SP2).
You use the No Majority: Disk Only quorum mode in the cluster.
The node that owns the cluster group that has a quorum disk resource tries to stop the Cluster service.
In this scenario, the Cluster outage occurs on all nodes.
Additionally, an instance of event ID 7024 that resembles the following is logged in the System log:
Log Name: System Source: Service Control Manager Date: date Event ID: 7024 Task Category: None Level: Error Keywords: Classic User: N/A Computer: computer name Description: The Cluster Service service terminated with service-specific error 5925 (0x1725)
This issue occurs because of a deadlock that causes a timer to expire. This timer terminates the Cluster services.
The timer that terminates the Cluster services is set when the quorum disk resource is offline on a node. The Cluster service on the cluster node that owns the quorum disk resource enters a deadlock state during the shutdown process. However, the Cluster services on all nodes fail if the quorum disk resource is not online on another node when the timer expires. Therefore, the Cluster services on all nodes fail when the quorum disk resource is not online when the timer expires.
Note This timer that terminates the Cluster services is called "death timer" in the Cluster logs.
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:
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.
To apply this hotfix, you must be running Windows Server 2008 SP2 on the computer. Additionally, the failover cluster feature must be installed on the computer.
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The global 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 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
6.0.600 2. 22xxx
Windows Vista and Windows Server 2008
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008
For all supported x64-based versions of Windows Server 2008
For all supported IA-64-based versions of Windows Server 2008
Workaround for Windows Server 2008
To work around this issue, increase the value for the QuorumArbitrationTimeMax setting. To set the value for the QuorumArbitrationTimeMax setting explicitly, at the command prompt, type the following command, and then press ENTER:
cluster /prop quorumarbitrationtimemax=90
Note The value of this setting depends on the environment. Therefore, the value may have to be adjusted to a larger value. If you increase the value to 120, and if this issue still occurs, install this hotfix because this workaround cannot resolve the issue.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the cluster command, visit the following Microsoft Web site:
The following is a sample of the Cluster log when the issue occurs:
00000264.00000938::2009/08/04-19:03:00.727 INFO [QUORUM] Node 3: quorum is arbitrated by node 100000264.00000938::2009/08/04-19:06:10.379 INFO [QUORUM] Node 3: quorum is not owned by anyone00000264.00000938::2009/08/04-19:06:10.379 WARN [QUORUM] Node 3: One off quorum (1 2 3)00000264.00000938::2009/08/04-19:06:10.379 INFO [QUORUM] Node 3: death timer is started at 2009/08/04-19:06:10.379 and expires in 20 seconds00000264.00001b3c::2009/08/04-19:06:31.357 ERR [QUORUM] Node 3: Death timer expired after 20 seconds (death timer started at 2009/08/04-19:06:10.379). Lost quorum.00000264.00001b3c::2009/08/04-19:06:31.357 ERR lost quorum (status = 5925)00000264.00001b3c::2009/08/04-19:06:31.357 ERR FatalError is Calling Exit Process.00000264.00000734::2009/08/04-19:06:31.358 INFO [CS] About to exit process...