"TCorp" <tcorpus@hotmail.com> wrote in message
news:eghBqpALGHA.2992@tk2msftngp13.phx.gbl...
> Thanks Gopal and Hilary. I will try both suggestions.
>
> I knew that WSM was an option, but I haven't investigated it. Is there a
> way to centrally manage all the WSMs? The fact that I can centrally
> manage the push subscriptions is the reason I was using them.
>
> Thanks again,
> Ted.
>
> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
> news:eMhiY48KGHA.1236@TK2MSFTNGP10.phx.gbl...
>> In a case like this you should be using pull subscriptions and use
>> Windows Synchronization Manager to manage the pull. With WSM you can
>> configure it to pull when it senses a network connection.
>>
>> --
>> 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 >>
>> "TCorp" <tcorpus@hotmail.com> wrote in message
>> news:eMRN8q3KGHA.2704@TK2MSFTNGP15.phx.gbl...
>>> The application error log on my SQL Server 2005 is full of error
>>> messages from my push subscriptions not being able to connect when they
>>> are off the network.
>>>
>>> I have a SQL Server 2005 publisher to several MSDE merge push
>>> subscribers. Many subscribers are laptops which go off the network for
>>> periods during the day or overnight. I am getting the following message
>>> litting my Server's application log:
>>>
>>> Replication-Replication Merge Subsystem: agent <AgentName> failed. The
>>> process could not connect to Subscriber '<MSDESubscriberServerName>'.
>>>
>>>
>>> I tried unchecking the "Write to Windows application event log" setting
>>> for the job, but it didn't seem to make any difference (would I need to
>>> reinitialize the subscription?).
>>>
>>> TIA,
>>> -Ted.
>>>
>>
>>
>
>
