Clustered SQL7 upgrade to SQL2000 fails to find default server

We are trying to upgrade to SQL2000 in a failover cluster
environment but the upgrade process is failing to identify
the default server and is instead creating a new named
instance of SQL2000 alongside SQL7 (the 'default' checkbox
on the upgrade wizard is greyed out and unchecked). The
production database is 125Gb so I don't want to use the
copy database wizard if possible. Can anyone suggest how
to get round this? Is it a registry setting?
TIA
JohnI am not sure what process you are taking to do this but here is the proper
sequence:
1. Uncluster SQL Server 7.0 cluster
2. Upgrade SQL Server 7.0 to a SQL Server 2000 default instance (putting
binaries on a local drive)
3. Upgrade the default instance of SQL Server 2000 ti a clustered intance
of SQL Server.
This is documetned in Books on Line:
Upgrading to a SQL SErver 2000 Failover Cluster
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Rand,
this is exactly the process we are trying to follow, but
the 2nd step fails because the upgrade process can't find
the default SQL7 server to upgrade in place and instead
creates a new instance of SQL2000. We have tried this over
and over again, even to the point of completely removing
and reinstalling SQL7. I've had no trouble before with
upgrading a standalone server so it's probably something
to do with the clustering. Any suggestions would be
greatly appreciated...

>--Original Message--
>I am not sure what process you are taking to do this but
here is the proper
>sequence:
>1. Uncluster SQL Server 7.0 cluster
>2. Upgrade SQL Server 7.0 to a SQL Server 2000 default
instance (putting
>binaries on a local drive)
>3. Upgrade the default instance of SQL Server 2000 ti a
clustered intance
>of SQL Server.
>This is documetned in Books on Line:
>Upgrading to a SQL SErver 2000 Failover Cluster
>Rand
>This posting is provided "as is" with no warranties and
confers no rights.
>.
>