January 5, 2011 at 9:40 am
I am trying to set up replication between two SQL 2008 servers and I am getting the following error:
Agent message code 20084. The process could not connect to Distributor 'servera'.
The subscriber has sysadmin rights to the distributer and has read/write rights to the replication data folder. I have logged in as that account to verify all connections work properly. I am able to subscribe to the same publication on other servers using the same users. The only difference is we have a firewall between the two that are currently not working. I am able to push the subscription, but I can not pull and I would prefer to pull.
What needs to be open on the firewall to get this working? I already have the sql ports open, including the browser port (1434 for UDP).
Thanks much,
Jason
January 5, 2011 at 10:58 am
Can you check the firewall's logs to see what's trying to get through? That'll pretty much tell you what you need to let through, won't it?
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
January 6, 2011 at 11:54 am
You might have already done this. I would try to check the service account that the agent is running under to see if it has the right permissions to access the folder. I would also try telnet and ping commands to make sure they are working right between the two servers. To me it doesn't look like a firewall issue as you said push subscriptions are working. If you have already fixed it, please let us know the solution.
You can go also through the below article to troubleshoot replication issue to double where exactly you are having the issue. ihttp://blogs.msdn.com/b/chrissk/archive/2009/05/25/transactional-replication-conversations.aspx
January 6, 2011 at 12:15 pm
Thanks for the replies. The firewall is showing ports 1751 and 1753 being blocked, but I do no think that is the problem. We are working on getting them opened just for testing to see if it helps. We do not host the server in question or the firewall so getting our vendor to make the changes takes a little time.
I did already ping, telnet, portqry, and connect to the publishing SQL server from the subscribing server while logged in as the account performing the pull. Everything connects without issue.
Thanks much,
Jason
September 13, 2011 at 9:37 am
Hi there!
I have the same problem. I configured a Snapshot Replication and a push subscription. The snapshot works fine, but the distribution don't when I executed it under the windows service account that I created for it. However it works perfectly when I specify the windows Administrator account. Obviously this is a permission issue, but where?
I have assigned all the minimum permission required for the Distribution Agent to run as stated in Microsoft web sites, which are:
-Register the account in the PAL.
-Give "read & execute" permission on the share folder
-Make the account a member of the db_admin server role for the distribution db. I also did this for the replication db, just in case.
Does someone have any idea about what else can I do???
August 31, 2012 at 7:49 am
If you're running distrib.exe from the command-line, I've had this error message ("could not connect to distributor") when the distrib.exe command-line specifies a database name for the subscription to go into that doesn't match the database name that you setup when you configured the subscription! i.e. double-check the -SubscriberDB option
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply