Conflicts how can it be possible

Dear Friends
I am getting the conflict for the records with following
remark.
The row was updated at 'SERVER1.DATABASE1' but could not
be updated at 'SERVER2.DATABASE2'. Violation of PRIMARY
KEY constraint 'PK__TABLE04__5DF6A344'. Cannot insert
duplicate key in object 'TABLE04'.
This record is created in SERVER2 AND ALSO CHANGED IN
SERVER2. The replication was down and then it come up
with this error when the user have change on same record.
Can you please suggest what can be the reason.
Publisher have not change anything every change is done
by the supplier still it is in the conflict.
Your guidance will help me a lot.
Best regards
Sharad
Is it possible that you updated the primary key? This might cause this
problem.
You also might want to edit your update proc and comment out the section
where it updates the pk in the second portion of the update proc.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Sharad" <niitmalad@.yahoo.co.in> wrote in message
news:06f901c4ec1e$5ed33310$a501280a@.phx.gbl...
> Dear Friends
> I am getting the conflict for the records with following
> remark.
> The row was updated at 'SERVER1.DATABASE1' but could not
> be updated at 'SERVER2.DATABASE2'. Violation of PRIMARY
> KEY constraint 'PK__TABLE04__5DF6A344'. Cannot insert
> duplicate key in object 'TABLE04'.
> This record is created in SERVER2 AND ALSO CHANGED IN
> SERVER2. The replication was down and then it come up
> with this error when the user have change on same record.
> Can you please suggest what can be the reason.
> Publisher have not change anything every change is done
> by the supplier still it is in the conflict.
> Your guidance will help me a lot.
> Best regards
> Sharad