dfr031260
asked on
Replication Error on SQL Server 2005 MSSQL_REPL-2147200996
The I update a column in a I get the following error message...:
The merge process was unable to access row metadata at the 'Subscriber'. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to write to, or use SQL Profiler to determine the source of the failure. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200996)
Get help: http://help/MSSQL_REPL-2147200996
New request is not allowed to start because it should come with valid transaction descriptor. (Source: MSSQLServer, Error number: 3989)
There was only 1 subscription.
I have dropped and recreated the publication and subscription. It does not happen with all the tables I am replicating, just this one table.
The merge process was unable to access row metadata at the 'Subscriber'. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to write to, or use SQL Profiler to determine the source of the failure. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200996)
Get help: http://help/MSSQL_REPL-2147200996
New request is not allowed to start because it should come with valid transaction descriptor. (Source: MSSQLServer, Error number: 3989)
There was only 1 subscription.
I have dropped and recreated the publication and subscription. It does not happen with all the tables I am replicating, just this one table.
Last Comment
/ http://ask.sqlservercentral.com/questions/29246/merge-replication-error.html /
"
This might happen if you have records in the child tables referencing subscriber parent records which no longer exist. You can try to run the agent with
-output [some_file_path] -OutputVerboseLevel desired_level
The output verbose level should be 0, 1, or 2:
•0 to print only error messages
•1 to print all progress report messages
•2 (default and most useful when debugging) to print all error and report messages.
It goes without saying that these switches have a very negative impact on performance, but in your case, they might be useful to identify the actual source of the problem as it is entirely possible that the problem has nothing to do with FK integrity violations and could be something else. I don't believe though that it has anything to do with the tempdb activity (despite what the error message says).
"
"
This might happen if you have records in the child tables referencing subscriber parent records which no longer exist. You can try to run the agent with
-output [some_file_path] -OutputVerboseLevel desired_level
The output verbose level should be 0, 1, or 2:
•0 to print only error messages
•1 to print all progress report messages
•2 (default and most useful when debugging) to print all error and report messages.
It goes without saying that these switches have a very negative impact on performance, but in your case, they might be useful to identify the actual source of the problem as it is entirely possible that the problem has nothing to do with FK integrity violations and could be something else. I don't believe though that it has anything to do with the tempdb activity (despite what the error message says).
"
ASKER
Is this run with the merge agent? Currently the Merge Agent step has:
-Publisher [POLAOVGALAXY] -PublisherDB [SCDS_Pro] -Publication [MergeRepl_scds_pro] -Subscriber [polaovstage\five] -SubscriberDB [SCDS_Pro] -Distributor [POLAOVGALAXY] -DistributorSecurityMode 1
When I added:
-output [d:\SQLReplLog] -OutputVerboseLevel 2
It threw and error...: Message
2012-12-21 18:11:02.171 The handle is invalid.
-Publisher [POLAOVGALAXY] -PublisherDB [SCDS_Pro] -Publication [MergeRepl_scds_pro] -Subscriber [polaovstage\five] -SubscriberDB [SCDS_Pro] -Distributor [POLAOVGALAXY] -DistributorSecurityMode 1
When I added:
-output [d:\SQLReplLog] -OutputVerboseLevel 2
It threw and error...: Message
2012-12-21 18:11:02.171 The handle is invalid.
ASKER
Got it to run somewhat, but got another error. This is the merge agent step...:
-Publisher [POLAOVGALAXY] -PublisherDB [SCDS_Pro] -Publication [MergeRepl_scds_pro] -Subscriber [polaovstage\five] -SubscriberDB [SCDS_Pro] -Distributor [POLAOVGALAXY] -DistributorSecurityMode 1 -Output D:\SQLReplLogs\MergeRepLog
The error..:
Message
Executed as user: pola\wgadmin. The parameter is incorrect. The step failed.
-Publisher [POLAOVGALAXY] -PublisherDB [SCDS_Pro] -Publication [MergeRepl_scds_pro] -Subscriber [polaovstage\five] -SubscriberDB [SCDS_Pro] -Distributor [POLAOVGALAXY] -DistributorSecurityMode 1 -Output D:\SQLReplLogs\MergeRepLog
The error..:
Message
Executed as user: pola\wgadmin. The parameter is incorrect. The step failed.
ASKER
Here is the error log...
MergeRepLog.txt
MergeRepLog.txt
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
also , as per the error:
"The Merge Agent was unable to update information about the last synchronization at the Subscriber. Ensure that the subscription exists at the Subscriber, and restart the Merge Agent."
"The Merge Agent was unable to update information about the last synchronization at the Subscriber. Ensure that the subscription exists at the Subscriber, and restart the Merge Agent."
ASKER
Spot on...thanks
Microsoft SQL Server
Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.
171K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
ASKER