Article ID: 983564 - Last Review: May 30, 2011 - Revision: 7.0

FIX: Error message when you use database mirroring in Microsoft SQL Server 2005, Microsoft SQL Server 2008, or Microsoft SQL Server 2008 R2, and an assertion failure occurs intermittently

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Microsoft distributes Microsoft SQL Server 2005, Microsoft SQL Server 2008, or Microsoft SQL Server 2008 R2 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 Microsoft SQL Server 2005, Microsoft SQL Server 2008, or Microsoft SQL Server 2008 R2 fix release.

On This Page

Expand all | Collapse all

SYMPTOMS

You set up Database Mirroring between two Microsoft SQL Server 2005, Microsoft SQL Server 2008, or Microsoft SQL Server 2008 R2 servers. In this situation, you notice an intermittent assertion failure. Additionally, the following error message is logged in the SQL Server error log file on the mirror server: 
<Date Time> spid<ID>s     Using 'dbghelp.dll' version '4.0.5'
<Date Time> spid<ID>s     **Dump thread - spid = 22, PSS = 0x0000000082E34B60, EC = 0x000000008600C1C0
<Date Time> spid<ID>s     ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump<XXXX>.txt
<Date Time> spid<ID>s     * *******************************************************************************
<Date Time> spid<ID>s     *
<Date Time> spid<ID>s     * BEGIN STACK DUMP:
<Date Time> spid<ID>s     *   04/17/10 01:18:26 spid 22
<Date Time> spid<ID>s     *
<Date Time> spid<ID>s     * Location:  loglock.cpp:834
<Date Time> spid<ID>s     * Expression:      result == LCK_OK

...

<Date Time> spid<ID>s     Error: 17066, Severity: 16, State: 1.
<Date Time> spid<ID>s     SQL Server Assertion: File: <loglock.cpp>, line=834 Failed Assertion = 'result == LCK_OK'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
<Date Time> spid<ID>s     Error: 3624, Severity: 20, State: 1.
<Date Time> spid<ID>s     A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.
Additionally, a mini-dump is generated with name "SQLDump<XXXX>.dump" in the SQL Server error log file folder.
Back to the top

CAUSE

This issue occurs because the migrated locks on the page are refcounted on the mirror. Lock escalation does not release these refcounted locks. The outstanding locks on the page that are not released during lock escalation cause a conflict on the mirror during the latter deallocation and allocation operation of this page.
Back to the top

RESOLUTION

Cumulative update information

SQL Server 2005

The fix for this issue was first released in Cumulative Update 10. For more information about how to obtain this cumulative update package for SQL Server 2005, click the following article number to view the article in the Microsoft Knowledge Base:
983329  (http://support.microsoft.com/kb/983329/ ) Cumulative update package 10 for SQL Server 2005 Service Pack 3
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
960598  (http://support.microsoft.com/kb/960598/ ) The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released

SQL Server 2008 Service Pack 1

The fix for this issue was first released in Cumulative Update 9 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2083921  (http://support.microsoft.com/kb/2083921/LN/ ) Cumulative update 9 for SQL Server 2008 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970365  (http://support.microsoft.com/kb/970365/LN/ ) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2008 Service Pack 2

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2289254  (http://support.microsoft.com/kb/2289254/ ) Cumulative update 1 for SQL Server 2008 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2402659  (http://support.microsoft.com/kb/2402659/ ) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2261464  (http://support.microsoft.com/kb/2261464/ ) Cumulative update package 3 for SQL Server 2008 R2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981356  (http://support.microsoft.com/kb/981356/ ) The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top

REFERENCES

For more information about the SQL Server error log, visit the following Microsoft Developer Network (MSDN) website:
Viewing the SQL Server error log (http://msdn.microsoft.com/en-us/library/ms187885(sql.90).aspx)
For more information about Database Mirroring, visit the following MSDN website:
Overview of Database Mirroring (http://msdn.microsoft.com/en-us/library/ms189852(sql.90).aspx)
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897  (http://support.microsoft.com/kb/935897/ ) An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
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:
822499  (http://support.microsoft.com/kb/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  (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates
Back to the top
APPLIES TO
  • Microsoft SQL Server 2005 Service Pack 3
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 Workgroup
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Standard
  • Microsoft SQL Server 2008 R2 Workgroup
Back to the top
Keywords: 
kbfix kbqfe kbexpertiseadvanced kbsurveynew KB983564
Back to the top