Hi, al

I am installing SQL2K Cluster on Win2003 and getting "Another Virtual Server of the same name exists on the network error"
My SQL2K Cluster virtual name is different from the Win2003 cluster and any of the nodes. There is no existing SQL Cluster with the same virtual name.
Any suggestions will be appreciated.

Is this a named or a default instance? WHat are all of
the names you are using?

the network error".
SQL Cluster with the same virtual name.

Allan

The installation fails at the very beginning (at the Computer Name prompt) - before the Instance Name prompt
My node names are PVLDCSQL01N1 and PVLDCSQL01N1. The Windows cluster name is PVLDCSQL01CL an
the two virtual SQL Server names (I am building active-active) are PVLDCSQL01R1 and PVLDCSQL01R2.

Well, if you're building a multiple instance cluster, one
will have to be a named instance (not entered on the first
screen tho; just the first part is).

PVLDCSQL01R1 and PVLDCSQL01R2 are unique, but as I said,
one would have to be a named instance, so it would be like
PVLDCSQL01R2\INS2, not just PVLDCSQL01R2. Or PVLDCSQL01R1
\INS1.

But if you are getting the error before you even choose
what type of instance, PVLDCSQL01R1 or PVLDCSQL01R2 exist
somewhere and can be resoved through DNS. Check your DNS
server to see if for some reason entries exist, and reboot
to completely flush (the "just incase" ... you probably
shouldn't have to reboot).

I've only ever seen this error when a duplicate name
exists out on the network. This is by design to ensure
uniqueness.

Ping the virtual server name that you are running into problem with. This
may help you find whether the name is already used.

--
Linchi Shea
linchi_shea (AT) NOSPAMml (DOT) com


"Oleg" <anonymous (AT) discussions (DOT) microsoft.com> wrote

The entries for the SQL Virtual names do exist in the DNS. . . and, as far as I understand, they have to. Otherwise, the names will not be resolved. But those entries have been created specifically for this cluster build and do not reference any other machine on the network. Also, the SQL Cluster virtual name should match the cluster resource Network name, correct ?

Remove the entries from DNS, they will be added by setup. Also check that
all your registry keys have been cleaned up per 290991 HOW TO: Manually
Remove SQL Server 2000 Default, Named, or Virtual
http://support.microsoft.com/?id=290991. You may need to search the
registry on each node for the SQL Net Name to see if some stray key
somewhere has an invalid entry pointing to that name.

Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Cindy

Your first suggestion was correct - deleting DNS entries did the trick.

Thank you