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. Cluster network name resource cannot be brought online when one of the domain controllers is partly down in Windows Server 2008 R2

Cluster network name resource cannot be brought online when one of the domain controllers is partly down in Windows Server 2008 R2

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a failover cluster that is running Windows Server 2008 R2 in a domain environment.
  • You have two domain controllers in the domain. For example, you have a primary domain controller DC1 and a secondary domain controller DC2 in the domain.
  • You create a cluster network name resource on DC1, and the cluster network name resource is brought online.
  • DC1 is partly down. More specifically, the Netlogon service on DC1 stops running, but the remote procedure call (RPC) service is still running.
In this scenario, the cluster network name resource cannot be brought online and goes to a "failed" state.

↑ Back to the top

Cause

This issue occurs because the system assumes that DC1 is running correctly when the RPC service is running. When a cluster network name resource is brought online for the first time, an Active Directory object is created on DC1. Then, when DC1 is partly down, the system tries to update the object, and the Cluster service tries to locate a writable domain controller by checking the cached entry. The system assumes that DC1 is running correctly by checking the RPC service. However, because the Netlogon service is not running on DC1, the object cannot be updated.

You can confirm the cause of this issue by checking the cluster log. If the issue has occurred, a message in the cluster log resembles the following:
INFO [RES] Network Name <NetResourceName>: Initiating the Network Name operation : 'Verifying computer object associated with network name resource ServiceOrApplicationName'
INFO [RES] Network Name <NetResourceName>: Trying to find computer account <ServiceOrApplicationName> object GUID(95df46f8a2b1f946ab38a303c58bf33c) on any available domain controller.
WARN [RES] Network Name <NetResourceName>: Search for existing computer account failed. status 8007203A
WARN [RES] Network Name <NetResourceName>: Couldn't get information from DC <FQDN>. status 1717
INFO [RES] Network Name <NetResourceName>: Trying to find object 95df46f8a2b1f946ab38a303c58bf33c on a PDC.
WARN [RES] Network Name <NetResourceName>: Search for existing computer account failed. status 8007203A
INFO [RES] Network Name <NetResourceName>: Unable to find object 95df46f8a2b1f946ab38a303c58bf33c on a PDC.
INFO [RES] Network Name <NetResourceName>: GetComputerObjectViaGUIDEx() failed, Status 8007203A.

Note The status code in the cluster log varies, depending on the configuration of the domain environment.

↑ Back to the top

Resolution

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 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=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 be running Windows Server 2008 R2 Service Pack 1 (SP1).

For more information about how to obtain a Windows 7 or 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 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.
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 2008 R2 file information notes
Important 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, 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.1.760
    1.18xxx    		Windows Server 2008 R2SP1GDR
    6.1.760
    1.22xxx    		Windows Server 2008 R2SP1LDR
  • 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 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. 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 nameFile versionFile sizeDateTimePlatform
Clusres.dll6.1.7601.181951,242,62428-Jun-201313:39x64
Clusres.dll6.1.7601.223701,280,51228-Jun-201305:11x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Clusres.dll6.1.7601.181952,070,01628-Jun-201312:26IA-64
Clusres.dll6.1.7601.223702,123,26428-Jun-201304:13IA-64

↑ 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

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

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File propertyValue
File nameAmd64_microsoft-windows-f..overcluster-clusres_31bf3856ad364e35_6.1.7601.18195_none_1eab0724b3daf12d.manifest
File versionNot applicable
File size2,693
Date (UTC)28-Jun-2013
Time (UTC)14:23
PlatformNot applicable
File nameAmd64_microsoft-windows-f..overcluster-clusres_31bf3856ad364e35_6.1.7601.22370_none_1f45443bccecd789.manifest
File versionNot applicable
File size2,693
Date (UTC)28-Jun-2013
Time (UTC)05:45
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File propertyValue
File nameIa64_microsoft-windows-f..overcluster-clusres_31bf3856ad364e35_6.1.7601.18195_none_c28e0f96fb7b88f3.manifest
File versionNot applicable
File size2,691
Date (UTC)28-Jun-2013
Time (UTC)14:05
PlatformNot applicable
File nameIa64_microsoft-windows-f..overcluster-clusres_31bf3856ad364e35_6.1.7601.22370_none_c3284cae148d6f4f.manifest
File versionNot applicable
File size2,691
Date (UTC)28-Jun-2013
Time (UTC)05:34
PlatformNot applicable

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 2860142
Revision : 1
Created on : 1/7/2017
Published on : 9/10/2013
Exists online : False
Views : 131