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.

"Access denied error" when Hyper-V Replica Broker goes online in a Windows Server 2012 or Windows Server 2012 R2 cluster


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a Windows Server 2012 R2 or Windows Server 2012 failover cluster that is in a domain, and the domain has a disjoint namespace. 
  • You set the primary Domain Name Service (DNS) suffix of the Windows Server 2012 failover cluster to the disjoint domain name.
  • You create a Hyper-V Replica Broker in the failover cluster, and then you bring the Hyper-V Replica Broker online. 
In this scenario, this issue occurs, and an error message that resembles the following is logged in the cluster log:
Virtual Machine Replication Broker <Hyper-V Replica Broker BROKER>: 'Hyper-V Replica Broker BROKER' failed to register the service principal name: General access denied error.

↑ Back to the top


How to obtain this update or hotfix

To resolve this issue, we have released hotfixes for Windows Server 2012 R2 and Windows Server 2012. We also have released update rollups for Windows Server 2012 R2 and Windows Server 2012.

Before you install this hotfix, check the prerequisite of the hotfix.

The update rollup fixes many other issues in addition to the issue that the hotfix fixes. We recommend that you use the update rollup. The update rollup is larger than the hotfix. Therefore, the update rollup takes longer to download.

Update for Windows Server 2012 R2 and Windows Server 2012

The following update rollup is available.

For Windows Server 2012 R2

For Windows Server 2012

Hotfix for Windows Server 2012 R2 and Windows Server 2012

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

Hotfix detail information

Prerequisites
To apply this hotfix, you must first install the update 2919355 on Windows 8.1, Windows RT 8.1, or 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 may have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.

↑ 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


More Information

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 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.17 xxx Windows 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
Vmclusres.dll6.3.9600.17211677,88814-Jun-201405:28x64

Windows Server 2012 file information notes

Important 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, SR_Level (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.17xxx Windows Server 2012RTMGDR
    6.2.920 0.21xxx Windows Server 2012RTMLDR
  • 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) 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
File nameFile versionFile sizeDateTimePlatform
Vmclusres.dll6.2.9200.17031674,30412-Jun-201423:19x64
Vmclusres.dll6.2.9200.21148674,30412-Jun-201423:19x64

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_c1048576c67265ad528c8465f9360a1a_31bf3856ad364e35_6.3.9600.17211_none_97f09fc9ce6182b9.manifest
File versionNot applicable
File size702
Date (UTC)14-Jun-2014
Time (UTC)19:54
PlatformNot applicable
File nameAmd64_microsoft-hyper-v-clustering_31bf3856ad364e35_6.3.9600.17211_none_9d3a2e8eb9696bb8.manifest
File versionNot applicable
File size48,550
Date (UTC)14-Jun-2014
Time (UTC)13:28
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_c6d1ecbd8a828ec76c12bdcf4b6ff913_31bf3856ad364e35_6.2.9200.17031_none_1960e2ca95c1ef10.manifest
File versionNot applicable
File size702
Date (UTC)14-Jun-2014
Time (UTC)00:17
PlatformNot applicable
File nameAmd64_fc8495ea059b6dbd179b40164862e650_31bf3856ad364e35_6.2.9200.21148_none_673f6dbfb7e94ddf.manifest
File versionNot applicable
File size702
Date (UTC)14-Jun-2014
Time (UTC)00:17
PlatformNot applicable
File nameAmd64_microsoft-hyper-v-clustering_31bf3856ad364e35_6.2.9200.17031_none_052fd2446f46d8cf.manifest
File versionNot applicable
File size48,206
Date (UTC)13-Jun-2014
Time (UTC)02:28
PlatformNot applicable
File nameAmd64_microsoft-hyper-v-clustering_31bf3856ad364e35_6.2.9200.21148_none_05b5a129886645eb.manifest
File versionNot applicable
File size48,206
Date (UTC)13-Jun-2014
Time (UTC)02:45
PlatformNot applicable

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

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 2976884
Revision : 1
Created on : 1/7/2017
Published on : 8/12/2014
Exists online : False
Views : 310