Upgrade from SQL 2000 to SQL 2005 Problem in Active/Active Cluster Environment

I'm running into a problem upgrading a SQL 2000 instance in an Active/
Active Cluster Environment to SQL 2005. This is not the first time
the cluster has been upgraded to 2005. It currently has 8 instances
of SQL running on it, however only 2 are SQL 2005. The previous
upgrade happened before I started here, so there isn't any
documentation for me to reference, and I haven't found any
documentation online that pertains to this situation. When I click
through the upgrade process one step is not consistent with the
installation instructions I've found on MSDN.

I do not encounter a screen that prompts me to input a Virtual SQL
Server Name. I'm assuming this is due to my situation being an
upgrade and not a new install.

Additionally when I try to finish the installation, I receive the
following error:

TITLE: Microsoft SQL Server 2005 Setup
------------------------------

SQL Server Setup did not install SQL Server on one or more remote
nodes of your failover cluster. To continue, log off of all remote
nodes and then run Setup again from the primary node.

For help, click:
http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=setup.rll&EvtID=50057

------------------------------
BUTTONS:

OK
------------------------------


I've tried performing this update by logging into the VM, the current
node the VM is on (this is also the node where the cluster IP VM is
located), and the failover node the VM isn't on. All of which result
in the same lack of entering a Virtual SQL Server Name step and the
failure noted above. The only thing I've found online is to failover
all VMs to one node in the cluster and then perform the upgrade
process. I will try this later this weekend during off hours to
ensure that no one experiences a dropped connection to the other
instances on the cluster.

If anyone has any suggestions or experience with this, please pass
that information on.

Thanks,

John

.

Loading