Chris Skorlinski, SQL Server Escalation Services I worked on customer’s Transactional Replication issue today where LogReader was failing, restarting, then failing again.  We used link below to enable logging to get a clearer picture of failure.  http://blogs.msdn.com/b/repltalk/archive/2010/03/04/kb-article-312292-how-to-enable-replication-agents-for-logging-to-output-files-in-sql-server.aspx 16:02:45 OLE DB DISTOLE: sp_MSget_last_transaction 16:02:45 Publisher: {call sp_repldone ( 0x000a35e7000315e7005b, 0x000a35e7000315e7005b, 0, 0)} 16:32:45 Status: 2, code:
Read More »

Below are cause and recommendation for the SQL Replication LogReader error “The specified LSN (…) for repldone log scan occurs before the current start of replication in the log (…).’. When the LogReader starts, it verifies the Last Distributed transaction (last transaction in msrepl_transactions) still exists in the transaction log.  This confirms the Published database
Read More »