Unanswered: Replication keeps failing after one failure
We are running Merge Replication on Sql Server 2K with multiples MSDE 2K subsciber.The Replication is getting done through a Visual Basic Application and it works fine as long as it does not fail.Once the replication fails on the Clients machine then we always need to blow the Local Database on the Client's machine and then start the Merge Replication process again.I wonder Why?Any help is really appriciated..
It's necessary adjust the retry count for the merge agent, in the event it fails (e.g. remote computer is turned off, network failure etc.). Expand Replication monitor, expand agents, click on merge agents. A list of merge agents, corresponding to each location is listed on the right. To change retry count for a merge agent, highlight the merge agent, right click and select agent properties. Click on tab "Steps", Highlight ID 2 (step 2 - run agent), click on edit. Step name should say "Run agent". Click on Advanced tab, and adjust the retry count and retry interval.
Thanks for your reply and I will increase the Number of Retry but my question is still unanswered and that's Why the Replication keeps failing after one failure?Is this turning on some flag somewhere in the Sql Server after a failure?
Replication is a configuration of Sql Server. Has nothing to do with Visual Basic.
What kind of Merge replication is setup? Merge continuosly, or scheduled merge?
If Merge continuously, then the retry count and schedule HAS to be changed. The defaults will cause the agent to fail if the connection is down for just 10 minutes. (10 retries, at 1 minute intervals).
Also, when you say replication fails, there are error messages that can be viewed via replication monitor. The agent may try 10 times, and on failure display 1 message. That doesn't mean there were no retries.
It's a Merge Replication which runs on Demand through Visual Basic Application.The process works fine 9/10 times but if its fails then it keeps failing and the error log says "The Process was Successfully Stopped".I also don't think that it involves any network issue as the subscriber is connected to the network all the time.
Also once the Synchronization fails then we need to set the Initial database at the subscriber(which involves defining the subscriber,creating the local DB,Copying Roles and creating a dynamic Merge Replication job) and then do the Regular Synchronization,which works fine thereafter.