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. The Hyper-V host may be unable to reconnect to the Cluster Scale-Out File Server share after an unplanned failover in Windows 8 or Windows Server 2012

The Hyper-V host may be unable to reconnect to the Cluster Scale-Out File Server share after an unplanned failover in Windows 8 or Windows Server 2012

View products that this article applies to.

Symptoms

Consider the following scenarios.

Scenario 1
  • You deploy file storage by using Failover Clustering Scale-Out File Server shares in Windows 8 or Windows Server 2012.
  • An unexpected error causes the Cluster service process (clussvc.exe) to stop.

In this scenario, you may receive I/O errors instead of failing over to a working cluster node.

Scenario 2
  • You deploy Windows 8 or Windows Server 2012 Hyper-V hosts that run virtual machines that are stored on Failover Clustering Scale-Out File Server shares in Windows Server 2012.
  • An unplanned failover causes the Scale-Out File Server to move to another node.

In this scenario, the Hyper-V host may be unable to reconnect to the share. This causes the virtual machines to become unresponsive and to enter a critical state.

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is available from Microsoft Support. 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, 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 have Windows 8 or Windows Server 2012 installed.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

↑ Back to the top

File information
The English (United States) 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 8 and Windows Server 2012 file information and notes

Important Windows 8 and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" 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 8" 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.20 xxxWindows 8 and Windows 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 8 and Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely 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 x86-based versions of Windows 8
File nameFile versionFile sizeDateTimePlatform
Mrxsmb20.sys6.2.9200.20978167,42401-Mar-201407:12x86
Mrxsmb.sys6.2.9200.20978300,03201-Mar-201407:10x86
Srvnet.sys6.2.9200.20978195,07201-Mar-201407:09x86
Srv2.sys6.2.9200.20978495,61601-Mar-201407:11x86
Smbserver-ppdlic.xrm-msNot applicable3,12101-Mar-201408:56Not applicable
Srvsvc.dll6.2.9200.20978241,66401-Mar-201408:05x86
Sscore.dll6.2.9200.2097827,64801-Mar-201408:05x86

For all supported x64-based versions of Windows 8 and of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Clussvc.exe6.2.9200.209787,256,57601-Mar-201408:17x64
Mrxsmb20.sys6.2.9200.20978214,01601-Mar-201407:30x64
Mrxsmb.sys6.2.9200.20978358,40001-Mar-201407:28x64
Srvnet.sys6.2.9200.20978247,29601-Mar-201407:28x64
Srv2.sys6.2.9200.20978618,49601-Mar-201407:30x64
Smbserver-ppdlic.xrm-msNot applicable3,12101-Mar-201410:55Not applicable
Srvsvc.dll6.2.9200.20978308,73601-Mar-201408:17x64
Sscore.dll6.2.9200.2097836,35201-Mar-201408:17x64

Additional file information

Additional file information for Windows 8 and Windows Server 2012

Additional files for all supported x86-based versions of Windows 8
File propertyValue
File nameUpdate.mum
File versionNot applicable
File size1,787
Date (UTC)03-Mar-2014
Time (UTC)18:58
PlatformNot applicable
File nameX86_02921088e62ff8b08c971717a5b40887_31bf3856ad364e35_6.2.9200.20978_none_59bdc0422d0283cf.manifest
File versionNot applicable
File size698
Date (UTC)03-Mar-2014
Time (UTC)18:58
PlatformNot applicable
File nameX86_587ff5714dea3805d063fcb08b21f704_31bf3856ad364e35_6.2.9200.20978_none_31bd2ef3de16ee9f.manifest
File versionNot applicable
File size701
Date (UTC)03-Mar-2014
Time (UTC)18:58
PlatformNot applicable
File nameX86_61d7657912e6f94b292a363cc4dfcbb1_31bf3856ad364e35_6.2.9200.20978_none_f733eb1e8476ea16.manifest
File versionNot applicable
File size700
Date (UTC)03-Mar-2014
Time (UTC)18:58
PlatformNot applicable
File nameX86_ae7300f226f638d0e32a8bd0b9309113_31bf3856ad364e35_6.2.9200.20978_none_80e1fd7631f26804.manifest
File versionNot applicable
File size697
Date (UTC)03-Mar-2014
Time (UTC)18:58
PlatformNot applicable
File nameX86_c75a6438ebe3f92a8a585f5ae8e58f9c_31bf3856ad364e35_6.2.9200.20978_none_d79bb1fbba89cd6c.manifest
File versionNot applicable
File size704
Date (UTC)03-Mar-2014
Time (UTC)18:58
PlatformNot applicable
File nameX86_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.2.9200.20978_none_881e78d9743e80af.manifest
File versionNot applicable
File size4,096
Date (UTC)01-Mar-2014
Time (UTC)08:53
PlatformNot applicable
File nameX86_microsoft-windows-smbminirdr_31bf3856ad364e35_6.2.9200.20978_none_7cd4f0733b960edc.manifest
File versionNot applicable
File size57,195
Date (UTC)01-Mar-2014
Time (UTC)08:53
PlatformNot applicable
File nameX86_microsoft-windows-smbserver-common_31bf3856ad364e35_6.2.9200.20978_none_0119b171fa9fb670.manifest
File versionNot applicable
File size2,591
Date (UTC)01-Mar-2014
Time (UTC)08:53
PlatformNot applicable
File nameX86_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.2.9200.20978_none_d7301cace0f4537f.manifest
File versionNot applicable
File size207,155
Date (UTC)01-Mar-2014
Time (UTC)08:53
PlatformNot applicable
File nameX86_microsoft-windows-smbserver_31bf3856ad364e35_6.2.9200.20978_none_f6386c36d5541d4a.manifest
File versionNot applicable
File size51,278
Date (UTC)01-Mar-2014
Time (UTC)09:03
PlatformNot applicable


Additional files for all supported x64-based versions of Windows 8 and of Windows Server 2012
File nameAmd64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.2.9200.20978_none_1323c80f4461de8f.manifest
File versionNot applicable
File size10,086
Date (UTC)01-Mar-2014
Time (UTC)11:15
PlatformNot applicable
File nameAmd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.2.9200.20978_none_e43d145d2c9bf1e5.manifest
File versionNot applicable
File size4,100
Date (UTC)01-Mar-2014
Time (UTC)11:15
PlatformNot applicable
File nameAmd64_microsoft-windows-smbminirdr_31bf3856ad364e35_6.2.9200.20978_none_d8f38bf6f3f38012.manifest
File versionNot applicable
File size57,199
Date (UTC)01-Mar-2014
Time (UTC)11:15
PlatformNot applicable
File nameAmd64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.2.9200.20978_none_5d384cf5b2fd27a6.manifest
File versionNot applicable
File size2,593
Date (UTC)01-Mar-2014
Time (UTC)11:15
PlatformNot applicable
File nameAmd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.2.9200.20978_none_334eb8309951c4b5.manifest
File versionNot applicable
File size207,159
Date (UTC)01-Mar-2014
Time (UTC)11:15
PlatformNot applicable
File nameAmd64_microsoft-windows-smbserver_31bf3856ad364e35_6.2.9200.20978_none_525707ba8db18e80.manifest
File versionNot applicable
File size51,282
Date (UTC)01-Mar-2014
Time (UTC)11:05
PlatformNot applicable
File nameWow64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.2.9200.20978_none_1d78726178c2a08a.manifest
File versionNot applicable
File size6,868
Date (UTC)01-Mar-2014
Time (UTC)08:47
PlatformNot applicable
File nameWow64_microsoft-windows-smbserver_31bf3856ad364e35_6.2.9200.20978_none_5cabb20cc212507b.manifest
File versionNot applicable
File size46,276
Date (UTC)01-Mar-2014
Time (UTC)09:02
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

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 2937634
Revision : 1
Created on : 1/7/2017
Published on : 4/14/2014
Exists online : False
Views : 179