Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Replication Error on SQL Server 2005 MSSQL_REPL-2147200996

Posted on 2012-12-20
8
Medium Priority
?
1,599 Views
Last Modified: 2013-01-06
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.
0
Comment
Question by:dfr031260
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 3
8 Comments
 

Author Comment

by:dfr031260
ID: 38710974
This is MERGE Replication
0
 
LVL 43

Expert Comment

by:Eugene Z
ID: 38712685
/ 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).

"
0
 

Author Comment

by:dfr031260
ID: 38713893
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.
0
Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

 

Author Comment

by:dfr031260
ID: 38713995
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.txt -OutputVerboseLevel 2

The error..:
Message
Executed as user: pola\wgadmin. The parameter is incorrect.  The step failed.
0
 

Author Comment

by:dfr031260
ID: 38714041
Here is the error log...
MergeRepLog.txt
0
 
LVL 43

Accepted Solution

by:
Eugene Z earned 1800 total points
ID: 38714831
looks like it is time to install sql 2005 sp4

http://support.microsoft.com/kb/913089

it will include some important fixes for sql2005 merge replication

like this one
http://support.microsoft.com/kb/974660
0
 
LVL 43

Expert Comment

by:Eugene Z
ID: 38714861
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."
0
 

Author Closing Comment

by:dfr031260
ID: 38749234
Spot on...thanks
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article shows gives you an overview on SQL Server 2016 row level security. You will also get to know the usages of row-level-security and how it works
It is possible to export the data of a SQL Table in SSMS and generate INSERT statements. It's neatly tucked away in the generate scripts option of a database.
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.
Using examples as well as descriptions, and references to Books Online, show the different Recovery Models available in SQL Server and explain, as well as show how full, differential and transaction log backups are performed

688 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question