I'm supporting 4 SQL Servers with a fairly complex merge
replication schema. One replication, "WebMerge",
published on the "LongHorn" server, publishes 10 tables
and has two push subscriptions, 1 to the
server "SouthernStar" and 1 to the server "McCoy". One
table, "SubDivisions", in the subsription
to "SouthernStar", creates "Resolved Conflict" messages
when certain transactions take place. If I open
the "SubDivision" table on both servers in Enterprise
Manager at the same time and write a record to each table,
the record from the publisher, "LongHorn", will get
replicated to the subscriber, "SouthernStar", but the
replication will not go the other way, so the record from
the "SouthernStar" does not get replicated to
the "LongHorn". Updates to preexisting records between
the 2 servers does not work in either direction. The
subscription between "LongHorn" to "McCoy" does not have
these issues and none of the other 9 tables included
in "WebMerge" have this issue.

It seems like the replication tables are screwed up. I
have 5 merge publications encompassing 60 tables and
certainly do not want to completely tear down replication
to resolve this issue.

Any thoughts?

Did you use the default conflict resolution mechanism? If so, I'd have a
look at them using the conflict viewer and see if this gives you any hints
about what is going on.

This statement " If I open the "SubDivision" table on both servers in
Enterprise Manager at the same time and write a record to each table, the
record from the publisher, "LongHorn", will get replicated to the
subscriber, "SouthernStar", but the replication will not go the other way,
so the record from the "SouthernStar" does not get replicated to the
"LongHorn". "

Sounds like a PK violation. If you insert a record in your publisher, and
simultaneously insert a record in the subscriber, and you have an identity
elements on both PK's, you are going to in effect be inserting records with
the same values for the pk's on the subscriber and publisher, and the
subscriber's record is being rolled back.


"Steven" <steven (AT) woodwyn (DOT) com> wrote