In Replication Monitor, expand your agents folder, and
then expand the merge agents folder. Locate your merge
agent, right click on it, select agent properties, select
run agent, click on edit and at the very end of the
command string add
-QueryTimeout 300
which means 300 seconds. Use this if you get the
enumerate or query metadata message.
Most of the time on our toplologies which involve ISDN and
lower bandwidths I find I have to change the LoginTimeout
setting to something like
-LoginTimeout 60 setting
I do this when I get the Could not connect to publisher or
subscriber message.
Then stop and start your agents.
Note that there is the slow link profile which also may
work for you - it doesn't work well for us, but it is
designed to address your apparent problem.
[quoted text, click to view] >-----Original Message-----
>Hi,
>
>How can I or where should I go to adjust the time-out
>range for a replication job and its agent on sql server
>2000?
>
>Many thanks.
>
>JJ
>.
thanks, Hilary, for the valuable input. I should have
pointed out to you earlier that we are not doing any merge
replication, we are only doing transactional replication.
But I assume your method should work the same.
Thanks!
JJ
[quoted text, click to view] >-----Original Message-----
>In Replication Monitor, expand your agents folder, and
>then expand the merge agents folder. Locate your merge
>agent, right click on it, select agent properties, select
>run agent, click on edit and at the very end of the
>command string add
>
>-QueryTimeout 300
>
>which means 300 seconds. Use this if you get the
>enumerate or query metadata message.
>
>Most of the time on our toplologies which involve ISDN
and
>lower bandwidths I find I have to change the LoginTimeout
>setting to something like
>
>-LoginTimeout 60 setting
>
>I do this when I get the Could not connect to publisher
or
>subscriber message.
>
>Then stop and start your agents.
>
>Note that there is the slow link profile which also may
>work for you - it doesn't work well for us, but it is
>designed to address your apparent problem.
>
>>-----Original Message-----
>>Hi,
>>
>>How can I or where should I go to adjust the time-out
>>range for a replication job and its agent on sql server
>>2000?
>>
>>Many thanks.
>>
>>JJ
>>.
>>
>.
correct:)
[quoted text, click to view] "JJ Wang" <jwang@leapwireless.com> wrote in message
news:22a701c373de$fe77bda0$a301280a@phx.gbl...
> thanks, Hilary, for the valuable input. I should have
> pointed out to you earlier that we are not doing any merge
> replication, we are only doing transactional replication.
> But I assume your method should work the same.
>
> Thanks!
>
> JJ
> >-----Original Message-----
> >In Replication Monitor, expand your agents folder, and
> >then expand the merge agents folder. Locate your merge
> >agent, right click on it, select agent properties, select
> >run agent, click on edit and at the very end of the
> >command string add
> >
> >-QueryTimeout 300
> >
> >which means 300 seconds. Use this if you get the
> >enumerate or query metadata message.
> >
> >Most of the time on our toplologies which involve ISDN
> and
> >lower bandwidths I find I have to change the LoginTimeout
> >setting to something like
> >
> >-LoginTimeout 60 setting
> >
> >I do this when I get the Could not connect to publisher
> or
> >subscriber message.
> >
> >Then stop and start your agents.
> >
> >Note that there is the slow link profile which also may
> >work for you - it doesn't work well for us, but it is
> >designed to address your apparent problem.
> >
> >>-----Original Message-----
> >>Hi,
> >>
> >>How can I or where should I go to adjust the time-out
> >>range for a replication job and its agent on sql server
> >>2000?
> >>
> >>Many thanks.
> >>
> >>JJ
> >>.
> >>
> >.
> >
Hi, Hilary,
time out 300 v.s. 600, which one waits longer? 'cause my
current setting is 600.
JJ
[quoted text, click to view] >-----Original Message-----
>correct:)
>"JJ Wang" <jwang@leapwireless.com> wrote in message
>news:22a701c373de$fe77bda0$a301280a@phx.gbl...
>> thanks, Hilary, for the valuable input. I should have
>> pointed out to you earlier that we are not doing any
merge
>> replication, we are only doing transactional
replication.
>> But I assume your method should work the same.
>>
>> Thanks!
>>
>> JJ
>> >-----Original Message-----
>> >In Replication Monitor, expand your agents folder, and
>> >then expand the merge agents folder. Locate your merge
>> >agent, right click on it, select agent properties,
select
>> >run agent, click on edit and at the very end of the
>> >command string add
>> >
>> >-QueryTimeout 300
>> >
>> >which means 300 seconds. Use this if you get the
>> >enumerate or query metadata message.
>> >
>> >Most of the time on our toplologies which involve ISDN
>> and
>> >lower bandwidths I find I have to change the
LoginTimeout
>> >setting to something like
>> >
>> >-LoginTimeout 60 setting
>> >
>> >I do this when I get the Could not connect to publisher
>> or
>> >subscriber message.
>> >
>> >Then stop and start your agents.
>> >
>> >Note that there is the slow link profile which also may
>> >work for you - it doesn't work well for us, but it is
>> >designed to address your apparent problem.
>> >
>> >>-----Original Message-----
>> >>Hi,
>> >>
>> >>How can I or where should I go to adjust the time-out
>> >>range for a replication job and its agent on sql
server
>> >>2000?
>> >>
>> >>Many thanks.
>> >>
>> >>JJ
>> >>.
>> >>
>> >.
>> >
>
>
>.
Don't see what you're looking for? Try a search.
