merge replication problem ; very urgent

We have a publisher and 2 subsribers. The subscribers are spanning 2 transactions/sec. We have inplemented merge replication and it was scheduled to occur every 5 min. When we start the replication, the replications is going on without any problem for sometime(may be some hours), but after that it failes with the message, "the process could not deliver inserts at the publisher". We have SAN. When I searched for this error in google, it asked me to increase the queytimeout value in agent profile. So I increased it from 300 to 600, but in vain. If anybosy could help me in this, that would be great.

Thanks,

Preethi.

Hi Preethi,

Is this SQL 2000 or SQL 2005?
Is there a large amount of data yet to be propagated across when this failure occurs?
Are any other processes running on the Publisher machine that are taking up the CPU or memory and hence the merge agent timing out?
Are there any constraints on the publisher that are making the inserts to fail?
Can you post the complete error message from the Merge agent.
Also a higher verbosity log will help. Run the merge agent with the parameter -OutputVerboseLevel 2 or 3.|||sql 2000.
we have 4 merge agents running thats it.
i took an error log with the high verbosity level.
In job history, the error is "remote procedure call failed and it didn't execute".
In the log that I took, the above error message i gave occured. Actually when we started replication fresh, it ran for 4 days for transaction rate 75K/hr. Now even with 12K/hr it is failing in 3 min.

Regarding error i will post it.|||Are you using any agent profile to run the merges?
When you changed the Timeout value, where did you change it?
Try increasing the timeout and logintimeout values. Set -QueryTImeout 1000 -LoginTimeout 1000 and see if it helps.

Another thing you could try is setting the -UploadGenerationsPerBatch and -DownloadGenerationsPerBatch to a low value say 25 and run the merge agent.