Microsoft KB Archive Search

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.

  1. Home
  2. Cluster services go offline when there's a connectivity issue in Windows Server 2012 R2 or Windows Server 2012

Cluster services go offline when there's a connectivity issue in Windows Server 2012 R2 or Windows Server 2012

View products that this article applies to.

This article describes an issue that occurs on a Windows Server 2012 R2 or Windows Server 2012-based failover cluster. A hotfix is available to fix this issue. The hotfix has a prerequisite.

↑ Back to the top

Symptoms

Consider the following scenario:
  • You have a failover cluster and the cluster spans two datacenters with different network subnets.
  • Node weight and quorum is configured to make sure that the primary datacenter would remain primary.
  • A connectivity issue occurs between datacenters.
In this scenario, the cluster nodes in both datacenters lose quorum and fail. All services in the quorum go offline. The expected behavior is that if there are connectivity issues, one of the datacenters loses quorum and stops the cluster service, while the nodes in the other datacenter continue to function as the cluster.

↑ Back to the top

Hotfix information

Important If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this hotfix. For more information, see Add language packs to Windows.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that's described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there's a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to get 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 don't qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you don't see your language, it's because a hotfix is not available for that language.

Prerequisites

To apply this hotfix in Windows Server 2012 R2, you must install April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355).

Registry information

To use the hotfix in this package, you don't have to make any changes to the registry.

Restart requirement

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

Hotfix replacement information

This hotfix doesn't 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 2012 R2 file information and notes

Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" 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, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    VersionProductMilestoneService branch
    6.3.960 0.17xxxWindows Server 2012 R2RTMGDR
  • 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 2012 R2" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Clussvc.exe6.3.9600.179997,517,69629-Jul-201514:28x64

Windows Server 2012 file information and notes

Important Windows 8 hotfixes and Windows Server 2012 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8/Windows Server 2012" 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, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    VersionProductMilestoneService branch
    6.2.920 0.21xxxWindows Server 2012RTMLDR
  • 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 2012" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Clussvc.exe6.2.9200.215787,300,09601-Aug-201514:33x64

Additional file information

Additional file information for Windows Server 2012 R2
Additional files for all supported x64-based versions of Windows Server 2012 R2
File propertyValue
File nameAmd64_e4485429753ea20f0e9ecb01dc0c556d_31bf3856ad364e35_6.3.9600.17999_none_989d9b7912c0b9d3.manifest
File versionNot applicable
File size1,072
Date (UTC)29-Jul-2015
Time (UTC)22:50
PlatformNot applicable
File nameAmd64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.3.9600.17999_none_aa7a2f7a75867743.manifest
File versionNot applicable
File size9,346
Date (UTC)29-Jul-2015
Time (UTC)15:25
PlatformNot applicable
File nameWow64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.3.9600.17999_none_b4ced9cca9e7393e.manifest
File versionNot applicable
File size6,410
Date (UTC)29-Jul-2015
Time (UTC)15:17
PlatformNot applicable
Additional file information for Windows Server 2012
Additional files for all supported x64-based versions of Windows Server 2012
File propertyValue
File nameAmd64_04e3dd5408e1c7e736766cfa490a9046_31bf3856ad364e35_6.2.9200.21579_none_f3e8d52f2294ad9e.manifest
File versionNot applicable
File size715
Date (UTC)02-Aug-2015
Time (UTC)18:37
PlatformNot applicable
File nameAmd64_06cb0a7985a1ca80488c2aac42b33f55_31bf3856ad364e35_6.2.9200.21579_none_b3ba1e00e248ccab.manifest
File versionNot applicable
File size723
Date (UTC)02-Aug-2015
Time (UTC)18:37
PlatformNot applicable
File nameAmd64_092509b2ee4a41230d0603698df7feaf_31bf3856ad364e35_6.2.9200.21579_none_6cfd58edce7bfde7.manifest
File versionNot applicable
File size723
Date (UTC)02-Aug-2015
Time (UTC)18:37
PlatformNot applicable
File nameAmd64_0fba1e0e29f4575627e18b36e2d1a2e0_31bf3856ad364e35_6.2.9200.21579_none_eb3126cb8b30db96.manifest
File versionNot applicable
File size723
Date (UTC)02-Aug-2015
Time (UTC)18:37
PlatformNot applicable
File nameAmd64_1678ef39807d11acffc73ee6e285f652_31bf3856ad364e35_6.2.9200.21579_none_f5a48013f28d7926.manifest
File versionNot applicable
File size723
Date (UTC)02-Aug-2015
Time (UTC)18:37
PlatformNot applicable
File nameAmd64_2a2df5e8a158e95dea1efab20f2d227c_31bf3856ad364e35_6.2.9200.21579_none_725583bc6a9d51c6.manifest
File versionNot applicable
File size723
Date (UTC)02-Aug-2015
Time (UTC)18:37
PlatformNot applicable
File nameAmd64_38789e09c9abe1afa16d3b41409a4552_31bf3856ad364e35_6.2.9200.21579_none_94ec1a21e75a3f7f.manifest
File versionNot applicable
File size723
Date (UTC)02-Aug-2015
Time (UTC)18:37
PlatformNot applicable
File nameAmd64_4d8edf59ea537b45f256a6456638fa58_31bf3856ad364e35_6.2.9200.21579_none_d94032dede71de83.manifest
File versionNot applicable
File size723
Date (UTC)02-Aug-2015
Time (UTC)18:37
PlatformNot applicable
File nameAmd64_6249383f7a61229a24153d243e36b3b3_31bf3856ad364e35_6.2.9200.21579_none_b37ad4b217677d5a.manifest
File versionNot applicable
File size723
Date (UTC)02-Aug-2015
Time (UTC)18:37
PlatformNot applicable
File nameAmd64_650515e106ffeb976e77bf93ea013445_31bf3856ad364e35_6.2.9200.21579_none_157dd2c998dd6a5b.manifest
File versionNot applicable
File size715
Date (UTC)02-Aug-2015
Time (UTC)18:37
PlatformNot applicable
File nameAmd64_67613c1cba3a3dadff827ac3d97a32bd_31bf3856ad364e35_6.2.9200.21579_none_c1f2cb97c33845fd.manifest
File versionNot applicable
File size723
Date (UTC)02-Aug-2015
Time (UTC)18:37
PlatformNot applicable
File nameAmd64_b5ad8eab1456fa4023839407375f875c_31bf3856ad364e35_6.2.9200.21579_none_294f5f7ac1c1276f.manifest
File versionNot applicable
File size723
Date (UTC)02-Aug-2015
Time (UTC)18:37
PlatformNot applicable
File nameAmd64_b8c99126552d5f18d042ed13ff730434_31bf3856ad364e35_6.2.9200.21579_none_543ee12e1d7b7d34.manifest
File versionNot applicable
File size723
Date (UTC)02-Aug-2015
Time (UTC)18:37
PlatformNot applicable
File nameAmd64_c57089d00e047ed80d67d1fd96f6c604_31bf3856ad364e35_6.2.9200.21579_none_4e725bf77f2761d9.manifest
File versionNot applicable
File size723
Date (UTC)02-Aug-2015
Time (UTC)18:37
PlatformNot applicable
File nameAmd64_f982725857048d1541ab1d959a50ff01_31bf3856ad364e35_6.2.9200.21579_none_3cf16fc2c02c60b8.manifest
File versionNot applicable
File size723
Date (UTC)02-Aug-2015
Time (UTC)18:37
PlatformNot applicable
File nameAmd64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.2.9200.21579_none_1324a9f944611ceb.manifest
File versionNot applicable
File size9,894
Date (UTC)01-Aug-2015
Time (UTC)16:57
PlatformNot applicable
File nameWow64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.2.9200.21579_none_1d79544b78c1dee6.manifest
File versionNot applicable
File size6,676
Date (UTC)01-Aug-2015
Time (UTC)15:39
PlatformNot applicable

↑ Back to the top

Status

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

↑ Back to the top

References

See the terminology that Microsoft uses to describe software updates.

↑ Back to the top

Keywords: kbqfe, kbsurveynew, kbfix, kbautohotfix, kbhotfixserver, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 3076953
Revision : 1
Created on : 1/7/2017
Published on : 9/8/2015
Exists online : False
Views : 194