Category: Troubleshooting

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

Share this PostChris 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:
Read More »

ReplTip – Setting LogScanThreshold can result in LogReader failure

Share this PostContent provided by Sateesh Yele, Microsoft SQL Escalation Services BOL/MSDN documents –Logscanthreshold as “internal use only”. https://technet.microsoft.com/en-us/library/ms146878(v=sql.110).aspx -LogScanThreshold scan_threshold Internal use only. Other blog postings imply how to adjust this setting for better Logreader agent performance.  If you add this parameter to the Logreader SQL Agent command line and start the agent, Logreader
Read More »