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
•	Information about whether you must restart the computer after you apply the hotfix package
•	Information about whether the hotfix package is replaced by any other hotfix package
•	Information about whether you must make any registry changes
•	The files that are contained in the hotfix package

Back to the top

In SQL Server 2000, you receive an error message when you try to rebuild the master database. This problem occurs when the following conditions are true:

•	You are running SQL Server 2000 Service Pack 4 (SP4) 64-bit, and you have installed hotfix builds. Note This problem does not occur in SQL Server 2000 32-bit.
•	The last hotfix build that you have installed is not earlier than hotfix build 2145 and is not later than hotfix build 2153.

The error message text is similar to the following: If you try to rebuild the master database by running the Setup program graphical user interface (GUI) in verbose log mode, the following message is written to the Setup log file: For a list of all publicly released SQL Server 2000 Post-Service Pack 4 hotfixes, see the following article in the Microsoft Knowledge Base:

Back to the top

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.

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it 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 Product Support Services to obtain the hotfix. For a complete list of Microsoft Product 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

•	You must have Microsoft SQL Server 2000 Service Pack 4 (SP4) 64-bit installed to apply this hotfix. For more information about how to obtain SQL Server 2000 Service Pack 4 64-bit, click the following article number to view the article in the Microsoft Knowledge Base: 290211 (http://support.microsoft.com/kb/290211/) How to obtain the latest SQL Server 2000 service pack
•	If you are installing hotfix build 2156, you must uninstall hotfix build 2145 through hotfix build 2153 before you install hotfix build 2156.
•	If you are installing hotfix build 2159 or a later hotfix build, you do not have to uninstall any previous hotfixes.

Restart information

You do not have to change the registry after you apply this hotfix.

Registry information

You do not have to change the registry.

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 of all the files that you must have to update a product fully 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 tool in Control Panel.

SQL Server 2000 64-bit version, build 2156

File name	File version	File size	Date	Time	Platform
Mssdi98.dll	8.11.50523.0	758,784	06-Jun-2005	22:46	IA-64
Odsole70.dll	2000.80.2156.0	150,528	01-Sep-2005	06:06	IA-64
Pfclnt80.dll	2000.80.2156.0	1,187,840	01-Sep-2005	06:22	IA-64
Replprov.dll	2000.80.2156.0	538,624	01-Sep-2005	06:09	IA-64
Sqlagent.exe	2000.80.2156.0	1,061,376	01-Sep-2005	06:26	IA-64
Sqldiag.exe	2000.80.2156.0	334,336	01-Sep-2005	06:24	IA-64
Sqldmo.dll	2000.80.2156.0	13,860,352	01-Sep-2005	06:30	IA-64
Sqlfth75.dll	2000.80.2156.0	246,784	01-Sep-2005	06:09	IA-64
Sqlservr.exe	2000.80.2156.0	24,914,432	01-Sep-2005	10:27	IA-64
Svrnetcn.dll	2000.80.2156.0	427,520	01-Sep-2005	06:21	IA-64

SQL Server 2000 64-bit version, build 2159

File name	File version	File size	Date	Time	Platform
Mssdi98.dll	8.11.50523.0	758,784	06-Jun-2005	22:46	IA-64
Odsole70.dll	2000.80.2159.0	150,528	15-Sep-2005	20:38	IA-64
Pfclnt80.dll	2000.80.2159.0	1,187,840	15-Sep-2005	20:58	IA-64
Replprov.dll	2000.80.2159.0	538,624	15-Sep-2005	20:44	IA-64
Sqlagent.exe	2000.80.2159.0	1,061,376	15-Sep-2005	20:59	IA-64
Sqldiag.exe	2000.80.2159.0	334,336	15-Sep-2005	21:00	IA-64
Sqldmo.dll	2000.80.2159.0	13,860,352	15-Sep-2005	21:04	IA-64
Sqlfth75.dll	2000.80.2159.0	246,784	15-Sep-2005	20:39	IA-64
Sqlservr.exe	2000.80.2159.0	24,944,640	16-Sep-2005	02:55	IA-64
Svrnetcn.dll	2000.80.2159.0	427,520	15-Sep-2005	20:56	IA-64
Sqlevn70.rll	2000.80.2159.0	35,328	16-Sep-2005	02:52	Not Applicable

Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top

For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the terminology that Microsoft uses when it corrects software after the software is released, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Rebuild the master database

You may have to rebuild the master database on computers that have SQL Server 2000 SP4 installed and on computers that have SQL Server 2004 post-SP4 hotfix builds installed. To do this, follow these steps:

Note You cannot use the Setup program GUI to rebuild the master database on computers that have SQL Server 2000 SP4 installed.

1.	Perform one of the following actions: • Install SQL Server 2000 hotfix build 2159 or a later hotfix build. • Uninstall all hotfix builds from hotfix build 2145 to hotfix build 2153. Then, install hotfix build 2156.
2.	If the SQL Server 2000 authentication mode is set to Windows Authentication Mode (Windows only), use SQL Server Enterprise Manager to temporarily change the authentication mode to Mixed Mode (SQL Server and Windows). Note If the target server has the SQL Server 2000 authentication mode set to Windows Authentication Mode, you cannot rebuild the master database. When you try to connect to the server that is running SQL Server, you receive the following error message: Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server connection.
3.	Run the following setup command: setup /i {{ProductCode} | OriginalInstallationMSIFile} /qb REINSTALL=All REINSTALLMODE=amus {SAPWD=password | BLANKSAPWD=1} Notes • ProductCode represents the product code. To obtain the product code, locate the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Setup\ProductCode • You must specify either BLANKSAPWD or SAPWD, even when the target server that is running SQL Server is using Windows Authentication Mode. If you do not specify either BLANKSAPWD or SAPWD, you cannot rebuild the master database. When you try to run the setup command, you receive the following error message: You must provide a system administrator (sa) password to continue installation.
4.	If you did not change the SQL Server 2000 authentication mode in step 2, go to step 6.
5.	Use SQL Server Enterprise Manager to change the SQL Server 2000 authentication mode back to Windows Authentication Mode.
6.	You may have to use SQL Server Enterprise Manager to change the following server properties after you successfully rebuild the master database: • The security mode • The cross db ownership chaining option • The Error Reporting option (Dr. Watson error reporting)

Back to the top