Error 18483 Sql Server Replication
Contents |
additional information might be available elsewhere. Thank you for searching on this message; your search helps us identify those sp_dropserver areas for which we need to provide more information. If the product or version you are looking for is not listed, you can use this search box to search TechNet, the Microsoft Knowledge Base, and TechNet Blogs for more information. Enter the product name, event source, and event ID. For example: Vista Application Error 1001.
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar 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 2005 (subscriber) and sql 2000 (publisher).When config the distributor, I run into an error 18483 could not connect to http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=SQL+Server&ProdVer=2000.80.760.0&EvtID=18483&EvtSrc=MSSQLServer 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 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 http://www.sqlservercentral.com/Forums/Topic441997-291-1.aspx "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=@serverproperty_servername, @local='local'Link for script: http://support.microsoft.com/kb/818334Wayne Post #446508 Ed7Ed7 Posted Wednesday, January 23, 2008 12:00 PM Old Hand Group: General Forum Members Last Login: Thursday, January 21, 2016 8:34 AM Points: 355, Visits: 930 It resolved. Thanks a lot for your help. Post #446581 alpeshpradhanalpeshpradhan Posted Wednesday, June 16, 2010 1:38 AM Grasshopper Group:
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get https://www.experts-exchange.com/questions/21585274/SQL-server-Replication-distributor-admin.html Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > SQL server Replication - distributor_admin Want to Advertise Here? Solved http://www.verycomputer.com/156_2cfa313ca08b011b_1.htm SQL server Replication - distributor_admin Posted on 2005-10-05 MS SQL Server 1 Verified Solution 5 Comments 3,924 Views Last Modified: 2008-05-28 Hi I am trying to setup replication in SQL server 2000. 1. selected distributor 2. sql server Configure the sql server agent service to start automatically 3. specified snapshot folder on a shared drive 4. Customized the distribution database 5. Gave database name and folder path for the db and log 6. Enabled server to use the distributor 7. Enable publication database 8. Did not select subscribers When the wizard is completed and the setup runs, it breaks at 'Configuring Distributor' i get the following issue. SQL Server sql server replication Enterprice Manager could not configure [server name] as the Distributor for 'server name' Error 18483: Could not connect to server 'xxxxxxxx' because 'distributor_admin' is not defined as a remote login at the server. Help is appreciated. 0 Question by:sansoftura Facebook Twitter LinkedIn Google Best Solution bymaxomedia You need to run sp_dropserver first, then go for sp_addserver. No worries, it does not delete your database. Do you have Publication and Distribution on the same server ? If you do, and you have Go to Solution 4 Comments Message Expert Comment by:maxomedia2005-10-07 Hello Check to make sure SELECT @@SERVERNAME returns correct servername. If not then you will need to run sp_dropserver
Replication on SQL 7.0, but I get the following Error: Error 18483: Could not connect to the server "Old_Name" because "distributor_admin" is not defined as a remote login at the server. I renamed the computer, awhile ago, and this is the only reason I can think of for this error, but how to I get around it without, reinstalling the whole thing. Shane. Top Error 18483 - Can't Configure Replication after Renaming Server. by Michael Hote » Tue, 21 Dec 1999 04:00:00 You can't. The only reliable way to get SQL Server running again after renaming a machine is to completely uninstall and reinstall SQL Server. -- Mike Schema Manager 1.0 review is up: http://www.mssqlserver.com/products SQL Server resources: http://www.mssqlserver.com Jokes, general products, and consulting: http://www.mhotek.com Certification resources: http://www.certfaq.com SYSOP PASS Discussion Forums: http://www.sqlpass.org "Aim high. You can never achieve more than you aspire to." - Al Reis Please direct all replies to the newsgroup unless specifically stated otherwise. Top 1. configuring distribution and publishing: error 18483 Hello, I do not manage to configure distribution and publishing for replication in SQL Server 2000. I use SQL Server 2000 SP3 with Windows 2000 Server. The steps: 1) login as 'sa' on the 'my server' in Enterprise Manager 2) click on my server in "server group". 4) right-click -> "properties" 4) tab "replication" 5) click button "configure" 6) the wizard "configure distribution and publishing wizard on 'my server'" appears. 7) click "Next" 8) choose "Make 'my server' its own distributor" and click "Next" 9) choose "Yes, make the 'SQL start agent' start automatically" and click "Next" 10) let the default replication database folder and click "Next" ( if it warns that this is a special network share that can be accessed only by administrator, then click "Yes" ) 11) choose "No, I want to use these default settings" and click "Next" 12) click "Finish" Then, the following error appears: "SQL Server Enterprise Manager could not configure 'my server' as the distributor for 'my server'. Error 18483: Could not connect to server 'my server' because 'distributor_admin' is not defined as a remote login at the server." I tried to create a login 'distributor_admin' on my server in SQL Server Enterprise Manager but I then had the same error. When I create this login, there is no option about whether to make this login 'remote' or not. The documentation is not speaking about this wizard for the documentation on distribution and publishing configuration but it speaks a