I am trying to setup a virtual SQL 2000 instance on Windows 2k3 Ent. I have
drives presented from the SAN and a Quorum disk and they can all failover
without issue. I start going through the SQL 2000 Installation and after I
input the IP for the Virtual Server and hit next I get nothing else. I check
task manager and the following process starts and uses 25% of the CPU until I
kill it. SQL Setup shows up as not responding and it won't go any further.
I have tried SQL 2000 Ent and SQL 2000 Dev edition with the same issues. I
have also tried the install on the other Node. The process that starts
running is called _INS5576._MP.

Any ideas/suggestion so I can get SQL installed?

Thanks,

Jason C

Make sure none of the "group names" for your cluster groups match any of
the "resource names" for items within the group. For example, DO NOT call
your SQL Server group the same name as your virtual SQL Server. Keep the
group name unique, such as "VSQL Group1".

Also check the SQLSTP.log in the \Winnt folder. This is the initial setup
file.

Chris Skorlinski
Microsoft SQL Server Support
Please reply directly to the thread with any updates.

This posting is provided "as is" with no warranties and confers no rights.

Thanks Chris. It was the naming of the SQL Server Group. I had it called
SQL and I changed it to VSQL Group as you suggested and the setup continues
and allows me to select the shared disks.


"Chris Skorlinski (MS)" wrote: