I have read lots of articles about and I think [hope] i'm
close to solution but...

I have two Windows 2003 Enterprise Edition in a two-node
cluster (both are Domain Controllers) and I want to install
SQL Server 2000 over this cluster as a prerrequisite to
install SMS 2003.

The cluster has a virtual name and IP and SQL Server has
its own virtual name and IP.
I have tried to launch the SQL Setup with and without DTC
(in Cluster group and in its own group), with and without
WINS Server. Of course, I can access to cluster resources
from other computers.

Always the same result: The first SQL Server Setup dialog
don't let me clic in the "Virtual Server" option.

Some idea to try?

Thanks
Sefirah

Ok, there are a few things to check

First, you still need to run Comclust.exe on each node to tell each node to
'switch' to clustered MSDTC mode.

You also need to follow
PRB: Installation of a Named Instance of SQL Server 2000 Virtual Server on a
Windows 2003-Based Cluster Fails
http://support.microsoft.com/default...&Product=sql2k

Make sure Terminal Services is not running in application mode.
http://support.microsoft.com/default...&Product=sql2k

Finally, you need to be installing SQL 2000 Enterprise Edition.

--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com

I support the Professional Association for SQL Server
www.sqlpass.org

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

For more information on the special considerations if you're using DCs as
your cluster nodes, see:
281662 Windows 2000 and Windows Server 2003 Cluster Nodes As Domain
Controllers
http://support.microsoft.com/?id=281662

Make sure SQL Server has a shared disk available in group with no other
resources. The SQL IP resource should NOT exist prior to installing SQL.
For more tips, see:
SQL Server 2000 Clustering Whitepaper,
http://www.microsoft.com/SQL/techinf...overcluster.as
p

And for Win03/SQL2K specific issues, see:
815431 PRB: Installation of a Named Instance of SQL Server 2000 Virtual
Server http://support.microsoft.com/?id=815431
329329 PRB: Windows Server 2003 Support for SQL Server 2000
http://support.microsoft.com/?id=329329
815430 INF: How to Suppress the Appshelp Message in an Unattended
Installation http://support.microsoft.com/?id=815430
817064 HOW TO: Enable Network DTC Access in Windows Server 2003
http://support.microsoft.com/?id=817064
301520 SQL Server 2000 Cluster Does Not Install on Windows Server
2003-Based http://support.microsoft.com/?id=301520
313037 INF: Upgrading SQL Server Clusters to Windows Server 2003
http://support.microsoft.com/?id=313037
327270 SQL Server 2000 Is Not Supported on Windows Server 2003 Terminal
Server http://support.microsoft.com/?id=327270
811430 INF: SQL Server 2000 Supports IPSec on Windows Server 2003 Cluster
http://support.microsoft.com/?id=811430
281662 Windows 2000 and Windows Server 2003 Cluster Nodes As Domain
Controllers http://support.microsoft.com/?id=281662
Windows Server 2003 Clustering Services
http://www.microsoft.com/windowsserv...ring/default.m
spx


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

Thanks a lot, Geoff, Sthephen and Cindy for your help.
I have read some of the articles you say me and now I'm
reading the new documentation (specially the article 281662
-Xtra thanks, Cindy-) and probing new checklists of
configurations.
For now, the only way to me is to have in the same cluster
the DC's and the SQL Server.
I tell you the manner I was resolved my problem.

Best regards and thanks again.

Sefirah