Home | Site Map | Cisco How To Net How To | Wireless | Search | Forums | Services | Setup Guide | Chicagotech MVP | About Us | Contact Us|

 

 

An error occurred while creating the cluster: This operation returned because the timeout period expired
An error occurred while creating the cluster: The server is not operational
Event ID 14128 14132: A protocol other than the Microsoft Virtual Network Switch Protocol has been bound to NIC 'Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client)' but the NIC is being used by a virtual switch.
Event ID 1530: Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.
Event ID 1570: Node 'HPV-DMZ01' failed to establish a communication session while joining the cluster. This was due to an authentication failure. Please verify that the nodes are running compatible versions of the cluster service software.

Situation: The client attempts to create a failover cluster but it failed with these errors: This operation returned because the timeout period expired and The server is not operational. Both nodes also have the following Event IDs.

Log Name: Microsoft-Windows-Hyper-V-Network-Admin
Source: Microsoft-Windows-Hyper-V-Network
Date: 7/29/2011 3:30:36 PM
Event ID: 14128
Description:
A protocol other than the Microsoft Virtual Network Switch Protocol has been bound to NIC 'Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client)' but the NIC is being used by a virtual switch.

Log Name: Microsoft-Windows-Hyper-V-Network-Admin
Source: Microsoft-Windows-Hyper-V-Network
Date: 7/29/2011 3:30:36 PM
Event ID: 14132
Description:
The virtual switch protocol is not bound to NIC 'Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client)' but the NIC is being used by a virtual switch.

Log Name: Application
Source: Microsoft-Windows-User Profiles Service
Date: 7/29/2011 3:32:51 PM
Event ID: 1530
Description:
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.

DETAIL -
3 user registry handles leaked from \Registry\User\S-1-5-21-271498468-1634270793-1794660368-1218:
Process 1264 (\Device\HarddiskVolume2\Windows\System32\wbem\WmiPrvSE.exe) has opened key \REGISTRY\USER\S-1-5-21-271498468-1634270793-1794660368-1218\Software\Microsoft\Windows\CurrentVersion\Internet Settings
Process 1264 (\Device\HarddiskVolume2\Windows\System32\wbem\WmiPrvSE.exe) has opened key \REGISTRY\USER\S-1-5-21-271498468-1634270793-1794660368-1218\Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings
Process 1104 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-271498468-1634270793-1794660368-1218\Printers\DevModePerUser


Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 7/29/2011 3:33:19 PM
Event ID: 1570
Description:
Node 'HPV-DMZ01' failed to establish a communication session while joining the cluster. This was due to an authentication failure. Please verify that the nodes are running compatible versions of the cluster service software.

Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 7/29/2011 3:33:21 PM
Event ID: 1570
Description:
The description for Event ID 1570 from source Microsoft-Windows-FailoverClustering cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

Case collections: Case 1: It could be security or permission issue. Make sure each node has permissions to access other nodes in "Access this computer from the network" policy. Please refer to these post for more information:
Can't create a cluster with Event ID 1570
, Unable to create cluster, hangs on forming cluster
The servers do not all have the same software updates

Case 2: The cluster name doesn't show up in the ADUC for some reason. Removing and re-install failover cluster. Refer to this page: Cluster: Can't bring Network Name on line

Case 3: The NIC on one of node was setup for VM incorrectly. Similar case can be found this post: hyper V network Event ID 14128


Case 4: Those two Nodes can ping each other on the SAN subnet. We found the problem is one Cisco switch port was configured incorrectly. After re-configure the port and make sure both NICs can ping each other, we can create the Cluster.

Case 5: one node was added, but with error and can't be viewed. Using cluster node nodename /forcecleanup to remove it from the cluster.

Case 6: It could be the firewall or antivirus software. Please refer to this page: Create Cluster errors (timeout) with Event ID 1570

Case 7: It is DNS issue. The cluster name is not listed in the DNS record. Adding the cluster name fixes the problem. Refer to this page: Can't create cluster because of network path not found

 

Post your questions, comments, feedbacks and suggestions

Contact a consultant

Related Topics

 

 

 

Bob Lin Photography services

Real Estate Photography services 

 

  This web is provided "AS IS" with no warranties.
Copyright © 2002-2018 ChicagoTech.net, All rights reserved. Unauthorized reproduction forbidden.