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

+关注继续查看

1，查看status= “Performance critical” Subscription的Detail，在Distributor to subscriber history tab中查看Action messages。

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.

Message Details

The replication agent has not logged a progress message in %ld 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.

Explanation

The Replication agents checkup job runs at a specified interval (10 minutes by default) to check on the status of each replication agent. If an agent has not logged any progress messages since the last time the agent checkup job ran, error MSSQL_ENG020554 can be raised. The agent is expected at least to log history messages even if no other replication activity is occurring. Although the replication agent is not responding as expected, it has not necessarily stopped or failed (if an agent has failed, error MSSQL_ENG020536 should be raised).

The following issues can cause error MSSQL_ENG020554 to be raised:

• The agent is busy.

If the agent is too busy to respond when polled by the agent checkup job, the agent checkup job cannot report whether the replication agent is functioning properly. There are a number of reasons why the replication agent could be busy: there might be a lot of data being replicated, or there might be application design or configuration issues that result in processes that run for a long time.

• The agent cannot log in to one of the computers in the topology.

All agents have a parameter -LoginTimeOut (set to 15 seconds by default), which governs how long an agent attempts to log in to a replication node, such as a Merge Agent logging in to the Publisher. If the -LoginTimeOut value is set higher than the interval at which the replication agent checkup job runs, a login problem could be the root cause of the error: error MSSQL_ENG020554 is raised before the agent is able to raise a more specific error.

This error message gets generated because of the Distribution heartbeat interval property. This property governs how long an agent can run without logging a progress message. If your replication agents are not reporting an error message and you are seeing the above message, then you could change your heartbeat interval to a higher value. One of the option could be that you changed the history logging option for your replication agent so that it doesn’t log any message.

exec sp_changedistributor_property
@property = 'heartbeat_interval',
@value = <value in minutes>;

USE master
GO

exec sp_changedistributor_property
@property = 'heartbeat_interval',
@value = 30;

set 30 minutes and check. if you still face the issue change it to 60 minutes

https://technet.microsoft.com/en-us/library/ms152484(v=sql.110).aspx

http://troubleshootingsql.com/2010/05/28/replication-agent-has-not-logged-a-message-in-10-minutes/

Error connecting to master ‘slave@192.168.200.128:3307‘ - retry-time: 30 retries: 1
Error connecting to master ‘slave@192.168.200.128:3307‘ - retry-time: 30 retries: 1
84 0

2052 0
561 0
‘Client‘ is not allowed to run in parallel.Would you like to stop the running one?
‘Client‘ is not allowed to run in parallel.Would you like to stop the running one?
280 0
+关注

AliHB Real-Time Cold data Backup

AliHB Real Time Cold data Backup

Bring Consensus to Date Replication