Microsoft KB Archive/302223

From BetaArchive Wiki
Knowledge Base


You receive an "Error 14114: (NULL) is not configured as a distributor" error message when you try to set up a SQL Server server as a distributor for replication

Article ID: 302223

Article Last Modified on 11/30/2005



APPLIES TO

  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Express Edition
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Workgroup Edition



This article was previously published under Q302223

SYMPTOMS

When you try to set up a SQL Server server as a distributor for replication, the following error message may occur:

Error 14114:(NULL) is not configured as a distributor

CAUSE

The error message appears because there is not an entry for the local server in the sysservers table in the master database.

To verify that there is no entry for the local server in the sysservers table in the master database, connect to the local server and run "select @@servername" from Query Analyzer. If a (NULL) is returned, then an entry for the local server does not exist in the sysservers table in the master database.

WORKAROUND

To correct the problem, use these steps:

  1. Run this code:

    use master
    go
    select * from sysservers
    go
                        
  2. Identify the name of the local server in the list. If the name exists, and the server id is anything other than 0, run the following statement and replace "yourservername" with the name of the local server:

    sp_dropserver 'yourservername','droplogins'
                        

    If a non-local server has a server id value of 0, then you need to drop that entry and run the sp_dropserver stored procedure.

  3. Add the local server back to the list by running this code:

    sp_addserver 'localservername', 'local'
                        

    You must stop and then restart the SQL Server server for the changes to take effect. After the server has been restarted, run "select @@servername" to verify that the changes have been applied. Executing "select @@servername", should return the name of your local server with a server id of 0.


REFERENCES

SQL Server 2000 Books Online; topic: "Renaming Servers"

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

321822 How to replicate between computers that are running SQL Server in non-trusted domains or across the Internet



Additional query words: replication setup wizard

Keywords: kberrmsg kbtshoot kbprb KB302223