FIX: SQL Server 2005 database engine generates failed assertion errors when you use the Replication Monitor to monitor the distribution database

Article translations Article translations
Article ID: 934106 - View products that this article applies to.
Bug: #50000948 (SQL Hotfix)
Notice
Microsoft distributes Microsoft SQL Server 2005 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 2005 fix release.
Expand all | Collapse all

On This Page

This article describes the following about this hotfix release:
  • The issues that are fixed by this hotfix package
  • The prerequisites for installing the hotfix package
  • Whether you must restart the computer after you install the hotfix package
  • Whether the hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes
  • The files that are contained in the hotfix package

SYMPTOMS

When you use Replication Monitor to monitor the distribution database in Microsoft SQL Server 2005, the SQL Server 2005 database engine repeatedly generates failed assertion errors. Additionally, the session of Replication Monitor is disconnected temporarily. When the failed assertion errors occur, you experience the following problems:
  • If you are running some Transact-SQL statements or some stored procedures against the instance of SQL Server 2005, the Transact-SQL statements or the stored procedures do not run.
  • If an application connects to the instance of SQL Server 2005, the connection is closed.
In this situation, the replication performance information is not visible. When you press F5 to update Replication Monitor, Replication Monitor reconnects, and the information is up to date.

If you experience the problem when you are running some Transact-SQL statements or some stored procedures, the Transact-SQL statements or the stored procedures run successfully if you reconnect to the instance of SQL Server 2005 and then run the Transact-SQL statements or the stored procedures.

If an application cannot connect to the instance, you can reconnect successfully to the instance.

RESOLUTION

A 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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=support
Note 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.

Prerequisites

You must have SQL Server 2005 Service Pack 2 installed.

For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
913089 How to obtain the latest service pack for SQL Server 2005

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.

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.
SQL Server 2005 32-bit version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.sqlserver.maintenanceplantasks.dll9.0.3154.0296,30410-Mar-200705:49x86
Mssqlsystemresource.ldfNot Applicable524,28810-Mar-200702:59Not Applicable
Mssqlsystemresource.mdfNot Applicable40,173,56810-Mar-200702:59Not Applicable
Rdistcom.dll2005.90.3154.0644,46410-Mar-200705:49x86
Msmdlocal.dll9.0.3154.015,930,22410-Mar-200705:49x86
Sqlaccess.dll2005.90.3154.0350,57610-Mar-200705:49x86
Sqlservr.exe2005.90.3154.029,191,53610-Mar-200705:49x86
SQL Server 2005 x64-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.sqlserver.maintenanceplantasks.dll9.0.3154.0296,30410-Mar-200705:49x86
Mssqlsystemresource.ldfNot Applicable524,28810-Mar-200702:59Not Applicable
Mssqlsystemresource.mdfNot Applicable40,173,56810-Mar-200702:59Not Applicable
Rdistcom.dll2005.90.3154.0828,27210-Mar-200711:12x64
Msmdlocal.dll9.0.3154.015,930,22410-Mar-200705:49x86
Sqlaccess.dll2005.90.3154.0357,74410-Mar-200711:12x86
Sqlservr.exe2005.90.3154.038,655,34410-Mar-200711:12x64

STATUS

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

MORE INFORMATION

This issue only temporarily affects replication performance. This issue is not fatal to the SQL Server 2005 database engine. This issue has no lingering side effects. Additionally, this issue only occurs at certain times and in certain situations. If you retry the same command, the operation will probably succeed.

To determine whether you are experiencing this problem, open the SQL Server Errorlog file. If you have this problem, you see the following text:
Failed Assertion = 'LCK_SUCCESS (result)'
At the time of the assertion, a minidump file is generated in the following folder:
Drive:\Program Files\Microsoft SQL Server\MSSQL.x\MSSQL\LOG
Note MSSQL.x is a placeholder for the instance ID for the instance of SQL Server. You can determine the corresponding value for the system from the value of the MSSQLSERVER registry entry in the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL\
If this issue frequently occurs, you can delete or archive old minidump files from the LOG folder to free drive space.

The SQL Server Errorlog file displays the problem command, a stack dump, and the assertion condition.

For example, you can find the problem command by using the following text in the SQL Server Errorlog file:
2006-12-18 09:43:01.52 spid345 * Location: IndexDataSet.cpp:18180
2006-12-18 09:43:01.52 spid345 * Expression: LCK_SUCCESS (result)
2006-12-18 09:43:01.52 spid345 * SPID: 345
2006-12-18 09:43:01.52 spid345 * Process ID: 1864
2006-12-18 09:43:01.52 spid345 *
2006-12-18 09:43:01.52 spid345 * Input Buffer 470 bytes -
2006-12-18 09:43:01.52 spid345 * use [master] exec [distribution].sys.sp_replmonitorhelpsubsc
2006-12-18 09:43:01.52 spid345 * ription @publisher = N'MyPublisherServer', @publisher_db = N'mydbname
2006-12-18 09:43:01.52 spid345 * ', @publication = N'mypub', @mode = 0, @exclude_anonymous = 0, @r
2006-12-18 09:43:01.52 spid345 * efreshpolicy = N'0'
2006-12-18 09:43:07.03 spid345 Error: 17066, Severity: 16, State: 1.
2006-12-18 09:43:07.03 spid345 SQL Server Assertion: File: <IndexDataSet.cpp>, line=18180 Failed Assertion = 'LCK_SUCCESS (result)'. 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 make sure that in-memory data structures are not corrupted.
The problem command may vary. Additionally, the source code line number of the assertion may vary between versions and platforms, such as the 32-bit platform and the 64-bit platform. The failed assertion condition that matches this issue is the LCK_SUCCESS (result) condition.

Call stack information

0:000> kL 100
Child-SP          RetAddr           Call Site
00000000`38637930 00000000`034b1e9c kernel32!RaiseException+0x73
00000000`38637a00 00000000`02fd8811 sqlservr!CDmpDump::Dump+0x7c
00000000`38637a50 00000000`02fcbeed sqlservr!CImageHelper::DoMiniDump+0x4e1
00000000`38637bc0 00000000`02ca9159 sqlservr!stackTrace+0x83d
00000000`38639110 00000000`02d71478 sqlservr!utassert_fail+0x6c9
00000000`38639ae0 00000000`02d8d593 sqlservr!UnlockDeallocatedPage+0x228
00000000`38639c20 00000000`02d9629b sqlservr!RemoveBTreePageIfUnchanged+0x113
00000000`38639ca0 00000000`02d9b247 sqlservr!BTreeRow::DeleteRecord+0xa9b
00000000`38639e70 00000000`02f5148e sqlservr!IndexDataSetSession::SetData+0x23c7
00000000`3863e0b0 00000000`02580bc1 sqlservr!RowsetNewSS::SetData+0x6e
00000000`3863e100 00000000`01c5d371 sqlservr!CValRowMult::SetDataX+0x1d1
00000000`3863e1c0 00000000`02616916 sqlservr!CEs::GeneralEval4+0x101
00000000`3863e270 00000000`02551d66 sqlservr!CQScanUpdateNew::GetRow+0x636
00000000`3863e300 00000000`0218f2ac sqlservr!CQueryScan::GetRow+0x76
00000000`3863e330 00000000`021908de sqlservr!CXStmtQuery::ErsqExecuteQuery+0x66c
00000000`3863e480 00000000`021910ec sqlservr!CXStmtDML::XretDMLExecute+0x2fe
00000000`3863e550 00000000`020d38a5 sqlservr!CXStmtDML::XretExecute+0xac
00000000`3863e580 00000000`020daac5 sqlservr!CMsqlExecContext::ExecuteStmts<1,1>+0x4f5
00000000`3863e6d0 00000000`02123668 sqlservr!CMsqlExecContext::FExecute+0x775
00000000`3863e880 00000000`02148d62 sqlservr!CSQLSource::Execute+0xa38
00000000`3863e9f0 00000000`0214cd9c sqlservr!CStmtExecProc::XretLocalExec+0x262
00000000`3863ea70 00000000`02141250 sqlservr!CStmtExecProc::XretExecExecute+0x54c
00000000`3863f130 00000000`020d38a5 sqlservr!CXStmtExec::XretExecute+0x20
00000000`3863f170 00000000`020daac5 sqlservr!CMsqlExecContext::ExecuteStmts<1,1>+0x4f5
00000000`3863f2c0 00000000`02123668 sqlservr!CMsqlExecContext::FExecute+0x775
00000000`3863f470 00000000`01f46a5a sqlservr!CSQLSource::Execute+0xa38
00000000`3863f5e0 00000000`01f4bbab sqlservr!process_request+0x43a
00000000`3863f860 00000000`03411dd6 sqlservr!process_commands+0x32b
00000000`3863fb40 00000000`034122ef sqlservr!SOS_Task::Param::Execute+0x116
00000000`3863fc40 00000000`03417713 sqlservr!SOS_Scheduler::RunTask+0xcf
00000000`3863fcb0 00000000`033f6a30 sqlservr!SOS_Scheduler::ProcessTasks+0x1c3
00000000`3863fd10 00000000`033faed6 sqlservr!SchedulerManager::WorkerEntryPoint+0x1f0
00000000`3863fda0 00000000`03400f67 sqlservr!SystemThread::RunWorker+0xd6
00000000`3863fde0 00000000`034015b1 sqlservr!SystemThreadDispatcher::ProcessWorker+0x337
00000000`3863fe70 00000000`781337a7 sqlservr!SchedulerManager::ThreadEntryPoint+0x271
00000000`3863ff20 00000000`78133864 msvcr80!_callthreadstartex+0x17
00000000`3863ff50 00000000`77d6b69a msvcr80!_threadstartex+0x84
00000000`3863ff80 00000000`00000000 kernel32!BaseThreadStart+0x3a
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
This hotfix is also included in the cumulative update package (build 3161) for SQL Server 2005 Service Pack 2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
935356 Cumulative update package (build 3161) for SQL Server 2005 Service Pack 2 is available

Properties

Article ID: 934106 - Last Review: October 8, 2011 - Revision: 3.0
APPLIES TO
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
Keywords: 
kbautohotfix kbsql2005repl kbfix kbexpertiseadvanced kbHotfixServer kbqfe KB934106

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com