Failover Cluster error 1207

Question

Hello,

I have 2 nodes of Failover Cluster on Windows Server 2022. A few days ago I saw errors with ID 1207.

Event Details:

The computer object associated with the cluster network name resource 'Cluster Name' could not be updated in domain 'contoso.local' during the Password change operation. The text for the associated error code is: The specified network password is not correct.

The cluster identity 'HVCluster$' 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.

This error is on the second Node which is "Current Host Server" on the Failover Cluster.

Any ideas?

Answer 1

Hi drClays,

Hope you're doing well.

Based on our past experience: (1) The CNO must have full control authority over itself, the VCO, and the OU in which it is located. If a 1207 alarm occurs in the cluster in the future, you can first check whether the permissions are complete. (2) In addition, when 1207 appears, it is usually accompanied by warning 1196. For the 1196 alarm, we generally need to check whether the CNO has full control over the alarm object A record. For example, the alarm clearly indicates that the CNO must have full control over its DNS zone. permissions, the CNO also needs to have full control over the DNS zone where it is located. (3) After confirming that there is no problem with the permissions, if an error is still reported, since you are in a production environment, we can perform Repair CNO and VCO operations during downtime. Please manually offline the name resource under cluster core resources, then click More Actions and select Repair. Please find the name of the character who reported the error in the role column, click on the resource below to find the name resource, and also go offline manually, click on More Actions and select Repair. (4) Or you can try to change the DNS timestamp A record of the cluster name and File server name to a static A record, so that he will not try to register the DNS record. a. Click View and select Advanced in DNS manager. b. Uncheck "Delete this record when it becomes stale" c. Right-click the blank part of DNS manager and click Refresh. The A record will be changed to static. (5) After Repair, you can run the "Get-ClusterResource -Name "resource name" | Update-ClusterNetworkNameResource" command to check whether the problem still exists. (6) If the error is still reported, try to upgrade the two node patches of the cluster to the latest I hope this helps!

Best Regards,

Ian Xue

---

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hey,

Check permissions and quota related to updating the computer objects in the AD. Should help:
https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd353998(v=ws.10)?redirectedfrom=MSDN

In addition, if you need shared storage for your cluster check StarWind VSAN.
https://www.starwindsoftware.com/starwind-virtual-san

Cheers,

Alex Bykovskyi

StarWind Software

Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.