This article has been archived. It is offered "as is" and will no longer be updated.
Bug #: 474330 (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.
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
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:
Getting registry information.
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.
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.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
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:
290211 How to obtain the latest SQL Server 2000 service pack
You do not have to restart the computer after you apply this hotfix.
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.
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
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
Current user information
Extended procedures information
Input buffers information
Head blockers information
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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:
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
Microsoft SQL Server 2000 Developer Edition, Microsoft SQL Server 2000 Enterprise Edition, Microsoft SQL Server 2000 Personal Edition, Microsoft SQL Server 2000 Standard Edition, Microsoft SQL Server 2000 Workgroup Edition