sql server replication:
By any chance did you use DTS or some non logged operation
to populate one or more of the tables involved?
[quoted text, click to view] >-----Original Message-----
>Hi!
>
>I hope anyone can help me with this very important
problem!
>
>Since configurig one subscriber in our merge replication
>scenario to a subscribing publisher we get a lot of merge
>conflicts type 10 reason code 2. Because we have the
german
>version i translate the reason text as meaningful as
possible:
>
>The row was updated at 'publisher.database' but could not
be updated
>at subscriber.database'. Unable to synchronize the row
because the
>row was updated by a process not within the replication
>
>We use SQL Server 2000 SP3 with Merge Replication and
>pull-subscriptions.
>
>Has anyone any hints what could be the reason for that?
Any
>help would be greatly appreciated!!!
>
>Best Regards, Gert
>.
Hi!
I hope anyone can help me with this very important problem!
Since configurig one subscriber in our merge replication
scenario to a subscribing publisher we get a lot of merge
conflicts type 10 reason code 2. Because we have the german
version i translate the reason text as meaningful as possible:
The row was updated at 'publisher.database' but could not be updated
at subscriber.database'. Unable to synchronize the row because the
row was updated by a process not within the replication
We use SQL Server 2000 SP3 with Merge Replication and
pull-subscriptions.
Has anyone any hints what could be the reason for that? Any
help would be greatly appreciated!!!