Error 18483 Sql Server 2000
SQL Server experts to answer whatever question you can come up with. Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads sp_addremotelogin on these forums. SQL Server Forums Profile | ActiveTopics | Members | Search | ForumFAQ sp_dropserver Register Now and get your question answered! Username: Password: Save Password Forgot your Password? All Forums SQL Server 2000 Forums Import/Export (DTS) and Replication (2000) Error 18483 while configuring distributor Reply to Topic Printer Friendly Author Topic dontipton Starting Member USA 8 Posts Posted-09/09/2002: 11:28:22 While configuring my distributor I received the following error:Error 18483: Could not connect to server because "distributor_admin" is not defined as a remote login at the server.Anyone have any ideas? dtipton@state.oh.us chadmat The Chadinator USA 1974 Posts Posted-09/09/2002: 16:25:00 Is your server registered as an IP address? If so, register it as the servername instead, then try again.If that doesn't do it, select @@servername and make sure it matches the netbios name.-Chad mko Starting Member 2 Posts Posted-04/02/2003: 17:26:18 I have the same problem. What do you mean that the servername should match the netbios name? tkizer Almighty SQL Goddess USA 38200 Posts Posted-04/02/2003: 18:05:44 Sort of a double post:(Edit Removed the link to post info)This article explains NetBIOS:http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnntpro00/html/NetBIOS.aspFor the most part, the NetBIOS name of the server is actually the real name of the server. Chadmat was just saying not to use the IP address as the name, but instead use the NetBIOS name.Tara garyn Starting Member USA 5 Posts Posted-11/17/2011: 18:43:16 I encountered this error after someone had left unfinished a failed attempt to setup ServerA as Publisher using the existing Distributor on ServerB. When I tried to run SQL2000 E/M's "Configure Publishing and Distribution" wizard on ServerA, I got this error. SSMS has separate wizards for Configuring Publishing vs Configuring Distribution, and one of those offered to drop a hidden existing (broken) Publisher partially-defined in metadata on ServerA. The wizard executed sp_dropdistributor @no_checks = 1, @ignore_distributor = 1, and the error 18483 was resolved for all client tools. I surmise a wizard had neglected in the past to create and coordinate the distributor_admin accounts & passwords between ServerA and ServerB; I never found that account on either, and it is apparently required if Publishe
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=19639 from others in the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top SQL Server Error 18483 - When Setting Up SQL Distribution up vote 2 down vote favorite I'm trying to synchronize a couple http://dba.stackexchange.com/questions/6845/sql-server-error-18483-when-setting-up-sql-distribution tables in one SQL Server 2000 database into another SQL Server 2005 database using replication. When I am attempting to set up my SQL Server as a distributor, I'm getting the following error: SQL Server Enterprise Manager could not configure 'VIPER' as the Distributor for 'VIPER' . Error 18483: Could not connect to server 'VIPER' because 'distributor_admin' is not defined as a remote login at the server. In doing research, I found several sources and articles that show that my machine name, and the actual name of the server are not the same. When I check the sysservers view in master, I see that: 0 1089 VMSSERV SQL Server SQLOLEDB VMSSERV 4/23/2008 9:50:41 AM 1 1601 repl_distributor SQL Server SQLOLEDB VIPER 10/12/2011 1:23:18 PM 2 1184 CHARLIE SQL Server SQLOLEDB CHARLIE 2/18/2011 1:32:14 PM The first line is the original database that was setup, and that I intend on using. You can see (kinda) that the original name is VMSSERV and the actual machine name is VIPER. So, from the results of my extensive w
up Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar http://www.sqlservercentral.com/Forums/Topic441997-291-1.aspx Who's On Home » SQL Server 2005 » SS2K5 Replication » Replication error 18483 Replication error 18483 Rate Topic Display Mode Topic Options Author Message Ed7Ed7 Posted Friday, January 11, 2008 1:39 PM Old Hand Group: General Forum Members Last Login: Thursday, January 21, 2016 8:34 AM Points: 355, Visits: 930 I setup trans replication between sql error 18483 2005 (subscriber) and sql 2000 (publisher).When config the distributor, I run into an error 18483 could not connect to server 'GHS0023RPT' because 'distribution_admin' is not defined as a remote login at the server.I search in forum and find many answers but not really help.1. I already setup server alias on sql 2000 and sql 2005. --- SQL error 18483 sql Server client Network utility (sql 2000) --- SQL Server Configuration Manager (sql 2005)2. On sql 2000. I validate the window server 2003 property. The computer name is "GHS0023RPT'.3. Select @@Servername. It returned "GHS023RPT'.Please help.TJ Post #441997 wayne gillettwayne gillett Posted Wednesday, January 23, 2008 9:26 AM Valued Member Group: General Forum Members Last Login: Friday, July 10, 2015 9:26 AM Points: 50, Visits: 555 I might be a bit late with this answer but I noticed a difference in the computer name (item2) and @@servername (item3). If that was the point you were making then you could run the following script. It will correct the error. You will have to stop and start SQL.-- Use the Master databaseUSE masterGO-- Declare local variablesDECLARE @serverproperty_servername varchar(100), @servername varchar(100)-- Get the value returned by the SERVERPROPERTY system functionSELECT @serverproperty_servername = CONVERT(varchar(100), SERVERPROPERTY('ServerName'))-- Get the value returned by @@SERVERNAME global variableSELECT @servername = CONVERT(varchar(100), @@SERVERNAME)-- Drop the server with incorrect nameEXEC sp_dropserver @server=@servername-- Add the correct server as a local serverEXEC sp_addserver @server=@serverprope