February 12, 2013 at 9:58 am
Hey All, I'm in the process of setting up Merge Replication on two test databases before I roll it out to our production environment.
The databases are on separate servers within a private LAN. Once I set the merge replication up there is no error given, so the assumption is that it has been set up correctly. However, the subscriber is not receiving any updates from the publisher database. Why?
I have tried troubleshooting this issue by performing;
A telnet to the other SQL port
Ensuring firewall setting have been disabled for this connection
I'm using the correct account details
That the account has been granted access to the subscriber database
The only information I can find that this process is not working is through Windows Event Viewer, I am getting the following error message;
Replication-Replication Merge Subsystem: agent NAGA-AdventureWorks2012-NagaAdevntureWorks-COBAN-6 failed. The process could not connect to Subscriber 'COBAN'.
Can anyone shed some light on this issue?
Thanks! RJ
--------------------------------------------
Laughing in the face of contention...
February 12, 2013 at 10:12 am
The merge agent cannot connect to the subscriber.
Either
1. any user cannot connect from the publisher to the subscriber due to network or firewall issues
2. The user you set up as the merge agent user cannot connect to the subscriber instance or does not have sufficient rights in the subscriber database (db_owner role).
February 13, 2013 at 9:17 am
Thanks for your response.
However, I am using the same account that the servers run under for the merge agent. I have tried creating a new user for the merge replication process but this doesn't seem to work either.
Do you have any further suggestions?
Thanks/
--------------------------------------------
Laughing in the face of contention...
February 21, 2013 at 10:20 am
This is a permissions issue.
If it is a Merge push subscription, ensure the Merge Agent process account is db_owner in the distribution database, a member of the PAL, a login associated with a user in the publication database, and has read permissions on the snapshot share.
If it is a Merge pull subscription, ensure the Merge Agent process account is db_owner in the subscription database and that the account used to connect to the Publisher and Distributor is a member of the PAL, a login associated with a user in the publication database, a login associated with a user in the distribution database, and has read permissions on the snapshot share.
All of this is covered in Replication Agent Security Model.
If you are still have problems after this, increase the -HistoryVerboseLevel to get additional details and/or enable verbose agent logging.
February 21, 2013 at 10:23 am
Hi there - Thanks for the response.
I found that this was related to my snapshot path not being unc formatted. All sorted now.
Thanks.
--------------------------------------------
Laughing in the face of contention...
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply