More info: I found out that, in Powershell, if I do a "Get-ClusterResource", I *do* see it as state 'Failed'. If I understand my searching correctly, should I just need to do:
Remove-ClusterResource -Name "SQL Network Name (MultiSite1)" I get that this is how to (ordinarily) remove a cluster resource, but will it work on this "failed" resource? On Tue, Feb 2, 2016 at 12:22 PM, Michael Leone <[email protected]> wrote: > I have to set up a SQL 2012 MultiSubnet Cluster. My boss had set up a > testing version (meaning: he set up a 2 node Windows 2012 mutlisubnet > cluster, and then installed SQL 2012 Cluster on it); when he left the > company recently, we uninstalled SQL Cluster, but left the Windows > cluster intact (rather than rebuild everything from scratch). > > I am at the point of reinstalling SQL 2012, now for production, not > testing. Here's the thing - when I run the Windows cluster validation, > I am still seeing references to the OLD SQL network name > ("MultiSite1"). This cluster resource does not exist any longer. > Problem is, I don't see it in the Failover Cluster Manager anywhere. I > only see it in the Cluster Validation report, under various warnings: > > under "Validate Resource Status", it shows that "Validating cluster > resource Name: MultiSite1" shows as 'Failed'. > > under "Validate Multiple Subnet Properties", it says to change the > HostRecordTTL property for network name "MultiSite1". > > It is also showing up as Cluster Event errors - event ID 1051, cluster > network name resource cannot be brought online. > > > SO: > > How can I get rid of this now phantom resource "MultiSite1", before I > go an install SQL 2012 (with it's own new SQL Server Network Name)? It > should have been removed when I uninstalled the old SQL 2012 cluster, > but apparently it wasn't (or I did the uninstall wrong, I guess). I > don't see "MultiSite1" under any resource in Failover Cluster Manager. > > Hope I was clear enough on this.
