Agent message code 20084. The process could not connect to Distributor

Question

Agent message code 20084. The process could not connect to Distributor

jeet_personal

Right there with Babe

Points: 765
More actions
September 3, 2009 at 10:26 pm

#385310

Hi
I am getting the following error message while running a transactional replication:
Agent message code 20084. The process could not connect to Distributor
Any Idea?

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Jack Corbett SSC Guru Points: 184394 More actions · Answer 1

Is the distributor on the same server or another one?

Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question

Siva K SSC Veteran Points: 297 More actions · Answer 2

I have the same issue. Trying to replicate from SQL 2005 to 2 subscribers on 2008. one server is succeeded and another one is failing. Getting error "Agent message code 20084. Process could not connect to subscriber <serverName>". Using managment studio 2008 I could connect to all servers. Ping is working fine in all direction. Attached screen shot. Any ideas pls?

jjcastroc031 SSC Rookie Points: 41 More actions · Answer 3

try to see the permission in the folder respdata.

and review in te sql configuration area that the server allow remote conections

steve smith-401573 SSChampion Points: 10889 More actions · Answer 4

@Jeet - any resolution to your problem? I was struggling with the same issue, only within SQL Server 2008; I tried both windows authentication and SQL Server authentication, and finally determined that I had to be careful which login I used, a windows login or SQL Server login. And, finally, specifying the correct password also helped (identical login names, but different passwords for windows and SS login.)

Jack Corbett SSC Guru Points: 184394 More actions · Answer 5

Does this help, http://social.msdn.microsoft.com/Forums/en/sqlreplication/thread/77c224fd-d3d8-427e-ace8-8c7c237bc830?

Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question

dave-e-hill Newbie Points: 1 More actions · Answer 6

I know this is years later BUT the error message still crops up when replicating between 2016 and 2019.

I was beating myself up over it trying all sorts of combinations of IDs, permissions and passwords

Finally resolved after installing the latest SQL Cumulative Updates (CU 25) on the Subscription server.

Dave