Merge deadlock

Hi, more or less once a day I receive this message from the merge
replication, because is continuous suddenly stops. I try to put an extra step
on the job to restart it but is ignored. Any clues why my step is ignored or
why this problem is happening?
cheers , Error:
The process could not enumerate changes at the 'Subscriber'.
(Source: Merge Replication Provider (Agent); Error number: -2147200999)
------
Transaction (Process ID 87) was deadlocked on lock resources with another
process and has been chosen as the deadlock victim. Rerun the transaction.
(Source: SUMSTR (Data source); Error number: 1205)
------
The process was successfully stopped.
(Source: Merge Replication Provider (Agent); Error number: -2147200999)
------
If you have large numbers of subscribers you might want to limit concurrent
processing or perhaps schedule your merge agents as opposed to running them
simultaneously or continuously.
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:BA09357D-8EE6-42A4-97C3-72384153AD02@.microsoft.com...
> Hi, more or less once a day I receive this message from the merge
> replication, because is continuous suddenly stops. I try to put an extra
step
> on the job to restart it but is ignored. Any clues why my step is ignored
or
> why this problem is happening?
> cheers , Error:
> The process could not enumerate changes at the 'Subscriber'.
> (Source: Merge Replication Provider (Agent); Error number: -2147200999)
> ----
--
> Transaction (Process ID 87) was deadlocked on lock resources with another
> process and has been chosen as the deadlock victim. Rerun the transaction.
> (Source: SUMSTR (Data source); Error number: 1205)
> ----
--
> The process was successfully stopped.
> (Source: Merge Replication Provider (Agent); Error number: -2147200999)
> ----