You need to figure out why the Failover Cluster resource group failed to go online. There are various ways of doing that: I'd start with the System log in the Event Log viewer where Failover Cluster service logs its events. Filter on Failover Cluster (probably
warnings and errors too) find the failures and see if anything meaningful is described. Failover clustering is a bit removed from how HPC uses it so the event log entries may not contain actionable data (as in, all it tells you is something failed but you
know that already).
If that is the case, you have to reinstall but there is a bit of a chicken/egg problem in that if any of the HPC services fail to start then the installation is considered failed and HPC setup (via Windows Installer) rolls back and uninstalls everything
including the event logs that could provide insight into why the installation failed.
The trick is to wait until HPC setup displays the dialog box indicating that installation failed but do not dismiss it. Also have the Failover Cluster manager snapin up and running so you can observe the installation from that perspective. When the failure
dialog appears, bring the Event Log viewer up again and look for the various operation/administrative logs under Applications and Services Logs/Microsoft/HPC. If you were watching the resource group while it is brought online, then you can probably figure
out which service is failing. Using that inspect the log and see if you can figure out why it is failing.
I would guess a permissions issue of some sort but since there are other resources in the group (disks, IP addresses, etc) they could be at fault as well. Prior to install HPC, you should double check your HA configuration by failing the resource group over
and back again to make sure that there are no issues there.
If you report back and the need for more help, it will be good to have the particulars of your configuration, namely whether SQL is part of the resource group, etc.
c
