Merge replication error on the subscriber - call sys.sp_MSmakegeneration timing out

We are running on SQL Server 2005 SP2. Merge replication is on for one publisher and one subscriber.

Merge replication is throwing following error

"The process is waiting for a response from the query '{call sys.sp_MSmakegeneration (?)}"

It is hung on there for atleast couple hour or so. I decrease uploadbatches and downloadbatches settings as recommended but no positive results.

Let us know if any insight on the above issue.

Thanks

Is it actually hung on as in waiting for a response or is this what you are seeing in Replication Monitor. Keep in mind that if you are seeing this in Replication Monitor, the title of that dialog is the LAST error message that was received. It could very well have finished many synch cycles successfully and everything is moving through, however, the last time it had an error raised, it was this particular error. If it is in fact still waiting, then you need to check the publisher and subscriber and make sure that you don't have any blocking.|||I have ran sp_lock as don't see any blocking through sp_who , out put of the sp_lock shows that it is holding key locks on tables such as MSmerge_genhistory and MSmerge_contents.|||

Now I am running the sys stored procedure

exec sp_MSmakegeneration

from SQL Management Studio to see if it gives out any different output.

|||sp_MSmakegeneration will not return any information unless it errors out. If you want to see exactly what's going on, your best bet is to run profiler to trace it.|||

That would mean that it isn't hung and that data is moving through the system. If you look at the VERY bottom of the Replication Monitor window, in the status bar at the bottom, do you see a message that says something like "Waiting 60 seconds to poll for changes" or something else indicating that it is either uploading, download, connecting, or checking for stuff?

The part of the Replication Monitor that you are looking at just shows the last error message encountered. That error message could have occured 10 days ago and everything since then is running correctly without any errors.

|||What is the status of this thread? Were you able to resolve the issue? We are currently experiencing the same problem and could use some help, thanks!