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 your computer after you install 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

Consider the following scenario. You install Microsoft SQL Server 2000 Service Pack 4 (SP4). Then, you run the Sqldiag.exe utility. In this scenario, a Buffer Overrun check dialog box appears, and you receive the following message: Notes

•	The Sqldiag.exe utility is a stand-alone utility.
•	You must be logged on as a member of the Administrators group to run the Sqldiag.exe utility.
•	The Buffer Overrun check dialog box represents a Microsoft investment in technologies that is designed to increase security across products. In this case, compilation code detected the presence of the potential for a buffer overrun condition and trapped this to a dialog box. The dialog box allows the user to accept or to deny and thus prevent any malicious attempts to compromise system integrity. In this case, this is redundant because Sqldiag.exe is a utility that has a hard-coded check that only allows Sqldiag.exe to be run by Administrators. If a malicious user was able to instantiate this code, the malicious user would already have Administrators rights on the computer and would not need any additional attack vector. Therefore, this check is not blocking any attack vector in this situation and does not represent a security issue in the product.

Back to the top

This problem occurs because, when you install SQL Server 2000 SP4, the following registry key is modified for the default instance:The character length value of this registry key is increased. However, the Sqldiag.exe utility does not support a larger value for this registry key.

Note Because the Sqldiag.exe utility is stand-alone, this larger registry value is not a major problem. Because you must be a member of the Administrators group to run the Sqldiag.exe utility, only a small subset of users are affected.

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 SQL Server 2000 Service Pack 4 (SP4) installed to apply this hotfix.

For more information about how to obtain SQL Server 2000 Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:

Restart information

You do not have to restart the computer 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 describes. This hotfix may not contain of 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 tool in Control Panel.

SQL Server 2000 32-bit versions

   Date         Time   Version         Size       File name
   ---------------------------------------------------------------
   06-Jun-2005  22:46  8.11.50523.0      239,104  Mssdi98.dll      
   17-May-2005  01:51  2000.80.1025.0     57,904  Osql.exe         
   12-Jul-2005  17:24  2000.80.2148.0    430,080  Pfclnt80.dll     
   17-Jun-2005  00:15                    552,068  Procsyst.sql
   17-Jun-2005  00:15                     18,810  Sp4_serv_qfe.sql
   08-Jul-2005  01:50  2000.80.2148.0    323,584  Sqlagent.exe     
   08-Jul-2005  02:51  2000.80.2148.0    118,784  Sqldiag.exe      
   08-Jul-2005  02:09  2000.80.2148.0    102,400  Sqlfth75.dll     
   08-Jul-2005  16:07  2000.80.2148.0  9,154,560  Sqlservr.exe     

SQL Server 2000 64 bit version

   Date         Time   Version         Size        File name     Platform
   ----------------------------------------------------------------------
   12-Jul-2005  19:42  8.11.50523.0       758,784  Mssdi98.dll   IA-64
   12-Jul-2005  19:41  7.10.3052.4        348,160  Msvcr71.dll   x86
   12-Jul-2005  19:41  2000.80.2148.0   1,187,840  Pfclnt80.dll  IA-64
   12-Jul-2005  19:42                     552,068  Procsyst.sql
   12-Jul-2005  19:42  2000.80.2148.0   1,061,376  Sqlagent.exe  IA-64
   12-Jul-2005  19:42  2000.80.2148.0     334,336  Sqldiag.exe   IA-64
   12-Jul-2005  19:42  2000.80.2148.0     246,784  Sqlfth75.dll  IA-64
   12-Jul-2005  19:42  2000.80.2148.0  30,181,888  Sqlservr.exe  IA-64

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

Back to the top

To work around this problem, ignore the message that is mentioned in the "Symptoms" section. Then, click OK in the Buffer Overrun check dialog box. When you click OK, the Sqldiag.exe utility will not collect the following information:

•	Library version information
•	Configuration information
•	Current user information
•	Lock information
•	Database information
•	Product information
•	Extended procedures information
•	Process information
•	Input buffers information
•	Head blockers information
•	Computer information

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

You should not modify the Scripts registry value to prevent this problem. Additionally, the Rebuild master utility (Rebuildm.exe) uses the Scripts registry value to build a version of the system databases that is consistent with the currently installed service pack level of SQL Server.

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 Microsoft corrects software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top