Tag: sp_repldone

Troubleshooting ‘The process could not execute ‘sp_repldone/sp_replcounters’

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 »

Troubleshooting LogReader Error “repldone log scan occurs before the current start of replication”

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 »

The process could not execute ‘sp_repldone/sp_replcounters’

Anurag Sharma | Microsoft SQL Server Escalation Services Log Reader fails with below error message The process could not execute ‘sp_repldone/sp_replcounters’ on ‘SQLGUY’. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011) Get help: http://help/MSSQL_REPL20011 The log scan number (23:49:3) passed to log scan in database ‘PUBLISHER’ is not valid. This error may indicate data corruption or that the
Read More »