June 16, 2009 at 8:52 am
I have 3 servers, a publisher and a distributor (located locally), and a subscriber located 800 miles away in Chicago. I have merge replication set up between the servers on a small database (17 tables). Replication provides us with failover as well as 100% up time on our application.
My problem is that I keep getting messages in ERRORLOG like this:
Error: 14151, Severity: 18, State: 1.
2009-06-16 08:11:40.52 spid52 Replication-Replication Merge Subsystem: agent MD00XX01-DBName-DBNAMEpulication-IL00XX01-3 failed. 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.
When I launch replication monitor, all is well. When I run select count(*) against the tables at the two locations, they match. I suspect that the message is logged because of latency, but I can find no documentation to support this theory. I have looked in BOL and googled till I am blue, no luck
Any help is sincerely appreciated. Thanks
April 13, 2011 at 8:42 am
Hi There,
I am currently having a similar problem.
We scheduled time to rebuild the publications, that should resolve the issue.
Will keep you updated.
But let me know if you have found another way to resolve it.
May 6, 2011 at 3:04 am
Hi All,
Had anyone identified any reason and solution to the random Merge replication error:
"The merge process was unable to access row metadata at the 'Subscriber'."
Our replication started complaining at 18:30 last night and I've been working on this for the last two hours.
Any feedback would be welcomed.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply