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

On This Page

This article describes an issue when TCP connections reconnect in Windows Server 2012 R2. A hotfix is available to resolve this issue. The hotfix has a prerequisite.

Symptoms

This issue occurs when a node of a failover cluster is removed from active cluster membership. Additionally, the following events are logged in the System log together with corresponding time stamps:

Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 07/08/2014 12:29:00 PM
Event ID: 1592
Task Category: Node-to-Node Communications

Level: Critical
Keywords:
User: SYSTEM
Computer: FC-NODE2.CONTOSO.COM
Description:
Cluster node 'FC-NODE2' lost communication with cluster node 'FC-NODE1'. Network communication was reestablished. This could be due to communication temporarily being blocked by a firewall or connection security policy update. If the problem persists and network communication are not reestablished, the cluster service on one or more nodes will stop. If that happens, run the Validate a Configuration wizard to check your network configuration. Additionally, check for hardware or software errors related to the network adapters on this node, and check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 07/08/2014 12:29:01 PM
Event ID: 1135
Task Category: Node Mgr
Level: Critical
Keywords:
User: SYSTEM
Computer: FC-NODE2.CONTOSO.COM

Description:
Cluster node 'FC-NODE2' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

Note The Computer, Date, and Cluster node values vary, depending on the environment.

Resolution

To resolve this issue, install the update rollup 2975719, or install the hotfix that is described in the "Hotfix information" section.

Update information

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2975719 August 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that 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, 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 do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must first install update 2919355 on Windows Server 2012 R2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2919355 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update: April 2014

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

Collapse this imageExpand this image
assets folding start collapsed
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 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:
    Collapse this tableExpand this table
    VersionProductMilestoneService branch
    6.3.960 0.17 xxxWindows 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
Collapse this imageExpand this image
assets folding start collapsed
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Clussvc.exe6.3.9600.171937,410,68829-May-201406:05x64
Collapse this imageExpand this image
assets folding end collapsed
Collapse this imageExpand this image
assets folding end collapsed

Status

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

More information

This issue occurs when a TCP connection breaks and then reconnects. A TCP acknowledgement is not received in the node-to-node communication on a Windows Server 2012 R2 failover cluster, and the node that does not receive the TCP acknowledgement is removed from the active failover cluster membership. Error 5023 is logged in the cluster.log file of the node that is removed from the active failover cluster membership. For example, the following error 5023 is logged in the cluster.log file on the FC-NODE2 node that corresponds to the previous System log:
00000b7c.00001254::2014/07/08-12:29:00.003 WARN [PULLER FC-NODE2] ReadObject failed with GracefulClose(1226)' because of 'channel to remote endpoint fe80::####:####:####:####%##:~49256~ is closed'.
00000b7c.00000fa8::2014/07/08-12:29:00.003 ERR [CORE] mscs::NodeObject::OnMessageReceived: (5023)' because of 'Can't remove sent messages from an empty sent messages queue.'
00000b7c.00000fa8::2014/07/08-12:29:00.003 ERR [NODE] Node 8: Error processing message from n1, starting Regroup.

Note
fe80::####:####:####:####%## represents the hexadecimal number that represents an IPv6 address.

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

Collapse this imageExpand this image
assets folding start collapsed

Additional file information for Windows Server 2012 R2

Additional files for all supported x64-based versions of Windows Server 2012 R2
Collapse this imageExpand this image
assets folding start collapsed
Collapse this tableExpand this table
File propertyValue
File nameAmd64_0d73dc007dc76763d947135e58a26bc5_31bf3856ad364e35_6.3.9600.17193_none_92a61bbf7946133c.manifest
File versionNot applicable
File size715
Date (UTC)30-May-2014
Time (UTC)04:58
File nameAmd64_43970e368a63681553f3e0cda8ab68b5_31bf3856ad364e35_6.3.9600.17193_none_6a885997b119d4f5.manifest
File versionNot applicable
File size723
Date (UTC)30-May-2014
Time (UTC)04:58
File nameAmd64_828cf525a061530f2e10a9bb524136b6_31bf3856ad364e35_6.3.9600.17193_none_775f45ed510659d6.manifest
File versionNot applicable
File size723
Date (UTC)30-May-2014
Time (UTC)04:58
File nameAmd64_965b6236d3ab05e942ac504dbe0c99f3_31bf3856ad364e35_6.3.9600.17193_none_759ad4771763590c.manifest
File versionNot applicable
File size723
Date (UTC)30-May-2014
Time (UTC)04:58
File nameAmd64_a1dfa607d2ef8c1a06fdbae1d4ecdfe8_31bf3856ad364e35_6.3.9600.17193_none_4fa6ffd8be4036e8.manifest
File versionNot applicable
File size723
Date (UTC)30-May-2014
Time (UTC)04:58
File nameAmd64_aa4d9c239f188594fe3153a6edeb503d_31bf3856ad364e35_6.3.9600.17193_none_977a17ae13354211.manifest
File versionNot applicable
File size723
Date (UTC)30-May-2014
Time (UTC)04:58
File nameAmd64_b98637cc530c89a87132a011c8603ade_31bf3856ad364e35_6.3.9600.17193_none_4295b75d65eb22d8.manifest
File versionNot applicable
File size723
Date (UTC)30-May-2014
Time (UTC)04:58
File nameAmd64_b998b79b864e712ca10189bd1da930c9_31bf3856ad364e35_6.3.9600.17193_none_269acca40631fafa.manifest
File versionNot applicable
File size723
Date (UTC)30-May-2014
Time (UTC)04:58
File nameAmd64_c41afcd20c2de8b9f7e112553d49054c_31bf3856ad364e35_6.3.9600.17193_none_14c3d229dbad7e55.manifest
File versionNot applicable
File size723
Date (UTC)30-May-2014
Time (UTC)04:58
File nameAmd64_cc5d420dedd97eaf20674ac1cded7c21_31bf3856ad364e35_6.3.9600.17193_none_35d0e289cee45a1d.manifest
File versionNot applicable
File size723
Date (UTC)30-May-2014
Time (UTC)04:58
File nameAmd64_dcdaf1485a500223b302cfb04f75e506_31bf3856ad364e35_6.3.9600.17193_none_00deeb1b469bd6b7.manifest
File versionNot applicable
File size723
Date (UTC)30-May-2014
Time (UTC)04:58
File nameAmd64_e378c260defd82b54eaf63eaeb646f4b_31bf3856ad364e35_6.3.9600.17193_none_7e688e80414a16ca.manifest
File versionNot applicable
File size723
Date (UTC)30-May-2014
Time (UTC)04:58
File nameAmd64_f03bd51905f72637224a88bd9dff1240_31bf3856ad364e35_6.3.9600.17193_none_8825fa88868c2ecd.manifest
File versionNot applicable
File size715
Date (UTC)30-May-2014
Time (UTC)04:58
File nameAmd64_fb9a5a02813e742129a31b668de7085a_31bf3856ad364e35_6.3.9600.17193_none_8726cf139f4e85c5.manifest
File versionNot applicable
File size723
Date (UTC)30-May-2014
Time (UTC)04:58
File nameAmd64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.3.9600.17193_none_aa741e8e758bf601.manifest
File versionNot applicable
File size9,490
Date (UTC)29-May-2014
Time (UTC)12:39
File nameWow64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.3.9600.17193_none_b4c8c8e0a9ecb7fc.manifest
File versionNot applicable
File size6,554
Date (UTC)29-May-2014
Time (UTC)10:00
Collapse this imageExpand this image
assets folding end collapsed
Collapse this imageExpand this image
assets folding end collapsed

Properties

Article ID: 2972254 - Last Review: August 12, 2014 - Revision: 6.0
Applies to
  • Windows Server 2012 R2 Datacenter
  • Windows Server 2012 R2 Essentials
  • Windows Server 2012 R2 Foundation
  • Windows Server 2012 R2 Standard
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseadvanced KB2972254

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