Microsoft KB Archive/278855: Difference between revisions
m (Text replacement - ">" to ">") |
m (Text replacement - "&" to "&") |
||
Line 53: | Line 53: | ||
2000-02-29 14:25:19.26 kernel SQL Server Assertion: File: <xdesmgr.c>, line=2926<br /> | 2000-02-29 14:25:19.26 kernel SQL Server Assertion: File: <xdesmgr.c>, line=2926<br /> | ||
Failed Assertion = '!(OldestActiveLSN > xbeginLsn) & | Failed Assertion = '!(OldestActiveLSN > xbeginLsn) && !OldestActiveLSN.IsInvalid()'. | ||
</div> | </div> |
Latest revision as of 12:36, 21 July 2020
Article ID: 278855
Article Last Modified on 3/14/2006
APPLIES TO
- Microsoft SQL Server 7.0 Standard Edition
This article was previously published under Q278855
BUG #: 57693 (SQLBUG_70)
SYMPTOMS
The following assertion may be seen in the SQL Server Errorlog when log shipping is set up on a replicated database:
CAUSE
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.
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 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.
Additional query words: xdesmgr 2000-02-29 14:25:19.26 2926
Keywords: kbbug kbfix KB278855