Microsoft Knowledge Base Email Alertz

Explains that you receive an Error 14114:(NULL) is not configured as a distributor error message when you try to set up a server that is running SQL Server as a distributor for replication. Provides steps to work around this problem.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 302223 - Last Review: November 30, 2005 - Revision: 4.3

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

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   (http://kbalertz.com/Feedback.aspx?kbNumber=321822/ ) How to replicate between computers that are running SQL Server in non-trusted domains or across the Internet

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
Keywords: 
kberrmsg kbtshoot kbprb KB302223
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Anonymous User Report As Irrelevant  
Written: 1/13/2006 6:01 PM
Thanks you for your help. I got the problem fixed.