Microsoft KB Archive/923296

= FIX: Log Reader Agent fails, and an assertion error message is logged when you use transactional replication in SQL Server 2005 =

Article ID: 923296

Article Last Modified on 11/20/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Standard X64 Edition
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems

-



BUG #: 1032 (SQL Hotfix)



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.



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



SYMPTOMS
When you use transactional replication in Microsoft SQL Server 2005, you may experience the following symptoms:
 * Log Reader Agent fails. Additionally, the Log Reader Agent connection is dropped.
 * An assertion error message is logged in the SQL Server error log.



Hotfix information
A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

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

Prerequisites
You must have SQL Server 2005 Service Pack 1 (SP1) installed to apply this hotfix. For more information about how to obtain SQL Server 2005 Service Pack 1, 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.

File information
This 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.

64-bit hotfix for Itanium processors


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

Error log information
When this problem occurs, the following information is logged in the SQL Server error log:   2006-05-22 14:22:07.49 spid101     ***Stack Dump being sent to E:\Program Files\Microsoft SQL Server\MSSQL\LOG\SQLDump0028.txt 2006-05-22 14:22:07.49 spid101    * ******************************************************************************* 2006-05-22 14:22:07.49 spid101    * 2006-05-22 14:22:07.49 spid101    * BEGIN STACK DUMP: 2006-05-22 14:22:07.49 spid101    *   05/22/06 14:22:07 spid 101 2006-05-22 14:22:07.49 spid101    * 2006-05-22 14:22:07.49 spid101    * Location:    logscan.cpp:2277 2006-05-22 14:22:07.49 spid101    * Expression:  startLSN >= m_curLSN 2006-05-22 14:22:07.49 spid101    * SPID:        101 2006-05-22 14:22:07.49 spid101    * Process ID:  1716 2006-05-22 14:22:07.49 spid101    * 2006-05-22 14:22:07.49 spid101    * Input Buffer 109 bytes - 2006-05-22 14:22:07.49 spid101    *                     16 00 00 00 12 00 00 00 02 00 00 00 00 00 00 00 00 00 2006-05-22 14:22:07.49 spid101    *        s p _ r e p  01 00 00 00 0b 00 73 00 70 00 5f 00 72 00 65 00 70 00 2006-05-22 14:22:07.49 spid101    *  l c m d s     &  ô 6c 00 63 00 6d 00 64 00 73 00 00 00 00 00 26 04 04 f4   2006-05-22 14:22:07.49 spid101     *       &        &  ÿ 01 00 00 00 00 26 04 04 00 00 00 00 00 00 26 04 04 ff   2006-05-22 14:22:07.49 spid101     *  ÿÿÿ  ¥      &  ;   ff ff ff 00 00 a5 0a 00 00 00 00 00 26 04 04 3b 0b 00 2006-05-22 14:22:07.49 spid101    *     &        &   ¡  00 00 00 26 04 04 00 00 00 00 00 00 26 04 04 20 a1 07 2006-05-22 14:22:07.49 spid101    *                     00 :  :   2006-05-22 14:22:10.58 spid101     Error: 17066, Severity: 16, State: 1. 2006-05-22 14:22:10.58 spid101    SQL Server Assertion: File: , line=2277 Failed Assertion = 'startLSN >= m_curLSN'. 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. 2006-05-22 14:22:10.58 spid101    Error: 3624, Severity: 20, State: 1. 2006-05-22 14:22:10.58 spid101    A system assertion check has failed. Check the SQL Server error log for details 2006-05-22 14:22:10.58 spid101    Using 'dbghelp.dll' version '4.0.5' 2006-05-22 14:22:10.60 spid101    **Dump thread - spid = 101, PSS = 0x4C4412C8, EC = 0x4C4412D0: :  :   2006-05-17 10:31:54.54 spid79      Error: 17066, Severity: 16, State: 1. 2006-05-17 10:31:54.54 spid79     SQL Server Assertion: File: , line=2528 Failed Assertion = 'm_noOfScAlloc == 0'. 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. 2006-05-17 10:31:54.64 spid77     Error: 14151, Severity: 18, State: 1. 2006-05-17 10:31:54.64 spid77     Replication-Replication Transaction-Log Reader Subsystem: agent SQL1-Production failed. The process could not execute 'sp_replcmds' on 'SQL1'.

Keywords: kbtshoot kbbug kbfix kbqfe kbpubtypekc kbexpertiseadvanced kbhotfixserver KB923296

-

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

© Microsoft Corporation. All rights reserved.