September 6, 2017 at 1:20 am
Can anyone please help me out to solve this error in SQL Server merge replication?
The merge process could not replicate one or more INSERT statements to the 'Subscriber'. A stored procedure failed to execute. Troubleshoot by using SQL Profiler. (Source: MSSQLServer, Error number: -2147200990)
A query executing on Subscriber 'DB-TEST' failed because the connection was chosen as the victim in a deadlock. Please rerun the merge process if you still see this error after internal retries by the merge process. (Source: MSSQLServer, Error number: 20245)
Cannot issue SAVE TRANSACTION when there is no active transaction. (Source: MSSQLServer, Error number: 628)
September 8, 2017 at 12:30 pm
ahsanmumtaz - Wednesday, September 6, 2017 1:20 AMCan anyone please help me out to solve this error in SQL Server merge replication?
The merge process could not replicate one or more INSERT statements to the 'Subscriber'. A stored procedure failed to execute. Troubleshoot by using SQL Profiler. (Source: MSSQLServer, Error number: -2147200990)
A query executing on Subscriber 'DB-TEST' failed because the connection was chosen as the victim in a deadlock. Please rerun the merge process if you still see this error after internal retries by the merge process. (Source: MSSQLServer, Error number: 20245)
Cannot issue SAVE TRANSACTION when there is no active transaction. (Source: MSSQLServer, Error number: 628)
As the error message says, you would want to troubleshoot this like any other deadlock. Refer to the following links for more information - and when you hit this error, you should be able to find more information in the system_health extended events session that is normally running by default. Capturing the deadlock information is explained more in the second link:
Detecting and Ending Deadlocks
Capturing Deadlocks in SQL Server
Sue
September 11, 2017 at 3:09 am
Dear All,
Thanks for considering my question, Your response showing that you haven't faced this error in your environment.
i just resolved mentioned issue by creating missing indexes on replication system tables like "Msmerge_content, Msmerge_tombstone, Msmerge_genhistory.....Msmerge....etc."
after making missing indexes on replication system tables it run faster like a charm.
so at conclusion if any one faces above mentioned error should take a look on missing indexes on replication system tables.
Thank you.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply