Category: Troubleshooting

SQL 2005 Merge Agent Blocking in MSmerge_generation_partition_mappings

ReplTalk Troubleshooting June 22, 2011

Share this PostIf 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
Read More »

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

ReplTalk Troubleshooting April 26, 2011

Share this PostSateesh 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)
Read More »

Distribution agent failing with “procedure was called with an incorrect number of parameters”.

ReplTalk Troubleshooting April 26, 2011

Share this PostSateesh Yele Microsoft SQL Server Support Transactional replication allows you to specify how data changes are propagated from the Publisher to Subscribers. For more information, please check this link. Specifying How Changes Are Propagated for Transactional Articles Recently, I worked on a case where the distribution agent failed with procedure was called with
Read More »

MSSQL_REPL-2147199360 Unable to decide if MakeGeneration is needed.

ReplTalk Inside Replication, Troubleshooting April 24, 2011

Share this PostError messages: Unable to decide if MakeGeneration is needed. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199360) Get help: http://help/MSSQL_REPL-2147199360 Query timeout expired (Source: MSSQLServer, Error number: 0) Get help: http://help/0 The merge process failed to execute a query because the query timed out. If this failure continues, increase the query timeout for the process. When
Read More »

Clearing Resolved Merge Replication Conflicts

ReplTalk Inside Replication, Troubleshooting April 19, 2011

Share this PostContent provided by: Steve Dybing, Microsoft SQL Server Support Background on Merge Conflicts ———————————————- When a Publisher and a Subscriber are connected and synchronization occurs, the Merge Agent detects if there are any conflicts. If conflicts are detected, the Merge Agent uses a conflict resolver (which is specified when an article is added
Read More »