RE: weird sql server 2000 setup problem

From: Uttam Parui[MS] (uttamkp_at_online.microsoft.com)
Date: 07/05/04 

Date: Mon, 05 Jul 2004 18:02:49 GMT

Its possible that some unnecessary service is affecting the setup. Try the foll:

1. Stop all services on the computer that may use ODBC.

    WARNING: Before stopping any services, verify that stopping these

   services will not disrupt other users.

  
  These services include any of the following:

        - All Microsoft Internet Information Server (IIS) services. This
                      includes all of the following:

                - Certificate Authority

                - Content Index

                - FTP Publishing Service

                - Gopher

                - IIS Admin Service

                - World Wide Web (WWW) Publishing

                - Microsoft NNTP Service

                - Microsoft SMTP Service

                - Microsoft Message Queue Service (MMSQ)

                - MSDTC

        - Microsoft Exchange Server

        - DBWeb

        - ARCserve backup

        - InocuLAN virus protection

        - McAfee antivirus services

        - UniCenter system monitoring

2. Occasionally, you may also need to stop additional services for SQL
   Server Setup to complete successfully. In these cases, you may want to
   stop any non-critical server services that were not installed with the
   default installation of Windows NT.

(NOTE: KB 192710 has basic guidelines and a list of services that needs to be running and all other services stopped for Win2K. Although you are using Win2K3, you can use this list as a guide).
http://support.microsoft.com/?kbid=192710

3. Before you begin the installation process, verify that:

*There is no IRQ sharing between network interface cards (NICs) and drive/array (SCSI) controllers. Although some hardware might support this sharing, it is not recommended.

*Your hardware is listed on the Microsoft Windows NT Hardware Compatibility List. For a complete list of supported hardware, visit the following Microsoft Web site:
http://www.microsoft.com/whdc/hcl/default.mspx

*Private network is configured as per "258750 Recommended private "heartbeat" configuration on a cluster server "

*The disk drive letters for the cluster-capable disks are the same on both servers.

*You have disabled NetBIOS for all private network cards before you start the SQL Server Setup program.

*You have cleared the system logs in all nodes and viewed the system logs again. Make sure that the logs are free of any error messages before you continue.

Additional Information
====================
Also, if you installing remotely, then try running the setup locally?

If you are installing SQL Server 2000 named virtual instance then refer to the following KB first

815431 PRB: Installation of a Named Instance of SQL Server 2000 Virtual Server on a Windows 2003-Based Cluster Fails
http://support.microssoft.com/?id=815431

The installation of SQL Server 2000 is not supported on a clustered configuration that has mounted drives even if the mounted drives are not intended to be used with SQL Server.
For more information, refer to
SQL Server 2000 support for mounted volumes
http://support.microsoft.com/?id=819546

Best Regards,

Uttam Parui
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.

Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

Relevant Pages

  • RE: Problems upgrading SQL MSDE for Sharepoint
    ... Please try the following steps and then run the SQL Server 2000 setup again: ... Can we install SQL Server successfully at this time? ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: x64 2003 Cluster - SQL2000 named instance fail
    ... one the settings are not detected by the setup. ... > in the cluster log you will notice the a connection to the SQL Server ... > named instance cannot be established. ... >> Microsoft highly recommends that users with Internet access update their ...
    (microsoft.public.sqlserver.clustering)
  • Solution to do Accent Insensitive Full Text Search with SQL Server 2000
    ... Installing an accent insensitive version of Microsoft Search ... This is the installation program we will use to ... some registry keys used by SQL Server and MS ... You will then have to create a schedule for the indexation process. ...
    (microsoft.public.sqlserver.fulltext)
  • Solution to do Case Insensitive Full Text Search with SQL Server 2000
    ... Installing an accent insensitive version of Microsoft Search ... This is the installation program we will use to ... some registry keys used by SQL Server and MS ... You will then have to create a schedule for the indexation process. ...
    (microsoft.public.sqlserver.fulltext)
  • I really meant Solution to do ACCENT Insensitive Full Text Search with SQL Server 2000
    ... Installing an accent insensitive version of Microsoft Search ... This is the installation program we will use to ... some registry keys used by SQL Server and MS ... You will then have to create a schedule for the indexation process. ...
    (microsoft.public.sqlserver.fulltext)