‘%s’ is not configured as a Distributor.

Details
Product: SQL Server
Event ID: 14114
Source: MSSQLServer
Version: 10.0
Component: SQL Server Database Engine
Message: ‘%s’ is not configured as a Distributor.
   
Explanation

If the error message specifies a particular instance, rather than ‘null’, the instance specified has not been properly configured to be recognized as a Distributor.

If the message specifies ‘null’ as a Distributor, there is no entry for the local server in
master
database, or the entry is incorrect (perhaps because the computer was renamed). Replication expects all servers in a topology to be registered using the computer name with an optional instance name (in the case of a clustered instance, the SQL Server virtual server name with the optional instance name). For replication to function properly, the value returned by SELECT @@SERVERNAME for each server in the topology should match the computer name or virtual server name with the optional instance name.

Replication is not supported if you have registered any of the SQL Server instances by IP address or by Fully Qualified Domain Name (FQDN). If you had any of the SQL Server instances registered by IP address or by FQDN in SQL Server Management Studio when you configured replication, this error could be raised.

   
User Action

If the error message specifies a particular instance, configure the server as a Distributor. For more information, see Configuring Distribution.

If the message does not specify a particular instance (‘null’), verify that the Distributor instance is registered properly. If the network name of the computer and the name of the SQL Server instance differ, either:

  • Add the SQL Server instance name as a valid network name. One method to set an alternative network name is to add it to the local hosts file. The local hosts file is located by default at WINDOWS\system32\drivers\etc or WINNT\system32\drivers\etc. For more information, see the Windows documentation.

    For example, if the computer name is comp1 and the computer has an IP address of 10.193.17.129, and the instance name is inst1/instname, add the following entry to the hosts file:

    10.193.17.129 inst1

  • Disable distribution, register the instance, and then reestablish distribution. For information about disabling distribution, see Disabling Publishing and Distribution. If the value of @@SERVERNAME is not correct for a non-clustered instance, follow these steps:

    sp_dropserver ”, ‘droplogins’
    go
    sp_addserver ”, ‘local’
    go

    After you execute the sp_addserver (Transact-SQL) stored procedure, you must restart the SQL Server service for the change to @@SERVERNAME to take effect.

    If the value of @@SERVERNAME is not correct for a clustered instance, you must change the name using Cluster Administrator. For more information, see Failover Clustering.

   
   
Version: 9.0
Component: SQL Server Database Engine
Message: ‘%s’ is not configured as a Distributor.
   
Explanation

If the error message specifies a particular instance, rather than ‘null’, the instance specified has not been properly configured to be recognized as a Distributor.

If the message specifies ‘null’ as a Distributor, there is no entry for the local server in
master
database, or the entry is incorrect (perhaps because the computer was renamed). Replication expects all servers in a topology to be registered using the computer name with an optional instance name (in the case of a clustered instance, the SQL Server virtual server name with the optional instance name). For replication to function properly, the value returned by SELECT @@SERVERNAME for each server in the topology should match the computer name or virtual server name with the optional instance name.

Replication is not supported if you have registered any of the SQL Server instances by IP address or by Fully Qualified Domain Name (FQDN). If you had any of the SQL Server instances registered by IP address or by FQDN in SQL Server Management Studio when you configured replication, this error could be raised.

   
User Action

If the error message specifies a particular instance, configure the server as a Distributor. For more information, see Configuring Distribution.

If the message does not specify a particular instance (‘null’), verify that the Distributor instance is registered properly. If the network name of the computer and the name of the SQL Server instance differ, either:

  • Add the SQL Server instance name as a valid network name. One method to set an alternative network name is to add it to the local hosts file. The local hosts file is located by default at WINDOWS\system32\drivers\etc or WINNT\system32\drivers\etc. For more information, see the Windows documentation.

    For example, if the computer name is comp1 and the computer has an IP address of 10.193.17.129, and the instance name is inst1/instname, add the following entry to the hosts file:

    10.193.17.129 inst1

  • Disable distribution, register the instance, and then reestablish distribution. For information about disabling distribution, see Disabling Publishing and Distribution. If the value of @@SERVERNAME is not correct for a non-clustered instance, follow these steps:

    sp_dropserver ”, ‘droplogins’
    go
    sp_addserver ”, ‘local’
    go

    After you execute the sp_addserver (Transact-SQL) stored procedure, you must restart the SQL Server service for the change to @@SERVERNAME to take effect.

    If the value of @@SERVERNAME is not correct for a clustered instance, you must change the name using Cluster Administrator. For more information, see Failover Clustering.

   
   
Version: 8.0
Component: SQL Engine
Message: ‘%s’ is not configured as a Distributor.
   
Explanation
If the message specifies a particular instance, as opposed to ‘null,’ the instance specified has not been properly configured to be recognized as a Distributor.

If the message specifies ‘null’ as a Distributor, there is no entry for the local server in the sysservers table in the master database, or the entry is incorrect. To verify the local server setting, connect to the local server and run “SELECT @@SERVERNAME” from Query Analyzer. If a (NULL) is returned, an entry for the local server does not exist in the sysservers table in the master database. If a value other than the Computer Name or SQL Virtual Name is returned, the entry is incorrect, perhaps because the computer was renamed. Note that a restart of SQL Server is required for changes to the local server to be reflected in @@SERVERNAME.

Fore more information on this message, see the Microsoft Knowledge Base article 302223.

   
User Action
If the message specifies a particular instance, as opposed to ‘null,’ you must either pass in a valid Distributor instance name or configure the desired instance as a Distributor. To verify if an instance is configured as a Distributor, use the stored procedure sp_helpdistributor. A Distributor can be configured through the Replication tools in SQL Enterprise Manager or with the sp_adddistributor stored procedure.

If the message specifies ‘null,’ verify that the value of @@SERVERNAME is correct for each server involved in this replication topology. Execute “SELECT @@SERVERNAME” and “EXEC master..xp_cmdshell ‘set computername'”. When ‘set computername’ is executed from Query Analyzer or OSQL for a clustered instance, it returns the SQL virtual server name rather than the node name, and the SQL virtual server name is the value needed for replication.

  • For a nonclustered default instance, “SELECT @@SERVERNAME” should return the same value as “EXEC master..xp_cmdshell ‘set computername'”.
  • For a nonclustered named instance, “SELECT @@SERVERNAME” should return the value as “EXEC master..xp_cmdshell ‘set computername'” plus “\” plus the name of the instance.
  • For a clustered default instance, “SELECT @@SERVERNAME” should return the same value as “EXEC master..xp_cmdshell ‘set computername'”.
  • For a clustered named instance, “SELECT @@SERVERNAME” should return the value as “EXEC master..xp_cmdshell ‘set computername'” plus “\” plus the name of the instance.

If the value of @@SERVERNAME is not correct for a nonclustered instance, follow these steps:

sp_dropserver ‘{old_name}’, ‘droplogins’
go
sp_addserver ‘{new_name}’, ‘local’
go

Note: After you run the sp_addserver stored procedure, you must restart the SQL Server service for the change to @@SERVERNAME to take effect.

If the value of @@SERVERNAME is not correct for a clustered instance, then you must uninstall and reinstall the clustered instance to correct the name.

Verify that all SQL Server instances used as a Subscriber, Publisher, and/or Distributor are listed in the replication properties by their computer name or their SQL virtual server name. If they are not, you will need to remove replication, register each SQL Server instance in your local Enterprise Manager by computer name or SQL virtual server name, then reestablish replication.

For more information, see theMicrosoft Knowledge Base articles 321822 and 818334.

Related:

Leave a Reply