Sign in
 
Home20122008 R2200820052000LibraryForums
SQL Server >
> 
> 
The replication agent has not logged a progress message in 10 minutes

Answered The replication agent has not logged a progress message in 10 minutes

  • Tuesday, December 04, 2012 10:02 PM
     
     
    Sign In to Vote
    0
    I previously had a replication issue where the number of rows in msmerge_genhistory (3 million+) was causing initialization from a snapshot to fail.  In order to fix this I had to increase my querytimeout from the default of 5 minutes to 30 minutes.  Now a client is trying to synchronize and initializing from the snapshot.  The querytimeout doesn't throw the error now but I still get an error that the agent has not logged a progress message in 10 minutes.  I read somewhere that changing the heartbeat_interval on the distributor to a higher value will increase the time before an error is thrown.  Will this have any adverse affects on others?  There are many other databases on our server using replication that use this distributor.  Is there some way to check the current hearbeat_interval?  The error message is indicating 10 minutes so if I could confirm the current heartbeat_interval is set to 10 that would be nice. 
     

All Replies