Prev: possible resolution
Next: SQL 2008 to SQL 2000 Merge Replication
From: Koen Mestdagh on 19 Jan 2010 02:42

Message-ID: <23bce490eb754ada94664e2dc6dfb612(a)newspe.com>
X-Mailer: http://www.umailcampaign.com, ip log:81.82.229.3
Newsgroups: microsoft.public.sqlserver.replication
NNTP-Posting-Host: 22.bb.5446.static.theplanet.com 70.84.187.34
Lines: 1
Path: news.netfront.net!news.glorb.com!news2.glorb.com!news.alt.net!msrtrans!TK2MSFTFEEDS02.phx.gbl!TK2MSFTFEEDS01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl!newspe.com
Xref: news.netfront.net microsoft.public.sqlserver.replication:1841

Hi,

We had exactly the same error after performing metadatacleanup manually at
the publisher and the subscribers.
After some trial and error, we found out that the field
cleanedup_unsent_changes in table sysmergesubscriptions at the subscribers
contained 1 instead of 0.

So resolution to fix our issue:
- backup db at publisher and subscribers (just in case);
- at subscriber: update sysmergesubscriptions set cleanedup_unsent_changes =
0 where cleanedup_unsent_changes = 1 and subscriber_server = 'Publisher'
(replacing Publisher with your name);
- start to replicate (everything should go well now);
- verify all subscriptions.

Happy merge replicating...

url:http://www.ureader.com/msg/11563919.aspx
 | 
Pages: 1
Prev: possible resolution
Next: SQL 2008 to SQL 2000 Merge Replication