After doing maintenance on Cisco UCS Server Profiles I had to fix up network adapters on a 4 node Hyper-V Failover Cluster. After the maintenance 3 of the 4 nodes came online. Errors in the event log included cluster service termination due to file already exists. After checking all settings on the 4th node and doing a cluster validation that showed all was OK I was ready to scratch my eyes out when I came across an article that advised to rename all of the network connections used by the cluster and then try to start the service again. Low and Behold! Issue resolved.
The life saving article is here: http://lokna.no/?p=1753