cluster cleanup

All work is being done in a Dev. Env.

I am cleaning up a SQL Server 2005 uninstall FailOver problem:

2 Microsoft references.

BOL: Remove a SQL Server 2005 Failover Clustered Instance
http://msdn2.microsoft.com/en-us/library/ms190438.aspx

BOL: How to: Manually Uninstall a SQL Server 2005 Failover Cluster
http://technet.microsoft.com/en-us/l.../ms180973.aspx

The differences between the 2:
The technet article includes these 2 steps:

Backup the existing registry on each node before removing SQL Server 2005.

Using the Registry Editor utility (regedit.exe) locate the registry key
HKLM\Software\Microsoft\Microsoft SQL Server\<instid>\Setup, where <instid>
represents the specific instance of SQL Server 2005 being uninstalled (for
example, MSSQL.1 for the first instance, MSSQL.2 for the second instance,
etc.). In this key set SqlCluster=0. This will uncluster the clustered
instance of SQL Server 2005.

I did not do this, instead I went ahead and performed all steps beginning
with:

Launch Add or Remove Programs in Control Panel

Whe I was brought in, I found that sql server had not been removed from both
nodes.

I cleaned up everything with Add and remove as best I could,
then turned sql server services off
removed the sql sderver registry entries
deleted all sql server folders

sql server 2005 configuration is the onlyh entry I have not removed.

I then began an install of sql server 2000
My virtual SQL server ip address was still in DNS
I opened DNS and removed the ip addresses for the sql server 2005 nodes and
virtual server.

then installed sql server 2000 again.

I got as far as installing sql server 2000 when I had a cluster error.

a resource is unavailable.

I ran Microsoft's cluster advisor and found a drive had failed.

I am thinking the best bet is to uninstall the cluster and begin again.

mjs

In a Dev environment? Absolutely. Evict all nodes, wipe the cluster out
and start over - it's not worth the time investment in trying to clean it up
bit-by-bit unless it's a production environment.

--

Ryan Sokolowski
MVP - Windows Server - Clustering
MCSE, CCNA, CCDA, BCFP

"mj" <mj@discussions.microsoft.com> wrote in message
news:A91882CB-013F-4DD0-B85B-58073FFCE3ED@microsoft.com...
> All work is being done in a Dev. Env.
>
> I am cleaning up a SQL Server 2005 uninstall FailOver problem:
>
> 2 Microsoft references.
>
> BOL: Remove a SQL Server 2005 Failover Clustered Instance
> http://msdn2.microsoft.com/en-us/library/ms190438.aspx
>
> BOL: How to: Manually Uninstall a SQL Server 2005 Failover Cluster
> http://technet.microsoft.com/en-us/l.../ms180973.aspx
>
> The differences between the 2:
> The technet article includes these 2 steps:
>
> Backup the existing registry on each node before removing SQL Server 2005.
>
> Using the Registry Editor utility (regedit.exe) locate the registry key
> HKLM\Software\Microsoft\Microsoft SQL Server\<instid>\Setup, where
> <instid>
> represents the specific instance of SQL Server 2005 being uninstalled (for
> example, MSSQL.1 for the first instance, MSSQL.2 for the second instance,
> etc.). In this key set SqlCluster=0. This will uncluster the clustered
> instance of SQL Server 2005.
>
> I did not do this, instead I went ahead and performed all steps beginning
> with:
>
> Launch Add or Remove Programs in Control Panel
>
> Whe I was brought in, I found that sql server had not been removed from
> both
> nodes.
>
> I cleaned up everything with Add and remove as best I could,
> then turned sql server services off
> removed the sql sderver registry entries
> deleted all sql server folders
>
> sql server 2005 configuration is the onlyh entry I have not removed.
>
> I then began an install of sql server 2000
> My virtual SQL server ip address was still in DNS
> I opened DNS and removed the ip addresses for the sql server 2005 nodes
> and
> virtual server.
>
> then installed sql server 2000 again.
>
> I got as far as installing sql server 2000 when I had a cluster error.
>
> a resource is unavailable.
>
> I ran Microsoft's cluster advisor and found a drive had failed.
>
> I am thinking the best bet is to uninstall the cluster and begin again.
>
> mjs
>
>
>