The File Share Witness resource is in a failed state even though the File Share Witness directory is available, and quorum cannot be maintained in a Windows Server 2008 failover cluster

Article translations Article translations
Article ID: 978790 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You configure a Windows Server 2008 failover cluster to use a Node and File Share Majority quorum model.
  • The File Share Witness directory is not available. This behavior causes the File Share Witness resource to enter a failed state.
  • The File Share Witness directory becomes available later.
In this scenario, the File Share Witness resource remains in a failed state even though the File Share Witness directory is available. Additionally, when the File Share Witness resource is in a failed state but is needed to maintain the quorum, the cluster loses the quorum.

Note You expect the quorum to be maintained when the File Share Witness directory is available.

RESOLUTION

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 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:
http://support.microsoft.com/contactus/?ws=support
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 be running Windows Server 2008 or Windows Server 2008 Service Pack 2 (SP2) on the computer. Additionally, the computer must have the Failover Clustering feature enabled.
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
968849 How to obtain the latest service pack for Windows Server 2008

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

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
  • 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.
    Collapse this tableExpand this table
    VersionProductSR_LevelService branch
    6.0.600 1 . 22xxxWindows Server 2008SP1LDR
    6.0.600 2 . 22xxxWindows Server 2008SP2LDR
  • Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
  • 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 critical 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
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Clussvc.exe6.0.6001.225872,335,74422-Dec-200909:52x86
Clussvc.exe6.0.6002.222922,336,25622-Dec-200909:38x86
For all supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Clussvc.exe6.0.6001.225873,862,01622-Dec-200910:13x64
Clussvc.exe6.0.6002.222923,862,52822-Dec-200909:48x64
For all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Clussvc.exe6.0.6001.225876,465,53622-Dec-200909:58IA-64
Clussvc.exe6.0.6002.222926,466,04822-Dec-200909:45IA-64

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Update.mumNot applicable2,22623-Dec-200906:30Not applicable
X86_32b8027dc4f5d8ee4259cfe0f8ee4971_31bf3856ad364e35_6.0.6001.22587_none_3dcb6190b48d3d09.manifestNot applicable71123-Dec-200906:30Not applicable
X86_d4f0a3f3bedbf87f5a50232db0c5bbaf_31bf3856ad364e35_6.0.6002.22292_none_8389d15b88248542.manifestNot applicable71123-Dec-200906:30Not applicable
X86_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.0.6001.22587_none_b9fbd056bae3f2ef.manifestNot applicable15,11722-Dec-200915:49Not applicable
X86_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.0.6002.22292_none_bbd270e0b816e551.manifestNot applicable15,11722-Dec-200914:47Not applicable
Additional files for all supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Amd64_22b437110b41291829365181ef1076bd_31bf3856ad364e35_6.0.6002.22292_none_d6baab66874cce6f.manifestNot applicable1,07223-Dec-200906:30Not applicable
Amd64_f1a6f4cb0e2919dccf36195e7a7e0d02_31bf3856ad364e35_6.0.6001.22587_none_3ade11a9a44ad1a0.manifestNot applicable1,07223-Dec-200906:30Not applicable
Amd64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.0.6001.22587_none_161a6bda73416425.manifestNot applicable15,15522-Dec-200918:31Not applicable
Amd64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.0.6002.22292_none_17f10c6470745687.manifestNot applicable15,15522-Dec-200913:40Not applicable
Update.mumNot applicable2,24223-Dec-200906:30Not applicable
Wow64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.0.6001.22587_none_206f162ca7a22620.manifestNot applicable4,51022-Dec-200914:10Not applicable
Wow64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.0.6002.22292_none_2245b6b6a4d51882.manifestNot applicable4,51022-Dec-200914:36Not applicable
Additional files for all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Ia64_73f66b23b19da39286ea5a18b721efad_31bf3856ad364e35_6.0.6001.22587_none_a57a55ea9558c4e9.manifestNot applicable1,07023-Dec-200906:30Not applicable
Ia64_85374b61afec75d52ca1c20c9e6be550_31bf3856ad364e35_6.0.6002.22292_none_ff65385c926fb558.manifestNot applicable1,07023-Dec-200906:30Not applicable
Ia64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.0.6001.22587_none_b9fd744cbae1fbeb.manifestNot applicable15,13622-Dec-200919:19Not applicable
Ia64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.0.6002.22292_none_bbd414d6b814ee4d.manifestNot applicable15,13622-Dec-200913:37Not applicable
Update.mumNot applicable1,58123-Dec-200906:30Not applicable
Wow64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.0.6001.22587_none_206f162ca7a22620.manifestNot applicable4,51022-Dec-200914:10Not applicable
Wow64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.0.6002.22292_none_2245b6b6a4d51882.manifestNot applicable4,51022-Dec-200914:36Not applicable

Properties

Article ID: 978790 - Last Review: September 11, 2010 - Revision: 1.1
APPLIES TO
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Datacenter without Hyper-V
  • Windows Server 2008 Enterprise without Hyper-V
Keywords: 
kbclustering kbsurveynew kbexpertiseadvanced kbqfe kbautohotfix kbHotfixServer kbfix KB978790

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com