The process could not connect to Subscriber ‘ServerName’

When the message displays that it cannot connect to the subscriber, it is commonly because of the following reasons:

The subscribing server is busy

The subscribing server is down

The authentication is failing

Before correcting the problem, verify if the error message is occurring for one agent on a specific server or if it is the majority of the agents connecting to the subscriber with this problem.

If it is one subscriber, verify that the agent is not pushing a large amount of transactions.  Also, verify the both the CPU and disk space as well as the database size to rule out any of these as an issue.

Next, try to ping the subscribing server to verify that a connection can be established.

If it is only one agent that is having the issue, stop and start the agent and wait for it to connect.  Sometimes this needs to be done multiple times to establish a connection.

This issue may also occur if the agent has lost permissions to the destination subscriber.  This seldom is the case unless it is a new subscriber.

This entry was posted in Replication. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s