Article ID: 936232 - View products that this article applies to.
Bug #: 50001151 (SQL Hotfix)
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:
Under high memory pressure, an access violation may occur when you try to log in to an instance of Microsoft SQL Server 2000. Therefore, you cannot log in.
This problem occurs because the wait_for_client_connects thread does not have a valid execution context.
For more information about a similar problem, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/875445/ )FIX: An access violation exception may occur when you try to access SQL Server on a computer that is running under low memory conditions
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.
PrerequisitesTo apply this hotfix, you must have SQL Server 2000 Service Pack 4 (SP4) installed. 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:
(https://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.
Hotfix replacement informationThis hotfix is not replaced by any other hotfixes.
Registry informationYou do not have to change the registry.
File informationThis 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.
Collapse this tableExpand this table
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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:
822499For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/822499/ )New naming schema for Microsoft SQL Server software update packages
(https://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 936232 - Last Review: October 8, 2011 - Revision: 2.0