FIX: LogReader Fails with Error 14151 or Error 624

Last reviewed: April 30, 1997
Article ID: Q156860
The information in this article applies to:
  • Microsoft SQL Server, versions 6.0 and 6.5
BUG #: 15539 (Windows NT: 6.0)
       15571 (6.5)

SYMPTOMS

The LogReader process fails with either of the following errors:

  • Error 14151: Replicated transaction (x,y) not found in log; unable to run sp_repldone on 'PUBLISHER'
  • Error 624: Attempt to retrieve row from page via RID failed because the requested RID has a higher number than the last RID on the page. %S_RID.%S_PAGE.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server versions 6.0 and 6.5. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server version 6.0, and in U.S. Service Pack 1 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.

MORE INFORMATION

Sp_repldone scans the log for the next replicated transaction, starting from the oldest distributed transaction. If the transaction log contains a large number of non-replicated transactions between replicated transactions, and the DUMP TRANSACTION command is started after sp_repldone, DUMP TRANSACTION truncates past the oldest non-distributed transaction. Therefore, sp_repldone does not update the checkpoint record with the proper value for the oldest non-distributed transaction, and causes the LogReader to fail with the errors noted above.


Additional query words: failure sp1 sp3 6.00 6.50
Keywords : kbbug6.00 kbbug6.50 kbfix6.00.sp3 kbfix6.50.sp1 kbusage SSrvRep SSrvStProc kbfixlist
Version : 6.0 6.5
Platform : WINDOWS
Issue type : kbbug
Resolution Type : kbfix


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 30, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.