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

View products that this article applies to.

This article was previously published under Q278855

BUG #: 57693 (SQLBUG_70)

Expand all | Collapse all

SYMPTOMS

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()'.

Back to the top

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.

Back to the top

STATUS

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 (http://support.microsoft.com/kb/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.

Back to the top