Is Act-Act SQL certified on Windows2003?
I cannot get the 2nd instance to install. I keep getting
the following event errors:
THE EVENTVIEWER APP log
Event ID 17052 Source: MSSQL$VSQL02 unidl7401
The description for Event ID ( 17052 ) in Source (
MSSQL$VSQL02 ) 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]
OnlineThread: Error 435 bringing resource online.


Event ID 17055 Source: MSSQL$SSQL022
The description for Event ID ( 17055 ) in Source (
MSSQL$SQL022 ) 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: 17148, SQL
Server is terminating due to 'stop' request from Service
Control Manager.

The description for Event ID ( 17052 ) in Source (
MSSQL$SQL022 ) 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]
OnlineThread: Error connecting to SQL Server.

The description for Event ID ( 17052 ) in Source (
MSSQL$SQL022 ) 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 =
35; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]
ConnectionOpen (Connect()).

For a clustered named instance on Windows 2003 you have to use a named pipe alias during setup:
815431 PRB: Installation of a Named Instance of SQL Server 2000 Virtual Server http://support.microsoft.com/?id=815431

Other Windows 2003 specific info:
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

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