Error 18482 Could Not Connect
Contents |
360 games PC games sp_addremotelogin Windows games Windows phone games Entertainment All Entertainment
Sp_dropdistributor
Movies & TV Music Business & Education Business Students & educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
produced: SQLServer Enterprise Manager could not configure 'server' as the Distributor for 'server' Error 18482: Could not connect to server 'SSSS' because 'SSSS' is not defined as a remote server. Where ‘server' is the name of the local server (which is also acting as the distributor) and ‘SSSS' is a different name. Cause: This error has been observed on a server that had been renamed after the original installation of SQL Server, and where the SQL Server configuration function ‘@@SERVERNAME' still returned the original name of https://support.microsoft.com/en-us/kb/217395 the server. This can be confirmed by: select @@SERVERNAME
go This should return the name of the server. If it does not then follow the procedure below to correct it. Remedy: To resolve the problem the server name needs to be updated. Use the following: sp_addserver real-server-name, LOCAL if this gives an error complaining that the name already exists then http://www.cryer.co.uk/brian/sqlserver/ssem_cncd.htm use the following sequence: sp_dropserver real-server-name
go
sp_addserver real-server-name, LOCAL
go If instead the error reported is 'There is already a local server.' then use the following sequence: sp_dropserver old-server-name
go
sp_addserver real-server-name, LOCAL
go Stop and restart SQL Server. Other Possible Remedies Phillip Ushijima has told me that he had an issue with pushing a subscription with the error messages indicated. His solution was to edit the SQL Server registration properties in the Enterprise Manager MMC to match the name returned by @@servername. Whilst he is not sure whether it was significant, he had previously added an alias into the client configuration on the distributor/publisher with a matching name (although this was unsuccessful in resolving the error on its own). These notes are believed to be correct for SQL Server 7 and may apply to other versions as well. About the author: Brian Cryer is a dedicated software developer and webmaster. For his day job he develops websites and desktop applications as well as providing IT services. He moonlights as a technical author and consultant.
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 Help Expand Search https://www.experts-exchange.com/questions/27829895/SQL-Server-2008-cannot-delete-publisher-error-18482.html Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website http://www.sqlservercentral.com/Forums/Topic641456-291-1.aspx Testing Store Headlines Experts Exchange > Questions > SQL Server 2008 cannot delete publisher error 18482 Want to Advertise Here? Solved SQL Server 2008 cannot delete publisher error 18482 Posted on 2012-08-15 MS SQL Server 1 Verified Solution 5 Comments 776 Views Last Modified: 2013-01-24 I tried to delete publisher and got error: Cannot delete publication xxx. Cannot connect to error 18482 server'Distibution server name' becase 'Publisher server name' is not defined as a remote server. error 18482. I checked and my publisher server defined as remote server and distibution server, subscriber server also in sysserver table defined as remote servers. appreciate your help in advance. 0 Question by:DDB Facebook Twitter LinkedIn Google LVL 25 Best Solution byTempDBA Try running following in master server select @@servername If this gives NULL it means something is wrong with error 18482 could the metadata. So, make it fine using:- Use Master go exec Sp_DropServer '
up Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 2005 » SS2K5 Replication » distribution DB not available due to server... distribution DB not available due to server crash Rate Topic Display Mode Topic Options Author Message Remco-427773Remco-427773 Posted Thursday, January 22, 2009 2:58 AM Forum Newbie Group: General Forum Members Last Login: Thursday, March 10, 2011 2:27 AM Points: 2, Visits: 45 Hi,Two publishing SQL 2000 server, one subscriber server with a distribution DB. The Subcriber has unfortunately crashed. SQL 2005 server was reinstalled, but they forgot that the distribution DB resided on that server. I have two publsihing SQL2000 server, now these server are unable to find the distributor DB, as a result I cannot setup replication again on both SQL 2000 servers. I already used the sp_removedbreplication to remove the publication from both SQL 2000 server but I'm stil unable to add a new publication because both servers are looking for the non existing Distribution DB on the re-installed server. I receive the following error:_______The distributor is not available.Error 18482: Could not connect to server 'reinstalled server' because 'Publishing server' is not defined as remote server. VErify that you have specified the correct server name.________Any help?thanks,Remco Post #641456 Old McDonaldOld McDonald Posted Thursday, January 22, 2009 3:50 AM Mr or Mrs. 500 Group: General Forum Members Last Login: Tuesday, April 7, 2015 4:55 AM Points: 540, Visits: 994 I think the following sequence should help you:1. Execute sp_adddistributor on master db of distributor.2. Execute sp_adddistributor on on master db of all publishers.3. Execute sp_adddistributiondb on the distributor.For parameters refer to BOL. Let us know if it works. -Vikas Bindra Post #641484 Remco-427773Remco-427773 Posted Thursday, January 22, 2009 6:56 AM Forum Newbie Group: General Forum Members Last Login: Thursday, March 10, 2011 2:27 AM Points: 2, Visits: 45 hi vikas,I have tried your soultion, but I am still not succesful. I'll explain:>1. Execute sp_adddistributor on master db of distributor.This worked out perfectly on the Distributor (SQL 2005)>2. Execute sp_adddistributor on on master db of all publishers.This didn't work and generated the following, something with remote login not defined. The following erorr is given:Could not connect to server 'YYY' because 'distributor_admin' is not defined as a remote login at the server. Verify that you hav