If there are any replication failures in Active Roles, the Active Roles console provides a visual indication of this issue by placing a red triangle on the Server Configuration and Configuration Databases containers in the console tree. To get more information on a replication failure, you can use SQL Server Management Studio (see Monitoring replication earlier in this document).
The following sections discuss specific actions to take if you encounter a replication problem in Active Roles.
Replication stops synchronizing changes to configuration data, that is, changes made on a replication partner are not propagated to other replication partners. Replication Monitor in SQL Server Enterprise Manager or SQL Server Management Studio does not indicate any error.
If the Start command is unavailable, the SQL Server Agent service is already started.
Ensure that the Merge Agents are started on the Publisher SQL Server:
If the Start Synchronizing command is unavailable, the agent is already started.
Verify that the replication agent schedule is correct. The Merge Agents must be configured to run continuously at the Publisher. The Snapshot Agent must be configured to start daily at 12:00 a.m. at the Publisher. For details, see Replication Agent schedule earlier in this document.
Replication fails with one of the following errors on the Snapshot Agent or Merge Agent (see Monitoring replication earlier in this document):