Microsoft KB Archive/898709

= FIX: Error message when you use SQL Server 2000: &quot;Time out occurred while waiting for buffer latch type 3&quot; =

Article ID: 898709

Article Last Modified on 11/2/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition
 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Enterprise Edition
 * Microsoft SQL Server 2000 Personal Edition

-



Bug #: 474287 (SQL Server 8.0)



Notice
''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 applying this hotfix package
 * Whether you must restart the computer after you apply this hotfix package
 * Whether this hotfix package is replaced by any other hotfix package
 * Whether you must make any registry changes after you apply this hotfix package
 * The files that are contained in this hotfix package



SYMPTOMS
In SQL Server 2000, you may notice that the following error message has been logged in the SQL Server Errorlog file:

Time out occurred while waiting for buffer latch type 3,bp 0x1751380, page 1:1572), stat 0xb, object ID 2:600296667:2, EC 0x2C131568 : 0, waittime 72300. Continuing to wait. Waiting for type 0x3, current count 0xc0002a, current owning EC 0x2C131568.

In the error message, latch type 3 indicates that the SQL Server process is trying to acquire an update (UP) latch.

For a list of all publicly released SQL Server 2000 post-service pack hotfixes, see the following article in the Microsoft Knowledge Base:

894905 Cumulative list of the hotfixes that are available for SQL Server 2000 Service Pack 4



CAUSE
This problem occurs because the latch wait occurs. The SQL Server process is waiting to acquire a UP latch on the buffer on which it already has acquired an exclusive (EX) latch. This problem only occurs under rare conditions.



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 Microsoft 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:

http://support.microsoft.com/contactus/?ws=support

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.

Important If you have Microsoft SQL Server 2000 Service Pack 4 (SP4) installed on your computer, you must install Cumulative Hotfix for SQL Server 2000 Service Pack 4 - Build 2187 to fix this problem.

To obtain Cumulative Hotfix for SQL Server 2000 Service Pack 4 - Build 2187, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?familyid=9c9ab140-bdee-44df-b7a3-e6849297754a

Prerequisites
 This hotfix requires Microsoft SQL Server 2000 Service Pack 3a (SP3a).

For information about how to obtain SQL Server 2000 SP3a, see the following article in the Microsoft Knowledge Base:

290211 How to obtain the latest SQL Server 2000 service pack

 Cumulative Hotfix for SQL Server 2000 Service Pack 4 - Build 2187 requires SQL Server 2000 SP4.

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 after you apply this hotfix.

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 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.

Microsoft SQL Server 2000 SP3a-based hotfix
SQL Server 2000, 32-bit version

SQL Server 2000, Itanium architecture version



WORKAROUND
To work around this problem, restart the SQL Server service.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
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 software update terminology, 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

Keywords: kbexpertiseadvanced kbfix kbhotfixserver kbqfe kbpubtypekc KB898709

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.