Consider the following scenario:
- You install the Failover Clustering feature on a set of Windows Server 2008-based computers.
- You try to create a failover cluster on these computers by using the Failover Cluster Management Microsoft Management Console (MMC) snap-in or by using the Cluster.exe tool.
In this scenario, the cluster creation fails, and you receive the following error message:
An error occurred while creating the cluster. An error occurred creating cluster 'clustername'. The service has not been started.
Additionally, the following event is logged in the System log:
Log Name: System
Event ID: 1289
Task Category: None
The Cluster Service was unable to access network adapter 'Microsoft Failover Cluster Virtual Miniport'. Verify that other network adapters are functioning properly and check the device manager for errors associated with adapter 'Microsoft Failover Cluster Virtual Miniport'. If the configuration for adapter 'Microsoft Failover Cluster Virtual Miniport' has been changed, it may become necessary to reinstall the failover clustering feature on this computer.
To eliminate single points of failure that are related to network communication, failover clustering uses the Microsoft Failover Cluster Virtual Miniport driver. Additionally, this driver generates a physical address during startup. However, any of the following situations would make cluster creation fail:
- No physical adapter has a universally administered MAC address.
- Cluster configuration is not fully cleaned up after a sequence of repeated installation and removal of the Failover Clustering feature.
To resolve this problem, follow these steps to reinstall the Failover Clustering feature:
- On each computer that you want to make a cluster node, use the Server Manager console to remove the Failover Clustering feature.
- Restart each computer from which you have removed the Failover Clustering feature.
- Add the Failover Clustering feature on all these computers again.
- Run cluster validation against these computers.
- Try creating a cluster.
If the problem is not resolved after you reinstall the Failover Clustering feature, follow these steps, and then run the reinstallation again.Important
This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
How to back up and restore the registry in Windows
- Open Registry Editor.
- Locate the following registry subkey:
- Under this subkey, find the subkey that holds a DriverDesc string value entry whose value is "Microsoft Failover Cluster Virtual Adapter."
- Under the subkey that you found in step 3, add the following string value registry entry:
Value data: 02-AA-BB-CC-DD-01
- Restart the computer.
- Repeat step 1 through step 5 on other computers on which you experience this problem. When you do this on other computers, replace the value data of the registry with different values in order to set a unique value for each node. For example, set the value on the second node to 02-AA-BB-CC-DD-02, and set value on the third node to 02-AA-BB-CC-DD-03. If you notice this behavior on distinct clusters, make sure that you use an address for each node that is unique across all clusters.
- Try creating the cluster again.
Article ID: 973838 - Last Review: September 11, 2010 - Revision: 2.1
- Windows Server 2008 Enterprise
- Windows Server 2008 Datacenter
- Windows Server 2008 Datacenter without Hyper-V
- Windows Server 2008 Enterprise without Hyper-V
- Windows Server 2008 for Itanium-Based Systems
- Windows Server 2008 Standard without Hyper-V
|kbclustering kberrmsg kbtshoot kbexpertiseinter kbsurveynew kbprb KB973838|