Article ID: 905286
Article Last Modified on 11/27/2007
APPLIES TO
- Microsoft SQL Server 2000 Enterprise Edition
BUG #: 474471 (SQL Server 8.0)
Microsoft distributes Microsoft SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release.
SUMMARY
This article describes the following about this hotfix release:
- The issues that are fixed by this hotfix package
- The prerequisites for installing the hotfix package
- Whether you must restart the computer after you install the hotfix package
- Whether the hotfix package is replaced by any other hotfix package
- Whether you must make any registry changes
- The files that are contained in the hotfix package
SYMPTOMS
You run SQL Server Setup to install Microsoft SQL Server 2000 Service Pack 4 (SP4) in binary-only mode on a failover cluster. When you do this, the Setup program does not continue beyond the Services Accounts page. You receive the following error message:
Note This problem only occurs in the Setup program for the 32-bit version of SQL Server 2000 SP4. This problem does not occur in the Setup program for the 64-bit version of SQL Server 2000 SP4.
CAUSE
This problem occurs when you run the Setup program to install SQL Server 2000 SP4 after you add a new node to an existing failover cluster.
RESOLUTION
The installer does not install this hotfix correctly on x64-based systems. This installation issue occurs when the following conditions are true:
- The system uses the Advanced Micro Devices (AMD) AMD64 processor architecture or the Intel Extended Memory 64 Technology (EM64T) processor architecture.
Note This issue does not occur on systems that use the Intel Itanium processor architecture.
- The system is running a 64-bit version of the Microsoft Windows Server operating system.
- The system is running a 32-bit version of SQL Server 2000.
We have corrected this installation issue in later builds of SQL Server 2000, starting with version 8.00.2244. When a customer who is running SQL Server 2000 on an x64-based system requests this hotfix, we will provide a build that includes this hotfix and that can be installed correctly on an x64-based system. The build that we provide will be version 8.00.2244 or a later version.
Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2000 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Prerequisites
To apply this hotfix, you must have SQL Server 2000 SP4 installed on the computer. For more information about how to obtain SQL Server 2000 SP4, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack
Restart requirement
You do not have to restart the computer after you apply this hotfix.
File information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Sqlsui.dll | 2000.80.2151.0 | 323,584 | 28-Jul-2005 | 01:53 | x86 |
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
WORKAROUND
To work around this problem, use one of the following methods:
- Run the Setup program on the active node. Let the Setup program reinstall SQL Server 2000 SP4 on the existing nodes and on the new node.
Note This workaround will require some downtime for SQL Server when the following conditions are true:
- You install SQL Server 2000 SP4 on all nodes.
- All the nodes are at a service pack level that is earlier than SQL Server 2000 SP4.
- Create an unattended installation file. Use this file to install SQL Server 2000 SP4 on the new node in unattended mode.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
The binary-only mode is used automatically by SQL Server 2000 SP4 when you add a new node to an existing failover cluster. This is true when the existing nodes in the cluster are already running SQL Server 2000 SP4. The binary-only mode is intended to let SQL Server 2000 SP4 binaries be installed only on the new node. The binary-only mode is also intended to let SQL Server 2000 SP4 not run the database scripts of SQL Server 2000 SP4. This occurs when the new node is acting as a passive node in the cluster and when you run the Setup program from the new node.
Note You can find the instructions for how to apply this hotfix in the readme file that is included with the hotfix files.
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For more information about the terminology that Microsoft uses when Microsoft corrects software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Keywords: kbqfe kbhotfixserver kbfix kbbug KB905286
