Skip to main content

MERGE PROCESS WAS UNABLE TO CREATE A NEW GENERATION


error message:


THE MERGE PROCESS WAS UNABLE TO CREATE A NEW GENERATION AT THE “SUBSCRIBER”. TROUBLESHOOT BY RESTARTING THE SYNCHRONIZATION WITH VERBOSE HISTORY LOGGING AND SPECIFY AN OUT PUT FILE TO WHICH TO WRITE.


I tried "update sysmergepublications set [generation_leveling_threshold] = 0"
on both Subscriber and Publisher, still it didn't work.

Then I tried "select count (*) from dbo.MSmerge_contents" and "select count (*) from dbo.MSmerge_genhistory" on the Subscriber

The both query was running indefinely with no results, instanly I realised there is some Locking problem.

In desperation I restarted the Subscriber Database Engine and started the Agent.

Magic! Replication was successfull.




Popular posts from this blog

Web synchronization option for merge replication

http://msdn2.microsoft.com/en-us/library/ms151319.aspx SQL Server 2005 Books Online Implementing Replication over the Internet Replicating data over the Internet allows remote, disconnected users to access data when they need it using a connection to the Internet. Replicate data over the Internet using: A Virtual Private Network (VPN). For more information, see Publishing Data over the Internet Using VPN . The Web synchronization option for merge replication. For more information, see Web Synchronization for Merge Replication . All types of Microsoft SQL Server replication can replicate data over a VPN, but you should consider Web synchronization if you are using merge replication.

Request Signatures in Blackberry

Request Signatures in Blackberry need copy sigtool.db, sigtool.csk to SDK/component/Bin folder for example V 4.2.1 ../eclipse\plugins\net.rim.eide.componentpack4.2.1_4.2.1.17\components\bin