Merge agent failing with “Cannot insert duplicates rows into table “tablename”. Violation of PRIMARY KEY constraint” during initialization.

Sateesh Yele Microsoft SQL Server Support Last week, I worked on replication case where the merge agent was failing with the above error message. Here is the merge agent verbose log with the error message. Message: Batch send failed 2011-04-20 13:53:00.546 [39%] [346 sec remaining] Bulk copied data into table ‘MSmerge_tombstone’ (0 rows) 2011-04-20 13:53:00.843
Read More »

SQL 2005 Merge Agent Blocking in MSmerge_generation_partition_mappings

If you observe blocking in the SQL Server 2005 Merge Agent script out the “nc1MSmerge_generation_partition_mappings” index and verify the “INCLUDE (changecount)” option exists.  TO verify, generate the create index script by expanding the system tables in the published database.  Then expand “MSmerge_generation_partition_mappings” table. Right click the “nc1MSmerge_generation_partition_mappings” index and script to new query windows.  If
Read More »

Replication: Unable to Synchronize subscribers via Web Synchronization

reposting from Claudia Silva Microsoft SQL Escalation Services United Kingdom http://blogs.technet.com/b/claudia_silva/ Problem: The upload message to be sent to Publisher ‘XXX’ is being generated The merge process is using Exchange ID ‘XXXXX’ for this web synchronization session. No data needed to be merged. Request message generated, now making it ready for upload. Upload request size
Read More »

REPLICATION: My distribution agent generates a dump when replicating with my Oracle Subscriber

reposting from Claudia Silva Microsoft SQL Escalation Services United Kingdom http://blogs.technet.com/b/claudia_silva/ PROBLEM: I have a SQL Server 2005 replicating with an Oracle 11 subscriber. After installing the OLEDB driver for Oracle 11, a minidump is created every time the distributor tries to connect to Oracle: Distrib.exe crashes with STACK_OVERFLOW exception. The issue occurs while initializing
Read More »

Troubleshooting LogReader Error “repldone log scan occurs before the current start of replication”

Below are cause and recommendation for the SQL Replication LogReader error “The specified LSN (…) for repldone log scan occurs before the current start of replication in the log (…).’. When the LogReader starts, it verifies the Last Distributed transaction (last transaction in msrepl_transactions) still exists in the transaction log.  This confirms the Published database
Read More »