"Guy Thornton" <gt@scd.com> wrote in message
news:C64856F0-4CF7-43DC-9A1E-B6D9D75E3167@microsoft.com...
> Hilary,
>
> Thanks for this information, as I am having the same problem. I was able
> to
> change my query timeouts by updating the msdb database. A question I have
> though is what causes the queries to begin running longer? When I first
> began this publication, I had no problems completing the replication
> query.
> But over time, I have now encountered this problem.
>
> I am assuming that it is due to a build up of changes that have occurred
> overtime. And if that is the case, is there a way to reduce the change
> history that the query must process?
>
> "Hilary Cotter" wrote:
>
>> That's for the conflict viewer, when it logs on to the Publisher.
>>
>> If you are getting prompted for the username and password it is because
>> you
>> are using SQL authentication, switch to NT if possible. You should be
>> able
>> to change querytimeout on the default profile. By default its 300s. Try
>> to
>> use a new profile with the value you want, or modify it in the msdb
>> database.
>>
>> --
>> Hilary Cotter
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602.html
>>
>> Looking for a FAQ on Indexing Services/SQL FTS
>> http://www.indexserverfaq.com
>>
>> "David Chase" <dlchase@lifetimeinc.com> wrote in message
>> news:%23hRHTkeHGHA.3144@TK2MSFTNGP10.phx.gbl...
>> > So what is the query timeout in the View Conflicts button for? This
>> > shows
>> > 90 seconds.
>> >
>> > Also, I cannot get to agent properties because the subscribers are
>> > anonymous laptops. I get prompted for username and password but still
>> > does not connect.
>> >
>> > David
>> >
>> > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
>> > news:OPeON6WHGHA.3728@tk2msftngp13.phx.gbl...
>> >> Connect to your publisher in EM, expand the replication Monitor
>> >> folder,
>> >> expand the distribution or merge agent folder, right click on your
>> >> problem agent, and select agent properties, click the steps tab, and
>> >> double click on run agent, click in the command text box, and press
>> >> end,
>> >> then press space and type -QueryTimeOut 300 (or more).
>> >>
>> >> --
>> >> Hilary Cotter
>> >> Looking for a SQL Server replication book?
>> >> http://www.nwsu.com/0974973602.html
>> >>
>> >> Looking for a FAQ on Indexing Services/SQL FTS
>> >> http://www.indexserverfaq.com
>> >>
>> >> "David Chase" <dlchase@lifetimeinc.com> wrote in message
>> >> news:OWe$wyUHGHA.1676@TK2MSFTNGP09.phx.gbl...
>> >>> How do I change the value in QueryTimeout? I have some wireless
>> >>> laptops
>> >>> that are timing out sometimes when they synch. Thanks.
>> >>>
>> >>> David
>> >>>
>> >>
>> >>
>> >
>> >
>>
>>
>>