"Ron" wrote:
> 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.
> "Hilary Cotter" wrote:
> > 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...
> > > 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.