September 8, 2015 at 1:10 pm
Hello All, I have a weird issue that has sprung up on a not so common configuration
cliffs
started a new job recently
a lot of the stuff set up was done a fair amount of time ago
still exploring configurations / setups
come into work today to find merge replication failing and peeling back the layers of the onion have let to one road block after another.
EDIT:
This is resolved, I was able to figure this out. It dawned on me that in the hierarchy, the subscriber was also a re-publisher which I wasn't aware of at first...and even though the tables were different that were being republished the fact that the subscriber database was listed as a published database appears to be the issue.
I had to:
1. script out the down stream publication / subscriptions
2. drop the down stream publication
3. script out and drop the up stream publication / subscription
4. re-create the up stream publication / subscription
5. verify that was working
6. once working, I added the down stream publication / subscription
Once this was done in the following order, the publication was working again.
Basics
Publisher / distributor = 2008r2 sp3
subscriber = 2012 sp2
subscriber is also part of an availability group
This past weekend there was a failover (windows patching) and now the merge replication is pointing to the new primary and failing.
After discussing with the other DBA he enlighted me to the following (which goes through the steps of fixing the broken subscription)
https://msdn.microsoft.com/en-us/library/hh882436.aspx
Going through the steps listed, I find another issue when using the GUI ("for merge publications, the subscriber must not exceed the version of the publisher).
SO...that was a little shock, since this has been apparently functioning for quite some time, and I have no idea how it was originally set up as that wasn't documented and the person doesn't work here (ever heard that one before!!!)
I can, however add the subscription via t-sql without error and it looks like it starts working again...but here is the weird part.
I add the subscription, then run the snapshot agent, then start the synchronization...replication starts the application of the snapshot, and it looks like it makes it all the way through the process...the row counts match at each end...
Then it appears at the end of the sync tasks, it has an issue and blows up with the following error
2015-09-08 15:42:26.194 The merge process was unable to deliver the snapshot to the Subscriber.
If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write.
shortly followed by:
Message: Cannot find the object 'MSmerge_ctsv_FFC1150006B248139828C108E0C87137', because it does not exist or you do not have permission.
it is a push subscription, I cannot for the life of me figure out if this is a windows permissions error or something database related...or now the fact that this current set up shouldn't have ever worked based on the GUI error I got.
Any help or comments are appreciated.
Thanks in advance,
Lee
September 8, 2015 at 3:00 pm
Additional information, after tracing the subscriber when the snapshot is being applied, it looks like it is successful in delivering the snapshot
At the end though, for each of the articles the following statement is issued against the table
exec sys.sp_MSaddmergetriggers N'Unit', N'dbo', null, 0
followed by the error
Cannot find the object 'MSmerge_ctsv_0BF5A188A0974D838521AF4DA4DE23BB', because it does not exist or you do not have permission.
Failed to create merge replication triggers for object '[dbo].[Unit]'.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply