"Salvador" <Salvador@discussions.microsoft.com> wrote in message
news:723F7F3D-6BE0-4205-B79F-01CA227E7EF7@microsoft.com...
> Hi All,
>
> I have selected merge replication because both servers are constantly
> updating information. We have continuous merge replication (push) and
> everything works pretty good.
>
> The problem is in some occassions the job stops saying that it can not
> enumerate the changes on the subscriber, if I restart it works fine. This
is
> causing more than a headache because we always have to be watching if
> replication is working. I try to change the job to restart when it fails
but
> it doesn't work.
>
> I have one publisher with the distributor on the same machine pushing the
> continuous merge to one subscriber.
>
> Can this happen because the subscriber is busy and the job can connect?
Have
> anyone seen this happening?
>
> Thanks a lot

"Hilary Cotter" wrote:

> Yes, it is typically a transitory error. Many dba's run their merge agents
> in infinite loops by having step 3 looping back to step 1.
>
> --
> 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
>
> "Salvador" <Salvador@discussions.microsoft.com> wrote in message
> news:723F7F3D-6BE0-4205-B79F-01CA227E7EF7@microsoft.com...
> > Hi All,
> >
> > I have selected merge replication because both servers are constantly
> > updating information. We have continuous merge replication (push) and
> > everything works pretty good.
> >
> > The problem is in some occassions the job stops saying that it can not
> > enumerate the changes on the subscriber, if I restart it works fine. This
> is
> > causing more than a headache because we always have to be watching if
> > replication is working. I try to change the job to restart when it fails
> but
> > it doesn't work.
> >
> > I have one publisher with the distributor on the same machine pushing the
> > continuous merge to one subscriber.
> >
> > Can this happen because the subscriber is busy and the job can connect?
> Have
> > anyone seen this happening?
> >
> > Thanks a lot
>
>