Availability of the Distribution database from a Subscriber

Summary

The Subscriber is not able to reach its distribution database.

Configuration

To use this monitor, it is necessary to add administrator privileges in "Microsoft SQL Server Replication Distributor Availability from Subscriber Monitoring Run As Profile".

Db names in the db names list string should be separated by commas.

A db name should meet requirements of one of the next identifier classes:

1) Regular

• The first character must be one of the following:

- A letter as defined by the Unicode Standard 3.2. The Unicode definition of letters includes Latin characters from a to z, from A to Z, and also letter characters from other languages.

- The underscore (_)

• Subsequent characters can include the following:

- letters as defined in the Unicode Standard 3.2;

- decimal numbers from either Basic Latin or other scripts;

- the at sign (@), dollar sign ($), number sign (#), or underscore (_).

2) Delimited – can contain any characters, and should be delimited by double quotes or square brackets.

3) Undelimited – can be almost any character sequence, and should meet the next requirements:

• should not belong to one of the classes below;

• should not contain comma;

• should not start or end with any of white-space characters.

Any db name belonging to any of the classes above should be from 1 to 128 characters, not including the delimiter characters.

For more information, see https://msdn.microsoft.com/en-us/library/ms175874 page.

Causes

This situation may be caused by:

• A connectivity issue between the Distributor and the Subscriber.

• Insufficient permissions for the Replication Distribution Agent or Merge Agent account to access the Distribution database.

• Impossibility to configure CredSSP

Resolutions

Verify the following conditions:

• Ensure the network access between the Distributor and the Subscriber is correctly configured.

• Ensure any firewalls between the Distributor and Subscriber are configured to allow access on the ports used by Microsoft SQL Server.

• Ensure that the Windows Remote Management (WS-Management) service running on the Subscriber.

• Ensure firewall exceptions configured to allow connections for Windows Remote Management through HTTP-In.

• Ensure the Replication Agent’s account is configured correctly to access both the Distributor and the Subscriber.

• Ensure the Distribution Agent and Merge Agent accounts are added to the db_owner fixed role on the Distribution and the Subscriber databases.

• Ensure the monitoring account is in Local Administrators group on Distributor and on Subscribers.

• Ensure that the following registry key is present on Distributor and Subscribers: "LocalAccountTokenFilterPolicy"=dword:00000001 in [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system]

Additional

If there is a firewall in your replication topology, you may want to read the following article: http://support.microsoft.com/kb/164667/

To add LocalAccountTokenFilterPolicy key, execute the following:

reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f

Overrideable Parameters