possible resolution
in [Replication]
|
From: koen on 19 Jan 2010 02:39 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... NeilWak wrote: metadata cleanup 2147199401 02-Jan-08 Hi, I'm getting the following error on SQL Server 2005 Error messages: The Merge Agent failed after detecting that retention-based metadata cleanup has deleted metadata at the Subscriber for changes not yet sent to the Publisher. You must reinitialize the subscription (without upload). (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199401) Get help: http://help/MSSQL_REPL-2147199401 The subscription has been running fine for several months and re initialising is painful due to the size of the DB and the connection speed. Has anyone encountered this error or know of a fix? Thanks NW Previous Posts In This Thread: On Wednesday, January 02, 2008 4:52 AM NeilWak wrote: metadata cleanup 2147199401 Hi, I'm getting the following error on SQL Server 2005 Error messages: The Merge Agent failed after detecting that retention-based metadata cleanup has deleted metadata at the Subscriber for changes not yet sent to the Publisher. You must reinitialize the subscription (without upload). (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199401) Get help: http://help/MSSQL_REPL-2147199401 The subscription has been running fine for several months and re initialising is painful due to the size of the DB and the connection speed. Has anyone encountered this error or know of a fix? Thanks NW On Wednesday, January 02, 2008 1:10 PM Hilary Cotter wrote: There seems to be a bug with this that Microsoft is in the process of trying There seems to be a bug with this that Microsoft is in the process of trying to fix (from what I understand). I suggest you open a support incident with Microsoft on this. -- http://www.zetainteractive.com - Shift Happens! 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 "NeilWake" <NeilWake(a)discussions.microsoft.com> wrote in message news:A8E78C08-E908-4D41-A03B-A5BE807C7D7C(a)microsoft.com... On Monday, January 21, 2008 11:12 AM Jos? Araujo wrote: I have been having that issue since long time now... I have been having that issue since long time now... my "solution" was to disable metadata cleanup, but of course, after a year the metadata was huge. We tried republishing and changing the setting to 1 month and now, 1 month later, we have the issue again. BTW: we are on SQL2005 SP2. Jos? Araujo. "Hilary Cotter" <hilary.cotter(a)gmail.com> wrote in message news:OTBNQsWTIHA.4196(a)TK2MSFTNGP04.phx.gbl... Submitted via EggHeadCafe - Software Developer Portal of Choice ASP.NET ViewState - Extend Dynamic TextBox Control http://www.eggheadcafe.com/tutorials/aspnet/62ddc7ff-db0a-401d-825d-a92414fd7e75/aspnet-viewstate--exten.aspx
|
Pages: 1 Prev: ogical consistency-based I/O error Next: metadata cleanup 2147199401 |