Have you looked at this:
PRB: Installation of a Named Instance of SQL Server 2000 Virtual Server on a
Windows 2003-Based Cluster Fails
http://support.microsoft.com/default.aspx?scid=kb;en-us;815431&Product=sql2k --
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org [quoted text, click to view] "Mintz" <Mintz@discussions.microsoft.com> wrote in message
news:43763E00-DDEC-4944-9C44-B080D2169F87@microsoft.com...
> We have a four node cluster which was in a NT 4.0 domain - only two of
them active. Our goal is to make 3 active 1 passive. Recently we migrated to
Active Directory on Win 2003. The CLuster nodes are running win 2003 as
well.
[quoted text, click to view] >
> In the NT 4 domain I was able to run the setup and create named instance
without any problem. The same setup does not run anymore in Active Directory
Environment. Though everything continued to work fine - I can't install the
additional instance on the cluster. I know I have to run the setup on one
node first.
[quoted text, click to view] >
> Baiscally the setup creates the cluster resourcesm it starts the SQL
service but fails to connect to it and then rolls back and cleans up. I get
following app logs:
[quoted text, click to view] > The description for Event ID ( 17052 ) in Source ( MSSQL$OZONEDBI ) cannot
be found. The local computer may not have the necessary registry information
or message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event:
[sqsrvres] checkODBCConnectError: sqlstate = 01000; native error = 274d;
message = [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(Connect()).
[quoted text, click to view] >
>
> and another one:
>
> The description for Event ID ( 17052 ) in Source ( MSSQL$OZONEDBI ) cannot
be found. The local computer may not have the necessary registry information
or message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event:
[sqsrvres] ODBC sqldriverconnect failed
[quoted text, click to view] >
>
> Any Ideas? Would greatly appreciate your help...Thanks in advance.
> -Mintz.
>
>