Learn how to resolve a setup bug in the Microsoft SQL Server 2005 Beta 2 April CTP that results in a Error Locating Server/Instance Specified error message.
Tested with Microsoft SQL Server 2005 Beta 2 April CTP
If you receive the following error during installation of Microsoft SQL Server 2005 Beta 2 April CTP, perform
the following steps to resolve the issue:
TITLE: Microsoft SQL Server 2005 CTP Setup
----------------------------------------
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName;=Microsoft%20SQL%20Server&ProdVer;=9.00.1116&EvtSrc;=setup.rll&EvtID;=29545&EvtType;=lib%5Codbc_connection.cpp@Do_sqlScript@OdbcConnection::connect@xffffffff
Run SQLServerManager.msc from the Run dialog box. SQLServerManager.msc is installed ONLY when
you have installed the Client Tools. So, in order to perform this fix, also install the client tools.
Expand the SQL Native Client Configuration tree in the left pane.
Select the Client Protocols node in the left pane.
Right-click on the Shared Memory protocol and then click on Enable.
Click on Retry from the Microsoft SQL Server 2005 Beta 2 April CTP Setup error dialog box.
Thank you very much. This was the solution to my problem.By Chris A @ 7/31/2005 1:27:22 PM
This resolved mine as well. Thanks for your help!!By Tino T @ 8/1/2005 11:33:26 PM
Interestingly enough, I had this problem when I was trying to connect to an MSDE instance from Enterprise manager - I do have both SQL Express and MSDE installed - your solution also solved my problemBy SG @ 8/8/2005 12:22:25 PM
I don't know if we have automatic solution for this. I will deploy SQL Express via ClickOnce. I can't manually enable Client Native Connection for each.By Immanuel @ 8/8/2005 2:48:59 PM
Thanks, I couldn't conenct with SQLcmd utility and this solved my problem.
Thanks a lot!!!By Dale @ 8/9/2005 12:26:42 PM
Thank you so much!By barni07 @ 8/24/2005 5:20:42 PM
Well, my problem isn't solved. I can't open the Sql Server Configuration Manager. The error I get is:
Cannot connect to WMI provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 servers with SQL Server Configuration Manager.
Acceso denegado. [0x80070005]
Thank you so much!By jconigliaro @ 8/25/2005 10:50:06 AM
Make sure that these steps are performed during the installation, when the error dialog appears. If you try to do this before the install, or after the rollback, you will get the "Cannot connect to WMI provider..." error.By jmb @ 8/28/2005 7:25:03 AM
Thanks it is okBy Neil @ 3/31/2006 2:07:18 AM
Shared memory is running, and I get the following error when I try to connect on the local machine using the account that I installed the software with:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
Current .Net Version: 2.0.50727
