Hyper-V R2 - Failover Cluster Cluster Name resource fails to come online


Hi,

Having a bit of a problem with Hyper-V R2 and the Failover Clustering and was wondering if anyone can help.

Although our cluster appears to be functioning correctly, the Cluster Name resource will not come online. I get the following errors:

Microsoft-Windows-FailoverCluster
ID 1206
Cluster network name resource 'Cluster Name' cannot be brought online. The computer object associated with the resource could not be updated in domain 'xxx.local'. The error code was 'Unable to get Computer Object using GUID'. The cluster identity 'HYPERVR2CLUSTER$' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain.

And:
Microsoft-Windows-FailoverCluster
ID 1069
Cluster resource 'Cluster Name' in clustered service or application 'Cluster Group' failed.

I've checked that the account is present in Active Directory and at first glance it all seems fine. I've also tried the "Repair Active Directory Object" function (both just running the action and deleting the object entirely and recreating the object) with no success.

Has anyone seen this issue before? Any help would be greatly appreciated.

__________________
A.Rajesh Khanna

Hi,


Verify that the computer object associated with the cluster name exists, and that it is in the proper state. See this doc, it has more details on cluster AD requirements:

Failover Cluster Step-by-Step Guide: Configuring Accounts in Active Directory

Hi,

As previously mentioned, I have verified that the account exists in Active Directory. I have also tried deleting and recreating the account (by using the "Repair Active Directory Object" function from a Windows Server 2008 R2 Beta 1 server.

I've also compared the cluster permissions to another, fully functioning Windows Server 2008 (not R2 Beta) cluster and all permissions etc. appear identical.

I've also verified that name resolution (both DNS and NetBIOS) is functioning correctly.

I have a suspicion that the issue might be down to the length of the NetBIOS name; however as the resource is offline and won't come online, I can't change the name unfortunately.

__________________
A.Rajesh Khanna

Hi,

You can't delete / recreate the cluster computer objects... even though the friendly name that you created is the same, the underlying SID associated with that object is different. Hence, why you see the error that the computer object can't be found by GUID.
This is true with any security identity... you can't recreate things with the same friendly name and expect them to work.

You either need to restore the tombstone of the original computer object or re-create the cluster. Since you are using R2, there is also a AD Recycle Bin now, that will allow recovering deleted objects (if you have R2 DC's)

Thanks!

Hi,

I used the "Repair Active Directory Object" to recreate the object - surely this should recreate the object exactly as needed by the cluster service?

Also, me deleting the object was the last resort; the network name resource wasn't working - and has never worked - prior to me deleting the object. I had tried everything else to get this name online before actually deleting the object.

Thanks for the info but I have resolved this by deleting the cluster completely and starting from scratch which was a bit of a pain to do. I think the length of the name was the problem as I've chosen a shorter name for my new cluster and it now works.

__________________
A.Rajesh Khanna