Operating system environment: Windows Enterprise R2 SP1
No errors were found while verifying the cluster configuration. However, when you create a failover cluster, a time-out error occurs: "An error occurred while creating the cluster. An error occurred while creating the cluster "XXX". The operation returned because the timeout period has expired. ”。
The attempt to select a single server cluster was successfully created, but when the second node was added, it was stuck in the "Waiting node XXX to become the cluster's completion notification of the function member" until the timeout error exits "The operation returned because the timeout period has expired. ”
Troubleshooting process:
Creating a cluster with a single node although it succeeded, but found that the cluster name could not be brought online, the error log is as follows:
Event id:1027 task Category: Network Name resource
"Cluster Network Name resource" Cluster Name "cannot be brought online. The computer object associated with the resource could not be updated in the domain "SGCD.IAP" for the following reason: The primary cluster name identity token could not be obtained.
The text of the associated error code is: a thread that is not currently impersonating a client attempts to operate on an impersonation token.
The cluster Identity "sgftpclsuter$" may lack the permissions required to update the object. Work with your domain administrator to ensure that the cluster identity "
From the log, it is suspected that the cluster name failed when the domain control was created to register the computer.
Attempting to join a two node to another domain control, creating the cluster is normal, and the initial assertion is due to domain control issues. Discovers that the original domain control domain Policy set Network access restrictions "Computer Configuration-windows Settings-security Settings-user rights assignment from the network access this computer", after removing its policy, the two node is re-joined to this domain and successfully created the cluster.