Problem with remote replication

I have a number of dialup users who are trying to replicate against a master database.The first few times worked fine.but now each user is getting the following message

"The process could not change generation history at the publisher"

Any help or pointers gratefully received

many thanks

David J.

1) How many days has it run smoothly and end up with that error?

2) What is the number of transaction run per day?

3) Is this transactional replication?

|||

The first replication was done over the wirless network, after that the replication was done via a dialup connection over the Internet.Most users got 2/3 replications befor encountering the error message

"The process could not change generation history as the Publisher"

Not sure what you mean - Each user might add 400/500 new transactions each day

We are using Merge Replication

|||

It could be a timeout issue or a network related issue (due to flakiness)

Have you encountered the problem repeatedly now?

|||What will be the solution for timeout or network issues?|||

If it is a Timeout issue, it can be dealt with increasing the timeout value.

If it is a network issue, you will have to ensure that your network is connectable and the servers can talk to each other.

You should monitor your servers and see when you start encountering these problems. Analyze if there are any other external factors that influence it and then take some actions based on that fact.

|||Thanks, do you mean increasing timeout in SQL Enterprise Managers properties?|||Kind of. You would increase the timeout values (QueryTimeout/LoginTimeout) values for the agent jobs. But again, this suggestion holds if it is a timeout related problem.