Merge reversed

Running Win 2000 & SQL 2000
I have a merge publication/subscription (rows are
filtered by location), replicating data between 16
servers (15 remote location & a main office). When data
is changed at the a remote location, the changes gets
propagated to the main office, but at some point, the
change gets reversed.
Any idea what is causing this?
Larry,
when you say it gets reversed, do you mena the row is deleted from the
subscriber? This could be caused if you are partitioning data and a row has
been added on a subscriber which doesn't accord with its filter.
HTH,
Paul Ibison
|||Look in the conflict table, for the article, on the publisher. This might
give you a clue as to what is going on.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Paul,
No the row is not deleted, but changed back to its
original state, prior to being updated at the
subscriber. This happens sporadically, but is causing
MAJOR problems.
Larry...
|||Rand,
There is nothing in the conflict tables for any article
in the publication.
Larry...
|||I saw your reply to Rand and if both filtering and conflicts are ruled out
(and no user on the publisher is altering the data!) then this is very
strange. I'd use profiler or an audit trigger to capture what is going on.
HTH,
Paul Ibison
|||Thanks Paul...will do.
|||Does the MSmerge_history table on the distributor offer any reason why
the updates were not applied?
Reinout Hillmann
SQL Server Product Unit
This posting is provided "AS IS" with no warranties, and confers no rights.
anonymous@.discussions.microsoft.com wrote:
> Rand,
> There is nothing in the conflict tables for any article
> in the publication.
> Larry...
>

Merge Replication Problem

Hi all,

OS: Windows 2000 Server
SQL: SQL Server Standard 2000

I was searching the forums and the web but didn't find any information on solving this problem.

On the publisher when I look at the Replication Monitor -> Merge Agents section I see the following error to only one of the 4 subscribers. I've tried to removing and recreating the subscriber, unfortunately that didn't work so i recreated the merge replication all together with a new name and removed the original, this also didn't solve the problem.

I'm worried this is a problem on the subscriber, recently we renamed the windows computer name (which caused some data access and login errors), after doing a registry rebuild for SQL all of that seemed to be cleared up. NOt sure if this helps but I guess some background can't hurt.

So here's the error info that comes up.

Error Information

Agent, Merge Replication Provider, -2147200994
The process could not make a generation at the 'Subscriber'.

Data Source, SUBSCRIBER_DB_NAME, 515
Cannot insert the value NULL into column 'nicknames', table 'MyDB.dbo.MSmerge_genhistory'; column does not allow nulls. INSERT fails.

Thanks for any help...You have to do a no-sync subscription.
Check the following :
select * from sysmerge_subscriptions
go
Run sp_helpserver on the subscribing server and the srvid should be 0 for the subscriber.|||Hi Satya,

Thank you very much for the reply, at the very least it got me looking into nosync subscriptions...

Unfortunately I wasn't able to figure out how to set one up as such, and if simply changing the srvid at the subscriber is all that needs to be done.

I followed your instructions and ran the two queries you specificied at the SUBSCRIBER (not sure if both were supposed to be run at the subscriber...) and here are the results (in the attached zipped, csv file..) the srvid is not 0 for any of the rows.

If you get a chance to look at it and see the problem, or what needs to be changed (or how I should setup the nosync subscription), please do let me know...

once again thank you very much.|||Refer to books online about dynamic snapshot and applying them manually.

If any triggers are involved then execute sp_addsynctriggers, before that follow books online about this SP.