Error while configuring Publisher - SQL Server could not connect to the distributor using the specified password | SansSQL

Wednesday, July 17, 2013

Error while configuring Publisher - SQL Server could not connect to the distributor using the specified password

Recently I was trying to configure replication on one of my test bed and in this scenario there are 3 servers, one for Publisher, one for Distributor and the other for Subscriber.
All went well while configuring the distributor but when I was trying to configure the publisher,
I encountered an error which says "SQL Server could not connect to the distributor using the specified password".

This is the same password I provided while configuring distributor. I even tired updating the password in distributor but still it was giving the same error.
Finally When I checked in the SQL Server logs of Distributor Server, I found the below message which says the Publisher instance is not defined as remote Server. 
Date 7/18/2013 12:40:40 AM
Log SQL Server (Current - 7/18/2013 12:40:00 AM)

Source Logon

Message
Could not connect to server 'SANSLAB\DISTRIBUTER' because 'SANSLAB\PUBLISHER' is not defined as a remote server. Verify that you have specified the correct server name.  [CLIENT: <local machine>].

When I checked in the distribution properties, the server was added to the publishers list.

To fix this issue,
I removed the Publisher instance from the List of Publishers and then added it back to the list.
  1. Connect to the Distributor SQL Server Instance
  2. Right-Click on the "Replication" Folder and Choose "Distributor Properties..."
  3. Go to the "Publishers" page and remove the publisher from the list by unchecking it
    Choose "Yes" to continue and Click "Ok" to save and exit
  4. Now re-open the "Distributor Properties..." and Navigate to "Publishers" page.
    Click "Add" >> "Add SQL Server Publisher..."
  5. Connect to the Publisher SQL Server Instance and Update the "Administrative Link Password" and click "OK"
Now you can start configuring the Publications without encountering the above error.
When this SQL Server instance was initially configured to be part of publishers, somehow the remote login to this server was not enabled. When this was re-added, the remote login to this server was enabled and hence the issue got solved.

2 comments:

Richard Smith said...

My problem turned out to be that the initial password was not complex enough.

Mark Lingo said...

I know this is old, but it just helped me out. I didn't think the problem was going to be that simple. I found several others with the same error, but this was all I needed to do.

Post a Comment