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.
Verify that the SQL Server Agent service is started on the Publisher SQL Server:
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):
By using SQL Server Enterprise Manager or SQL Server Management Studio, verify that the Replication Agent credentials are set properly. The following conditions must be met:
For information on how to view or modify the credentials that the Snapshot Agent and Merge Agents use to connect to the Publisher and Subscribers, see Modifying Replication Agent credentials earlier in this document.
© 2021 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy