Share this PostReplTalk ReplTip – Replication Agent fails with “unable to start correctly” Taiyeb Zakir Microsoft SQL Server Escalation Services When you have a large number of SQL Server Agent or Replication Agent Jobs running, some of the Jobs may not even start. You might see an error like this in the Event log: “The
Read More »
Share this PostHow to fix SQL 2008 R2 Replication objects not being created on Subscriber Chris Skorlinski Microsoft SQL Server Escalation Services Just a heads up if you are still running any version of SQL Server prior to SQL Server 2012 SP1 for Transactional Replication and the following hold true: 1) Use ‘initialize with backup’
Read More »
Share this PostReplTip — Only one Log Reader can connect message when dropping a Publication by Taiyeb Zakir Sometimes when you try to drop a Transactional Publication using the GUI, you get the following error: Only one Log Reader Agent or log–related procedure (sp_repldone, sp_replcmds, and sp_replshowcmds) can connect to a database at a time.
Read More »
Share this PostWhile troubleshooting a customers environment I encountered the following 9003 Exception error message captured in SQL Server Profiler. “The log scan number (42:358:1) passed to log scan in database ‘<db name>’ is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf).
Read More »
Share this PostHolger Linke Microsoft SQL Server Escalation Services Abstract: This article describes an issue with SQL Server Transactional Replication that was detected recently. If you have configured the Log Reader agent to use the MaxCmdsInTran parameter, and also have configured the Distribution database to use the “sync with backup” option, you may experience a
Read More »