Knowledge Base

FIX: Attention Events that Occur During Blocking May Cause SQL Server to Stop Responding, Cause AVs or Other Errors

Article ID: 265838

Article Last Modified on 9/6/2006

APPLIES TO

Microsoft SQL Server 6.5 Service Pack 5a

This article was previously published under Q265838

BUG #: 19025 (SQLBUG_65)

SYMPTOMS

Attention events that are sent to the server during blocking, may result in access violations, may cause SQL Server to stop responding (hang), and/or the following errors may be written to the ERRORLOG:

Error : 1108, Severity: 21, State: 1
Cannot deallocate extent 736, database 2. Object id 0, index id 0, status 0 in extent does not match object id -809, index id 0, status 0 in object being deallocated. Run DBCC CHECKALLOC.

Error : 826, Severity: 20, State: 2
Attempt made to hold allocation page 10752 that is already in Pss pool. Database 'tempdb'

WORKAROUND

Resolve all blocking problems and reduce the frequency of attention events sent to the server. This can help reduce the likelihood of encountering this problem.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.5. This problem has been corrected in the Post Service Pack 5a Update for Microsoft SQL Server version 6.5. To install the Post Service Pack 5a Update, you must have either SQL Server 6.5 SP5 or SP5a installed.

For information about how to download and install the SQL Server 6.5 Service Pack 5a, refer to the following article in the Microsoft Knowledge Base:

197177 INF: How to Obtain SQL Server 6.5 Service Pack 5a

If you already have SQL Server 6.5 SP5 or SP5a installed, you can download the Post SP5a Update from the following article in the Microsoft Knowledge Base:

274036 INF: How to Obtain SQL Server 6.5 Post Service Pack 5a Update

For more information, contact your primary support provider.

Additional query words: error 1108 826

Keywords: kbbug kbfix kbqfe KB265838

Microsoft KB Archive/265838

Contents