"Vikas Kohli" wrote:
> Just to add more...
>
> I cant reinitialize the Replication since the Data volume is huge and I
> can't send that accross WAN. I have to use the property 'do not initialize
> Schema or data' when I add subscription.
>
> "Vikas Kohli" wrote:
>
> > When I had first configured this, everything was OK. However to carry a
> > schema change activity, I had dropped all the subscriptions and Publications,
> > dropped all the replication procedures, triggers manually wherever required
> > and reconfigure the Replication again after the schema change. It has started
> > giving error after then.I have tried removing replication a number of times
> > but each time same problem.
> >
> > Also please let me know what should be the normal count of Triggers at the
> > Central Subscriber, is it 12 or 4?
> >
> > "Hilary Cotter" wrote:
> >
> > > You need to reinitialize this subscription and resend your data. It looks
> > > like your replication metadata is out of sync.
> > >
> > > --
> > > 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:7DC1A948-B930-45A1-ACFF-BB88246FBC16@microsoft.com...
> > > > Hi,
> > > >
> > > > I have Merge Replication ( Articles x,y) with Publications at 4 Sites and
> > > a
> > > > Central Subscriber. All the Merge Agents are running with property
> > > > -exchangetype 2 parameter
> > > >
> > > > Article x have 12 triggers (4 for insert, 4 delete and 4 updates) which
> > > > looks OK ( 1 set for each publication) but article y has only 3 triggers(1
> > > > insert, i update and 1 delete). I am getting invalid following erros in
> > > the
> > > > conflict viewer:
> > > >
> > > > 1. The row was updated at 'SINDEV21.NewCase' but could not be updated at
> > > > 'SINDEV20.NewCase'. Invalid object name
> > > > 'ctsv_CAB6F215FE394ECAB4CE7DD56BD4B1B8'.
> > > >
> > > > 2. The row was updated at 'SINDEV21.NewCase' but could not be updated at
> > > > 'SINDEV20.NewCase'. Unable to synchronize the row because the row was
> > > updated
> > > > by a different process outside of replication.
> > >
> > >