FIX: Assert in Errorlog During WITH STANDBY Recovery on a Replicated Database

Article translations Article translations
Article ID: 278855 - View products that this article applies to.
This article was previously published under Q278855
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 57693 (SQLBUG_70)
Expand all | Collapse all


The following assertion may be seen in the SQL Server Errorlog when log shipping is set up on a replicated database:
2000-02-29 14:25:19.26 kernel SQL Server Assertion: File: <xdesmgr.c>, line=2926
Failed Assertion = '!(OldestActiveLSN > xbeginLsn) && !OldestActiveLSN.IsInvalid()'.


This behavior occurs when SQL Server is trying to write an abort log record for a replicated transaction, and is trying to gather information about other active transactions. However, an invalid LSN is used, which causes an assertion.


Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.


Article ID: 278855 - Last Review: October 21, 2013 - Revision: 2.1
  • Microsoft SQL Server 7.0 Standard Edition
kbnosurvey kbarchive kbbug kbfix KB278855

Contact us for more help

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