SQLTeam.com | Weblogs | Forums

Peer to peer replication issues


Guys, I had a peer to peer replication between two sql 2012 servers working fine until one of the servers had a unusual transaction log grown. It almost filled a 1TB hard drive in a few hours. Let's call the erratic server as B, while the another peer is A.

Replication from A to B works fine, but from B to A I get all kinds of issues, in replication monitor in the Publisher to Distributor History tab I got the following:

The replication agent has not logged a progress message in 10
minutes. This might indicate an unresponsive agent or high system
activity. Verify that records are being replicated to the destination
and that connections to the Subscriber, Publisher, and Distributor are
still active.

and then a few minutes later:

The process could not execute 'sp_MSadd_replcmds' on server A.

In the Distributor to Subscriber history tab, I got:

Query timeout

I don't see any issue with the server, no hardware failure, no performance problem.

Any idea? I'm kind new for this replication world.


Which server has the unusual transaction log growth? Which recovery model are you using, Simple, Full? If full, are you using the same account to run your transaction log backups backup jobs and your replication agents? Did the permissions on the account(s) change recently?


The unusual growth happened in server B.

We are using full recovery model, and nothing changed about the permissions or accounts being used. I already double checked it. Thanks for the help.


Is the transaction log backup job still running on server B?