Merge replication issues

We are getting a conflict error message "cannot synchronize, row was updated
outside of replication".
We cannot figure out what is causing this.
Can having different foreign key constraints at a publisher and subscriber
level cause problems with merge replication?
Sorry for the lack of information, but hopefully someone can help!
I have not seen that error message, but based upon my own limited
experiences, I can assure you that different constraints could certainly
create issues.
"llihp" <phill_dutton@.hotmail.com> wrote in message
news:428cb301_1@.x-privat.org...
> We are getting a conflict error message "cannot synchronize, row was
> updated
> outside of replication".
> We cannot figure out what is causing this.
> Can having different foreign key constraints at a publisher and subscriber
> level cause problems with merge replication?
> Sorry for the lack of information, but hopefully someone can help!
>
|||perhaps the row was updated by a process which did not trigger the triggers,
i.e. bcp, dts.
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
"llihp" <phill_dutton@.hotmail.com> wrote in message
news:428cb301_1@.x-privat.org...
> We are getting a conflict error message "cannot synchronize, row was
updated
> outside of replication".
> We cannot figure out what is causing this.
> Can having different foreign key constraints at a publisher and subscriber
> level cause problems with merge replication?
> Sorry for the lack of information, but hopefully someone can help!
>
|||"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eYHGHAPXFHA.2348@.TK2MSFTNGP14.phx.gbl...
> perhaps the row was updated by a process which did not trigger the
triggers,
> i.e. bcp, dts.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
I'm not sure what bcp is(?), but we aren't using any DTS packages within the
application.
Basically we are running a VB application at the sites, and this is
manipulating all the data within the database which is then susposed to be
sent back to the central server. We are having no issues with inserted rows
being replicated, it is only updates which are proving problematic.
|||Hi,
I am also getting the same error. I have multiple publishers with a central
subscriber ( using merge property -exchangetype 2). Please let me know if
there is any answere to it.
One stange thing that I have noticed is following:
I have Publications on Same Articles at 4 sites . Some articles have 4
insert, 4 update and 4 delete triggers but some articles get only 1 trigger
for update, 1 for delete and 1 for insert. Why is this so?
"llihp" wrote:

> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:eYHGHAPXFHA.2348@.TK2MSFTNGP14.phx.gbl...
> triggers,
> I'm not sure what bcp is(?), but we aren't using any DTS packages within the
> application.
> Basically we are running a VB application at the sites, and this is
> manipulating all the data within the database which is then susposed to be
> sent back to the central server. We are having no issues with inserted rows
> being replicated, it is only updates which are proving problematic.
>
>
|||Are all the triggers replication related? There should only be one trigger.
You might need to regenerate and resend your snapshot.
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
"Vikas Kohli" <VikasKohli@.discussions.microsoft.com> wrote in message
news:C682F2C2-AFAD-42FC-90C1-F81B1BE12928@.microsoft.com...
> Hi,
> I am also getting the same error. I have multiple publishers with a
central
> subscriber ( using merge property -exchangetype 2). Please let me know if
> there is any answere to it.
> One stange thing that I have noticed is following:
> I have Publications on Same Articles at 4 sites . Some articles have 4
> insert, 4 update and 4 delete triggers but some articles get only 1
trigger[vbcol=seagreen]
> for update, 1 for delete and 1 for insert. Why is this so?
> "llihp" wrote:
the[vbcol=seagreen]
be[vbcol=seagreen]
rows[vbcol=seagreen]