| Event Id | 20554 |
| Source | MSSQLServer |
| Description | The agent is suspect. No response within last %ld minutes. |
| Event Information | CAUSE: This behavior occurs because the replication agent is too busy to respond when SQL Server Enterprise Manager polls the replication agent; therefore, SQL Server Enterprise Manager does not know the status of the replication agent and it cannot report whether the replication agent is functioning or not. If the replication agent fails, you receive the following error message: Message 20536 Severity 10 "Replication: Agent failure." There are many reasons why the replication agent is busy: There may be a lot of data that is being replicated, or there may be configuration or replication design issues that cause processes to run for a long time. RESOLUTION: To reduce the frequency of the message, increase the inactivity threshold. Changing this value does not fix anything. Instead, it changes how frequently the replication agent is polled for its current status. To change the value of the inactivity threshold: 1. In SQL Server Enterprise Manager, under Replication Monitor, right-click the replication agent folder, and then click "Refresh Rate and Settings." 2. Set the value to the number of minutes for the Replication Monitor to wait between the polling of the replication agent. Unless you receive additional error messages that indicate that there is a problem with the replication agent, the "agent is suspect" message is only an informational message. When you receive this message, do not stop the replication agent if there are no additional related errors. If you stop the replication agent, it rolls back the process in which it is engaged, and then you must restart the process; instead, wait for the process to complete. |
| Reference Links | Microsoft product: SQL Server Version: 2000.80.760.0 Event Source: MSSQLServer Event ID: 20554 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.