I have a new merge replication application I am working on. I have the
publication/distributor setup on the server (windows 2003/SQL Server 2000
sp3a), and My client application is using the COM SQLMerge objects and
SQLError Object.

I have the appliation setup so that on the first attempt to synchronize, we
call the AddSubscription method to create the database locally and then it
applies the scripts, etc from the snapshot.

What I am seeing happen is that this initial load begins and all looks well,
however after all the scripts are applied and the sync process begins
processing articles, It gets to a certain point and then just stops. From
all indications the merge sync is still running on the client. But
eventually the subscription gets marked as failed on the server with a no
response in 3 minutes message.

I have modified the msdb agent profiles table to increase all query time out
parameters from 300 to 3600. But still get the same results.

Can someone please tell me what to look at next to resolve this?

Thanks.

Guy,
I'd enable logging (http://support.microsoft.com/?id=312292) and see if this
gives some useful info.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)