"Kaliven" <Graduate@163.com> wrote in message
news:%233vLb$oSHHA.920@TK2MSFTNGP05.phx.gbl...
>
> I have some subscribers in cluster.
>
> when delete a record in a subscriber side, Publisher accepted the
> operation.However if try to insert
> a record with the same rowguid in the same table named "Image",Publisher
> rejected the operation.
> After tracing that operations of the table Image,the record was inserted
> into the table. and then
> the record was deleted.
>
> checking the publisher....
> I found there is a record in the table conflict_mergeRepPub_Image.It is my
> insert record.
> Other fields list as below:
> Conflict type 3
> Reason Code 3
> Reason Text The same row was updated at 'CR950A24G.DDS' and
> deleted at 'CR165.DDS'.
> The resolver chose the deletion as the winner.
>
> 'CR950A24G.DDS'is the subscribe and 'CR165.DDS' is publisher.
>
> Our publisher use default resolver.I had tried to change the resolver to
> "subscriber always win",
> But it still happened. And I had doubted the FK on the table. But after I
> delete the FK, issue is
> still on.
>
> I am comer.I wish I had described the complex issue clearly.
>

"Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
news:OFgs$ZqSHHA.1036@TK2MSFTNGP03.phx.gbl...
> This is a primary key conflict. You are trying to enter two rows (one on
> the publisher and one on the subscriber) with the same rowguid value. It
> will always be kicked back. You need to use a different value on either
> side if you wish it to remain in.
>
> --
> 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
>
>
>
> "Kaliven" <Graduate@163.com> wrote in message
> news:%233vLb$oSHHA.920@TK2MSFTNGP05.phx.gbl...
>>
>> I have some subscribers in cluster.
>>
>> when delete a record in a subscriber side, Publisher accepted the
>> operation.However if try to insert
>> a record with the same rowguid in the same table named "Image",Publisher
>> rejected the operation.
>> After tracing that operations of the table Image,the record was inserted
>> into the table. and then
>> the record was deleted.
>>
>> checking the publisher....
>> I found there is a record in the table conflict_mergeRepPub_Image.It is
>> my insert record.
>> Other fields list as below:
>> Conflict type 3
>> Reason Code 3
>> Reason Text The same row was updated at 'CR950A24G.DDS' and
>> deleted at 'CR165.DDS'.
>> The resolver chose the deletion as the winner.
>>
>> 'CR950A24G.DDS'is the subscribe and 'CR165.DDS' is publisher.
>>
>> Our publisher use default resolver.I had tried to change the resolver to
>> "subscriber always win",
>> But it still happened. And I had doubted the FK on the table. But after I
>> delete the FK, issue is
>> still on.
>>
>> I am comer.I wish I had described the complex issue clearly.
>>
>
>

"Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
news:OFgs$ZqSHHA.1036@TK2MSFTNGP03.phx.gbl...
> This is a primary key conflict. You are trying to enter two rows (one on
> the publisher and one on the subscriber) with the same rowguid value. It
> will always be kicked back. You need to use a different value on either
> side if you wish it to remain in.
>
> --
> 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
>
>
>
> "Kaliven" <Graduate@163.com> wrote in message
> news:%233vLb$oSHHA.920@TK2MSFTNGP05.phx.gbl...
>>
>> I have some subscribers in cluster.
>>
>> when delete a record in a subscriber side, Publisher accepted the
>> operation.However if try to insert
>> a record with the same rowguid in the same table named "Image",Publisher
>> rejected the operation.
>> After tracing that operations of the table Image,the record was inserted
>> into the table. and then
>> the record was deleted.
>>
>> checking the publisher....
>> I found there is a record in the table conflict_mergeRepPub_Image.It is
>> my insert record.
>> Other fields list as below:
>> Conflict type 3
>> Reason Code 3
>> Reason Text The same row was updated at 'CR950A24G.DDS' and
>> deleted at 'CR165.DDS'.
>> The resolver chose the deletion as the winner.
>>
>> 'CR950A24G.DDS'is the subscribe and 'CR165.DDS' is publisher.
>>
>> Our publisher use default resolver.I had tried to change the resolver to
>> "subscriber always win",
>> But it still happened. And I had doubted the FK on the table. But after I
>> delete the FK, issue is
>> still on.
>>
>> I am comer.I wish I had described the complex issue clearly.
>>
>
>