Symptoms

Consider the following scenario:

  • You deploy a failover cluster in a Windows Server 2008 R2 or Windows Server 2012 environment.

  • You enable the Volume Shadow Copy Service on a cluster disk.

  • You replace a host bus adapter (HBA) on a cluster node.

  • You restart the cluster node.

In this scenario, the cluster node freezes.

Cause

This issue is triggered by a deadlock that occurs when the computer restarts.

Resolution

Update information for Windows Server 2012

To resolve this issue in Windows Server 2012, install update rollup 2855336. For more information about how to obtain this update rollup package, click the following article number to view the article in the Microsoft Knowledge Base:

2855336 Windows RT, Windows 8, and Windows Server 2012 update rollup: July 2013

Hotfix information for Windows Server 2008 R2

To resolve this issue in Windows Server 2008 R2, install the hotfix that is described in this article.

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 website:

http://support.microsoft.com/contactus/?ws=supportNote 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 R2 or Windows Server 2008 R2 Service Pack 1 (SP1). For more information about how to obtain a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to change the registry.

Restart requirement

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 R2 file information notesImportant Windows 7 hotfixes and Windows Server 2008 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 7/Windows Server 2008 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:

    Version

    Product

    Milestone

    Service branch

    6.1.760
    0.17xxx

    Windows Server 2008 R2

    RTM

    GDR

    6.1.760
    0.21xxx

    Windows Server 2008 R2

    RTM

    LDR

    6.1.760
    1.17xxx

    Windows Server 2008 R2

    SP1

    GDR

    6.1.760
    1.22xxx

    Windows Server 2008 R2

    SP1

    LDR

  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.

  • The MANIFEST files (.manifest) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. 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 x64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Volsnap.sys

6.1.7600.17089

295,280

02-Aug-2012

18:08

Volsnap.sys

6.1.7600.21291

296,288

02-Aug-2012

18:06

Volsnap.sys

6.1.7601.17920

296,288

02-Aug-2012

18:10

Volsnap.sys

6.1.7601.22077

296,816

02-Aug-2012

17:59

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Volsnap.sys

6.1.7600.17089

676,720

02-Aug-2012

16:54

Volsnap.sys

6.1.7600.21291

678,240

02-Aug-2012

16:48

Volsnap.sys

6.1.7601.17920

679,280

02-Aug-2012

16:47

Volsnap.sys

6.1.7601.22077

681,328

02-Aug-2012

16:45


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

For more information about the fix for this issue in Windows Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:

2706774 Cluster nodes stop responding in a Windows Server 2008 environment

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2

File name

Amd64_volume.inf_31bf3856ad364e35_6.1.7600.17089_none_71af8dd615c288fc.manifest

File version

Not applicable

File size

2,087

Date (UTC)

02-Aug-2012

Time (UTC)

18:25

File name

Amd64_volume.inf_31bf3856ad364e35_6.1.7600.21291_none_72265a4b2eef7726.manifest

File version

Not applicable

File size

2,087

Date (UTC)

02-Aug-2012

Time (UTC)

20:10

File name

Amd64_volume.inf_31bf3856ad364e35_6.1.7601.17920_none_73cdf37412c0303f.manifest

File version

Not applicable

File size

2,087

Date (UTC)

02-Aug-2012

Time (UTC)

18:37

File name

Amd64_volume.inf_31bf3856ad364e35_6.1.7601.22077_none_742858e52c00433a.manifest

File version

Not applicable

File size

2,087

Date (UTC)

02-Aug-2012

Time (UTC)

18:21

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File name

Ia64_volume.inf_31bf3856ad364e35_6.1.7600.17089_none_159296485d6320c2.manifest

File version

Not applicable

File size

2,085

Date (UTC)

02-Aug-2012

Time (UTC)

18:25

File name

Ia64_volume.inf_31bf3856ad364e35_6.1.7600.21291_none_160962bd76900eec.manifest

File version

Not applicable

File size

2,085

Date (UTC)

02-Aug-2012

Time (UTC)

20:07

File name

Ia64_volume.inf_31bf3856ad364e35_6.1.7601.17920_none_17b0fbe65a60c805.manifest

File version

Not applicable

File size

2,085

Date (UTC)

02-Aug-2012

Time (UTC)

18:13

File name

Ia64_volume.inf_31bf3856ad364e35_6.1.7601.22077_none_180b615773a0db00.manifest

File version

Not applicable

File size

2,085

Date (UTC)

02-Aug-2012

Time (UTC)

18:07


Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×