Subscriber not connecting to Publisher/Distributer in Transactional Replication

  • Hi

    I recently set up Transactional Replication between 2 Servers Londonsc1 and Londonbi1

    Londonsc1 is the publisher and distributor

    Londonbi1 is a pull subscriber

    Subscriptions are set to never expire

    Everything was running swimmingly until we had an outage that meant that all of our servers had to be restarted. Now the subscription job on Londonbi1 is giving an error message

    The remote server "Londonsc1" does not exist, or has not been designated as a valid publisher or you may not have permissions to see available publishers.

    The permissions and accounts should not have changed. I have tried restarting the SQL Server Agents on both servers, running the distribution cleanup jobs and even trying to re-initialise the subscriptions to no avail

    The Account running the subscription on LondonBI1 has access to the Replication folder on Londonsc1 which I have checked and also is listed as being able to connect to the distribution database on Londonsc1.

    Are there any other things I could try short of deleting the subscription and starting again?

    Many Thanks

  • I have managed to resolve this issue by adding the account runnning the subscription on Londonbi1 (subscriber server) to the list of accounts on the Publication Access list on Londonsc1 (Publisher and distributor server).

    Although I can see how this resolves the error message, I'm not entirely sure why I was not getting this error message when I initially set the replication up and why its been running successfully until now

Viewing 2 posts - 1 through 1 (of 1 total)

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