Monday, October 17, 2022

A hotfix that enables SQL Server availability groups support in Windows Server 2012 is available [MS]

Introduction

This article introduces a hotfix that changes the IP address resource behavior in failover clustering to enable SQL Server availability groups support in Windows Server 2012. The hotfix lets you use the loopback adapters in failover clustering, and stops the piling of IP addresses to the networking stack. After you install the hotfix, the LoopbackAdapterAllowed registry entry is provided to enable or disable the hotfix functionality. To enable the hotfix functionality, set the REG_DWORD value of the LoopbackAdapterAllowed registry entry to 1. To disable the hotfix functionality, set the REG_DWORD value to 0. The registry entry is located under the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClusSvc\Parameters

Resolution

This hotfix is also available at Microsoft Update Catalog.

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 this specific problem.

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, submit a request to 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 2012.

Registry information

To use the hotfix in this package, you do not have to make any changes to 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 2012 file information notesImportant Windows 8 hotfixes 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:

    Version

    Product

    Milestone

    Service branch

    6.2.920 0.20 xxx

    Windows Server 2012

    RTM

    LDR

  • 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 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 x64-based versions of Windows Server 2012

File name

File version

File size

Date

Time

Platform

Clusres.dll

6.2.9200.20687

2,463,232

13-Apr-2013

05:54

x64

Clussvc.exe

6.2.9200.20687

7,220,224

13-Apr-2013

05:57

x64

Clnetres.dll

6.2.9200.16384

70,144

26-Jul-2012

03:05

x64

Clusapi.dll

6.2.9200.16384

372,224

26-Jul-2012

03:05

x64

Resutils.dll

6.2.9200.20687

626,688

13-Apr-2013

05:56

x64

Clnetcfg.dll

6.2.9200.20687

780,288

13-Apr-2013

05:54

x64

Failoverclusters.common.dll

6.2.9200.20687

729,088

13-Apr-2013

06:23

x64




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

No comments:

Post a Comment

Search This Blog

Auto-correct problems with uppercase letters in Windows 8.1 and Windows Server 2012 R2 - Microsoft Support [MS]

Auto-correct problems with uppercase letters in Windows 8.1 and Windows Server 2012 R2 ...