This message could be a number of different issues upon getting the generic error below.
An error occurred while creating the cluster.
An error occurred creating cluster 'CLUSTERNAME'.
The service has not been started
Looking at the example error report you can see after Server3 checks the Network FT Driver it attempts to cleanup and exit.
Beginning to configure the cluster 'CLUSTERNAME'.
Initializing Cluster 'CLUSTERNAME'.
Validating cluster state on node server1.domain.com.
Searching the domain for computer object CLUSTERNAME.
Creating a new computer object for CLUSTERNAME in the domain.
Configuring computer object CLUSTERNAME as cluster name object.
Validating installation of the Network FT Driver on node Server1.domain.com.
Validating installation of the Cluster Disk Driver on node Server1.domain.com.
Configuring Cluster Service on node Server2.domain.com.
Validating installation of the Network FT Driver on node Server2.domain.com.
Validating installation of the Cluster Disk Driver on node Server2.domain.com.
Configuring Cluster Service on node Server3.domain.com.
Validating installation of the Network FT Driver on node Server3.domain.com.
Unable to successfully cleanup.
To troubleshoot cluster creation problems, run the Validate a Configuration wizard on the servers you want to cluster.
This issue is stemmed from installing the Failover Cluster in the wrong order normally in a Hyper-V cluster. To fix this all you need to do is remove this feature and install it again. Reinstall Failover Cluster feature to fix your cluster NIC missing during cluster creation.
ocsetup FailoverCluster-Core /uninstall
ocsetup FailoverCluster-Core
1 comment:
Thank you! This worked perfect!
Post a Comment