Article ID: 902955 - View products that this article applies to.
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:
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
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.
Hotfix informationA 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:
http://support.microsoft.com/contactus/?ws=supportNote 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.
PrerequisitesYou 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:
(http://support.microsoft.com/kb/290211/ )How to obtain the latest SQL Server 2000 service pack
Restart informationYou do not have to restart the computer after you apply this hotfix.
Registry informationYou do not have to change the registry.
Hotfix file informationThis 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
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
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
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:
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:
822499For 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:
(http://support.microsoft.com/kb/822499/ )New naming schema for Microsoft SQL Server software update packages
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 902955 - Last Review: October 9, 2011 - Revision: 4.0