Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
update-update conflict on same node
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  4 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Ron  
View profile  
 More options Nov 18 2009, 12:54 pm
Newsgroups: microsoft.public.sqlserver.replication
From: Ron <R...@discussions.microsoft.com>
Date: Wed, 18 Nov 2009 09:54:01 -0800
Local: Wed, Nov 18 2009 12:54 pm
Subject: update-update conflict on same node
Dear all

I have spent quite a day or so dealing with an issue that I can make little
sense of, I hope that someone has had a similar experience and can share some
knowledge?

I have peer-peer replication with 2 nodes. Updates are done on node 1 only.

I have a conflict that appears when I update a value in a column for a
particular record as follows.

"An update-update conflict between peer 1 (incoming)
and peer 1 (on disk) was detected and resolved. The incoming update was
skipped by peer 2."

What I find strange is it appears to be a conflict with itself? Peer1-Peer1?
(it must be as as I mentioned the updates are being done at one node

The conflict viewer UI says

Conflict peers (winner/loser)
ABC-PILOT/ABC-PILOT

Again indicating the same node.

This has me baffled and am struggling to see sense.

Thanks again for any help and my string of questions lately.


    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Hilary Cotter  
View profile  
 More options Nov 19 2009, 9:02 am
Newsgroups: microsoft.public.sqlserver.replication
From: "Hilary Cotter" <hilary.cot...@gmail.com>
Date: Thu, 19 Nov 2009 09:02:40 -0500
Local: Thurs, Nov 19 2009 9:02 am
Subject: Re: update-update conflict on same node
you probably did a version of a dummy update.

http://support.microsoft.com/kb/973223

"Ron" <R...@discussions.microsoft.com> wrote in message

news:9E37A64E-E88F-49DC-8BD9-071D80485E10@microsoft.com...


    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Ron  
View profile  
 More options Nov 19 2009, 9:28 am
Newsgroups: microsoft.public.sqlserver.replication
From: Ron <R...@discussions.microsoft.com>
Date: Thu, 19 Nov 2009 06:28:01 -0800
Local: Thurs, Nov 19 2009 9:28 am
Subject: Re: update-update conflict on same node
Hilary, you just made my day.

I've yet to install but agree it looks very similar to the problem I have
been having, thanks for taking the time to reply. I thought I had lost the
plot.

I wonder how it is I couldn't track down this error on the web, no matter
thanks again.


    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Ron  
View profile  
 More options Nov 20 2009, 6:40 am
Newsgroups: microsoft.public.sqlserver.replication
From: Ron <R...@discussions.microsoft.com>
Date: Fri, 20 Nov 2009 03:40:01 -0800
Local: Fri, Nov 20 2009 6:40 am
Subject: Re: update-update conflict on same node

I can confirm that this hotfix solved the problem, though it was very
slightly different to the one reported. My UPDATE statement was setting a
column to a value that it was already set to, rather than the contents of the
same column. Small difference but I suppose the same effect.

Thanks again Hilary


    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2010 Google