The Agent is Suspect. No Response within the last 10 Minutes

Hi
I am running Merge Replication, using Named Pull subscriptions over FTP
between our clients and a central server. This process works fine as long as
small amounts of data change between all databases (Les than 1000 changes
between merges).

The problem is that I have 38000 data changes that I have to implement on
the central server. The moment I do this, all my replications fail with the
error "The Agent is suspect. No response within the last 10 minutes". Our
clients use a range of access methods like Dialup over Telephone, ISDN and
ADSL. All of these machines fail to replicate after about 15 minutes of
activity. (The subscription side does not give an error, in fact it still
says "Retrieving Subscription Information" when the server side already
times out.)

I have done the following to try and remedy the situation, but to no avail:
1. Adjusted the Agent profile as follows: - BcpBatchsize = 10 000 (was 100
000)
-
KeepaliveMessageInterval = 30 (was 300
- LoginTimeout
= 300 (was 15)
-
MaxDownloadChanges=2000 (was 0)
-
MaxUploadChanges = 2000 (was 0)
- QueryTimeout
= 600 (was 300)


I think what is happening is that the subscriber is stil interpreting data
received from the Publisher while the timeout occurs (Some of the tables
contain 150 000 and more records), but I have no idea where to adjust the 10
minute timeout to be more. What worries me more is the fact that the
subscriber never gets informed of the timeout and as such, the application
doing the replication effectively hangs, waiting for a response from the
publisher that never comes.

Once again, any suggestions would be welcome.

Regards

You can set ths time in Replication monitor. Open replicationmonitor->
Refresh rate and setting. In genneral tab, increase inactivity threshold
value. This will solve your problem.
Let me know whether this works or not.

Sri
"Paul Kleynhans" wrote in message

 > Hi
 > I am running Merge Replication, using Named Pull subscriptions over FTP
 > between our clients and a central server. This process works fine as long
as
 > small amounts of data change between all databases (Les than 1000 changes
 > between merges).
 >
 > The problem is that I have 38000 data changes that I have to implement on
 > the central server. The moment I do this, all my replications fail with
the
 > error "The Agent is suspect. No response within the last 10 minutes". Our
 > clients use a range of access methods like Dialup over Telephone, ISDN and
 > ADSL. All of these machines fail to replicate after about 15 minutes of
 > activity. (The subscription side does not give an error, in fact it still
 > says "Retrieving Subscription Information" when the server side already
 > times out.)
 >
 > I have done the following to try and remedy the situation, but to no
avail:
 > 1. Adjusted the Agent profile as follows: - BcpBatchsize = 10 000 (was 100
 > 000)
 > -
 > KeepaliveMessageInterval = 30 (was 300
 > -
LoginTimeout
 > = 300 (was 15)
 > -
 > MaxDownloadChanges=2000 (was 0)
 > -
 > MaxUploadChanges = 2000 (was 0)
 > -
QueryTimeout
 > = 600 (was 300)
 >
 >
 > I think what is happening is that the subscriber is stil interpreting data
 > received from the Publisher while the timeout occurs (Some of the tables
 > contain 150 000 and more records), but I have no idea where to adjust the
10
 > minute timeout to be more. What worries me more is the fact that the
 > subscriber never gets informed of the timeout and as such, the application
 > doing the replication effectively hangs, waiting for a response from the
 > publisher that never comes.
 >
 > Once again, any suggestions would be welcome.
 >
 > Regards
 >
 >
 >