"umesh" <umesh@discussions.microsoft.com> wrote in message
news:5E54715C-4EE4-4D7A-B5C0-E1AF17BD1213@microsoft.com...
> Hello Hilary
>
> Thank you very much for the reply.
>
> In my replication scenario, I am creating all the setup (database
> creation,
> publications, subscription, everything) through scripts. After doing this,
> the replication seems to work fine, by checking the values in both
> Publisher
> and subscriber. But after some time, with out making any change in
> replication settings, it seems that replication fails and the conflict
> viewer
> shows the error message as I posted earlier.
>
> Also in another dicussion I found the same problem mentioned by another
> person and there it was asked to check whether any DTS action is going on.
> As
> in our development enviornment some person might have tried for this or
> done
> some thing related to DTS. Could you please tell me how can I check or
> conclude that the replication problem is because of DTS. Or any other
> method ?
>
> Thank you
> Umesh
>
>
> "Hilary Cotter" wrote:
>
>> Did you disable any of the merge replication triggers?IIRC this will
>> cause
>> this error.
>>
>> --
>> Hilary Cotter
>> Director of Text Mining and Database Strategy
>> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
>>
>> This posting is my own and doesn't necessarily represent RelevantNoise's
>> positions, strategies or opinions.
>>
>> 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
>>
>>
>>
>> "umesh" <umesh@discussions.microsoft.com> wrote in message
>> news:43AD8F20-A649-4539-927C-20F0FB379AC5@microsoft.com...
>> > Hi
>> >
>> > The actual error message is "The row was updated at 'publihser' but
>> > could
>> > not be updated at 'subscriber'. Unable to synchronize the row because
>> > the
>> > row
>> > was updated by a different process outside of replication."
>> >
>> > Thanks in advance
>> > Umesh
>> >
>> > "umesh" wrote:
>> >
>> >> Hi,
>> >>
>> >> I have a database with SQL Server 2000 and many MSDE. I need to
>> >> replicate
>> >> all MSDE database to the central Server, which is SQL Server 2000.
>> >> Also I
>> >> dont need to replicate from central database to all other MSDE
>> >> database.
>> >> So
>> >> central database just acts as backup for all MSDE and also the
>> >> replication
>> >> should occur in 5 seconds, as some client applications are connected
>> >> to
>> >> this
>> >> Server database to show the values in all MSDE database. I cannot do
>> >> Transactional replication since using MSDE as database in all machines
>> >> excpet
>> >> the one used as Server.
>> >> Thus the topology is, Multiple publisher - Central Subscriber, with
>> >> one
>> >> direction (ExchangeType=2 , publisher to subscriber only) and
>> >> replication
>> >> interval as 5 seconds (PollingInterval 5).
>> >> Does this topology has any problem ?
>> >> The replication is working, but after some time, some tables dont
>> >> replicate
>> >> and the conflict message comes like 'Cannot update as some process
>> >> outside of
>> >> replication is accessing the row' .
>> >>
>> >> Please comment on this...
>> >>
>> >> Thanks in advance
>> >> Umesh
>>
>>
>>

"Hilary Cotter" wrote:

> It sounds like a row is present in the tables published for merge
> replication which is missing replication tracking metadata. For an insert it
> is easy to understand how this row could be present (non logged operations).
> For an update it is more difficult to see how such tracking metadata could
> be missing. Disabling replication triggers is one of the reasons which can
> cause this. In your scenario I can't think of anything obvious.
>
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
>
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
>
> 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
>
>
>
> "umesh" <umesh@discussions.microsoft.com> wrote in message
> news:5E54715C-4EE4-4D7A-B5C0-E1AF17BD1213@microsoft.com...
> > Hello Hilary
> >
> > Thank you very much for the reply.
> >
> > In my replication scenario, I am creating all the setup (database
> > creation,
> > publications, subscription, everything) through scripts. After doing this,
> > the replication seems to work fine, by checking the values in both
> > Publisher
> > and subscriber. But after some time, with out making any change in
> > replication settings, it seems that replication fails and the conflict
> > viewer
> > shows the error message as I posted earlier.
> >
> > Also in another dicussion I found the same problem mentioned by another
> > person and there it was asked to check whether any DTS action is going on.
> > As
> > in our development enviornment some person might have tried for this or
> > done
> > some thing related to DTS. Could you please tell me how can I check or
> > conclude that the replication problem is because of DTS. Or any other
> > method ?
> >
> > Thank you
> > Umesh
> >
> >
> > "Hilary Cotter" wrote:
> >
> >> Did you disable any of the merge replication triggers?IIRC this will
> >> cause
> >> this error.
> >>
> >> --
> >> Hilary Cotter
> >> Director of Text Mining and Database Strategy
> >> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> >>
> >> This posting is my own and doesn't necessarily represent RelevantNoise's
> >> positions, strategies or opinions.
> >>
> >> 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
> >>
> >>
> >>
> >> "umesh" <umesh@discussions.microsoft.com> wrote in message
> >> news:43AD8F20-A649-4539-927C-20F0FB379AC5@microsoft.com...
> >> > Hi
> >> >
> >> > The actual error message is "The row was updated at 'publihser' but
> >> > could
> >> > not be updated at 'subscriber'. Unable to synchronize the row because
> >> > the
> >> > row
> >> > was updated by a different process outside of replication."
> >> >
> >> > Thanks in advance
> >> > Umesh
> >> >
> >> > "umesh" wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> I have a database with SQL Server 2000 and many MSDE. I need to
> >> >> replicate
> >> >> all MSDE database to the central Server, which is SQL Server 2000.
> >> >> Also I
> >> >> dont need to replicate from central database to all other MSDE
> >> >> database.
> >> >> So
> >> >> central database just acts as backup for all MSDE and also the
> >> >> replication
> >> >> should occur in 5 seconds, as some client applications are connected
> >> >> to
> >> >> this
> >> >> Server database to show the values in all MSDE database. I cannot do
> >> >> Transactional replication since using MSDE as database in all machines
> >> >> excpet
> >> >> the one used as Server.
> >> >> Thus the topology is, Multiple publisher - Central Subscriber, with
> >> >> one
> >> >> direction (ExchangeType=2 , publisher to subscriber only) and
> >> >> replication
> >> >> interval as 5 seconds (PollingInterval 5).
> >> >> Does this topology has any problem ?
> >> >> The replication is working, but after some time, some tables dont
> >> >> replicate
> >> >> and the conflict message comes like 'Cannot update as some process
> >> >> outside of
> >> >> replication is accessing the row' .
> >> >>
> >> >> Please comment on this...
> >> >>
> >> >> Thanks in advance
> >> >> Umesh
> >>
> >>
> >>
>
>