Merge seems to hang at conflict and conflict is not logged

We have a SQL2005 merge replication database with 8 subscribers. Three of the
subscribers have not successfully replicated. We would appreciate any
additional ideas for correcting this. So far we have some inconsistencies.
For example, the "View Synchronization Status" displays:
"Downloaded 100 change(s) in 'OurTable' (100 updates, 1 conflict)"
and the publisher's "Microsoft Replication Conflict Viewer" displays:
"There are no conflicts to view."
If you have any ideas why conflicts are causing the replication to fail
while the conflict viewer shows no conflicts, we would appreciate your input.
Thanx.
Were there any conflicts on the subscriber side?
You can run the conflict viewer there as well, or if that's not
convenient/possible there are sp_xxx procedures to help you view the
conflict tables on the client...

merge replication problem;urgent

We have a publisher and 2 subsribers. The
subscribers are spanning 2 transactions/sec. We have
implemented merge replication and it was scheduled
to occur every 5 min. When we ran it for the first time with a
transaction rate of 75k/hr it ran for 4 days.After sometime we got
problems so we reduced the transaction rate to 12k/hr then,
the replications is going on without any problem for
sometime(may be some hours), but after that it
failes with the message, "the process could not
deliver inserts at the publisher". When
I searched for this error in google, it asked me to
increase the queytimeout value in agent profile. So
I increased it from 300 to 600, but in vain. Now the merge agent is
failing as soon as it is started.We have a dedicated network for this
replication. If
anybody could help me in this, that would be great.
windows: windows 2003 server, sql server: sql server 2000 standard
edition.
Failing as soon as started, might be syntax error w/ QueryTimeout switch.
Confirm you added to end of Run Agent step:
-QueryTimeout 0
0 = unlimited
ChrisB
MCDBA OCP
www.MyDatabaseAdmin.com
"sqldbapree" wrote:

> We have a publisher and 2 subsribers. The
> subscribers are spanning 2 transactions/sec. We have
> implemented merge replication and it was scheduled
> to occur every 5 min. When we ran it for the first time with a
> transaction rate of 75k/hr it ran for 4 days.After sometime we got
> problems so we reduced the transaction rate to 12k/hr then,
> the replications is going on without any problem for
> sometime(may be some hours), but after that it
> failes with the message, "the process could not
> deliver inserts at the publisher". When
> I searched for this error in google, it asked me to
> increase the queytimeout value in agent profile. So
> I increased it from 300 to 600, but in vain. Now the merge agent is
> failing as soon as it is started.We have a dedicated network for this
> replication. If
> anybody could help me in this, that would be great.
> windows: windows 2003 server, sql server: sql server 2000 standard
> edition.
>
sql