Error 18483 Sql

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 sp_addremotelogin this site About Us Learn more about Stack Overflow the company Business Learn

Sp_dropserver

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 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 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 web search, I ran this in Query Analyzer: USE MASTER GO SELECT @@SERVERNAME, SERVERPROPERTY('ServerName') This returns: VMSSERV VIPER Most of my web searches show that I should refer to http://support.microsoft.com/kb/818334, which instructs to use:

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 on these forums. SQL Server Forums Profile | ActiveTopics | Members | Search | ForumFAQ Register Now and get your question answered! Username: Password: Save Password Forgot your Password? All Forums SQL Server 2000 Forums http://dba.stackexchange.com/questions/6845/sql-server-error-18483-when-setting-up-sql-distribution 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 http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=19639 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 fa

18483) http://www.sql-server-performance.com/forum/threads/replication-error-18483.6337/ Discussion in 'General DBA Questions' started by boam5, Sep 30, 2005. boam5 New Member when configuring publisher and distributor i've got http://stackoverflow.com/questions/2953383/help-with-linked-server-error this error : "error 18483 : could not connect to server g4b because 'distributor_admin' si not defined as a remote error 18483 login at the server" please help me..thx boam5, Sep 30, 2005 #2 dineshasanka Moderator Check These http://support.microsoft.com/default.aspx?scid=kb;en-us;321822 http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=7&messageid=220975 ---------------------------------------- Cast your vote http://www.geocities.com/dineshasanka/sqlserver05.html http://spaces.msn.com/members/dineshasanka dineshasanka, Sep 30, 2005 #2 boam5 New Member ok thx a lot. boam5, Sep 30, 2005 #2 (You error 18483 sql must log in or sign up to reply here.) Share This Page Tweet Please click 'Forgot Your Password' to reset your password if this is your first time using the new forums. Your name or email address: Do you already have an account? Forgot your password? No, create an account now. Yes, my password is: Stay logged in SQL Server Performance Forums Home Forums > ARCHIVED SQL Server Posts > SQL Server 7.0 and 2000 Forum Topics > General DBA Questions > Forums Forums Quick Links Search Forums What's New? Members Members Quick Links Registered Members Current Visitors Recent Activity Help Help Quick Links Smilies BB Codes Trophies Search titles only Posted by Member: Separate names with a comma. Newer Than: Advanced search...

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 Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Help with Linked Server Error up vote 0 down vote favorite In SSMS 2008, I am trying to execute a stored procedure in a database on another server. The call looks something like the following: EXEC [RemoteServer].Database.Schema.StoredProcedureName @param1, @param2 The linked server is set up correctly, and has both RPC and RPC OUT set to true. Security on the linked server is set to Be made using the login's current security context. When I attempt to execute the stored procedure, I get the following error: Msg 18483, Level 14, State 1, Line 1 Could not connect to server 'RemoteServer' because '' is not defined as a remote login at the server. Verify that you have specified the correct login name. I am connected to the local server using Windows Authentication. Anyone know why I would be getting this error? sql-server share|improve this question asked Jun 1 '10 at 21:13 Randy Minder 24.8k21107206 Just a guess but maybe a kerberos double hop issue? blogs.msdn.com/b/sql_protocols/archive/2006/08/10/694657.asp‌x –Martin Smith Jun 1 '10 at 21:17 add a comment| 2 Answers 2 active oldest votes up vote 2 down vote accepted 'Be made using the login's current security context' translates as impersonation (aka. as 'self-mapping' in SQL Server linked in terms). Access a remote server under an impersonated context means delegation. So you need to set up the constraint delegation, see Configuring Linked Servers for Delegation: Requirements for the Client The Windows user must have access permissions to SQLSERVER1 and SQLSERVER2. The user AD property Account is sensitive and cannot be delegated must not be selected. The client computer must be using TCP/IP or named pipes network connectivity. Requirements for the First/Middle Server (SQLSERVER1) The server must have an SPN registered by the domain administrator. The account under which SQL Server is running must be trusted for delegation. The server must be using TCP/IP or named pipes network connectivity. The linked serve