Cluster problem

An installation of sql2k5 sp2 to one node of a three node
active/active/active cluster has failed. It cannot proceed beyond the
beginning of the sql2k5 sp2 installation. It fails because it can't install
sqlsupport.msi. It seems to want to put the files in the wrong place.
We can't get the sp to install after a lot of trying and want to 1) fail the
instance the node normally hosts to a partner 2) disconnect the node from
the cluster heartbeat and public networks and 3) run a SQL de-install of the
problematic instance on the disconnected node to clear off SQL and then
reinstall it, bringing it up to SQL2K5 SP2 4) reconnect the node to the
network and 5) fail the instance on the partner node back.
I don't think this will work because during the de-install the add/remove
routine will ask to remove code from san drives it can't find because
they're no longer accessible to it, since it has been disconnected from the
network and SAN. I think a manual removal may be all that can work.
After the node has been reconnected, and SQL installation commenced I will
be asked to create a new instance, a local or clustered instance, neither of
which I want. Can I avoid this by running SQL Setup on the reconnected node
and asking to manage a virtual instance instead of installing a fresh one?
Will I need, at some point, to evict the disconnected node from the cluster?
I know on a previous occasion, I couldn't get the node, once evicted, to
rejoin. Once it's out, it's out for good, isn't it?
"Robert Hindla" <rhindla@.panix.com> wrote in message
news:C38733A0.1BA20%rhindla@.panix.com...
> An installation of sql2k5 sp2 to one node of a three node
> active/active/active cluster has failed. It cannot proceed beyond the
> beginning of the sql2k5 sp2 installation. It fails because it can't
> install
> sqlsupport.msi. It seems to want to put the files in the wrong place.
Are you installing the first instance or the second instance?
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
The next ClusterHelp classes are:
Jan 18 - 31 in Denver
Mar 10- 13 in Denver
|||The virtual SQL instance I'm proposing to de-install and then re-configure
using the setup program in 'manage' mode (instead of 'setup' mode) is one of
two named instances. It isn't the default instance.
The default instance functions satisfactorily, but only after a lot of
backing and filling, such as returning the native client to RTM level and
then re-running the installation of the client tools.
On 12/17/07 1:25 PM, in article
351AA24D-A3AA-4812-9682-F36BAFB1BC14@.microsoft.com, "Russ Kaufmann [MVP]"
<russ@.clusterhelp.com> wrote:

> "Robert Hindla" <rhindla@.panix.com> wrote in message
> news:C38733A0.1BA20%rhindla@.panix.com...
> Are you installing the first instance or the second instance?
|||"Robert Hindla" <rhindla@.panix.com> wrote in message
news:C38DA216.1BACB%rhindla@.panix.com...
> The virtual SQL instance I'm proposing to de-install and then re-configure
> using the setup program in 'manage' mode (instead of 'setup' mode) is one
> of
> two named instances. It isn't the default instance.
> The default instance functions satisfactorily, but only after a lot of
> backing and filling, such as returning the native client to RTM level and
> then re-running the installation of the client tools.
So, it sounds to me like things are seriously hosed (to use a highly
technical term) with your cluster. I would consider a complete rebuild over
the holidays if it were me.
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
The next ClusterHelp classes are:
Jan 18 - 31 in Denver
Mar 10- 13 in Denver