Cannot Connect to local SQL 2008, Named Pipes

When I launch SQL Serve Management Studio, I am receiving the following error message:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes, error: 40 Could not open a connection to SQL Server) (Microsoft SQL Server,Error: 2)

In SQL Server Configuration Manager:

The following services are running (none are stopped)

- SQL Server
- SQL Server Agent
- SQL Server Analysis Services
- SQL Server Browser
- SQL Server Integration Services
- SQL Server Reporting Services

The following protocols are enabled:

- Shared Memory
- Named Pipes
- TCP/IP

If I set the Connection Properties to Shared Memory, the provider in the error message changes from "Named Pipes" to "Shared Memory".  A timeout occurs for TCP/IP.

This SQL Server instance has been working without fail since original installation.  

No changes have been made to user accounts.

I was going to try a complete Uninstall / Re-install.  Does anyone know of anything else I could try or check?


MDKIMZEYAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
MDKIMZEYConnect With a Mentor Author Commented:
Solution in this case was to completely uninstall SQL 2008 followed by re-install - None of the usual suspects - (services, protocols, firewall, account names, spelling of server, etc.) were the cause.  I honestly don't know why this worked.
0
 
Rajkumar GsSoftware EngineerCommented:
0
 
MDKIMZEYAuthor Commented:

Actually, I'm trying to connect to a local SQL 2008 instance using Windows Authentication on the same box that I'm executing SSMS on.  

This article also assumes you can get past the "Connect to Server" dialog.
0
 
Rajkumar GsSoftware EngineerCommented:
>> The server was not found or was not accessible

Since you are from the same machine, make sure the instance name you entered to connect is spelled correctly.

Raj
0
 
MDKIMZEYAuthor Commented:
Raj,

I appreciate your input - I finally got it back but this required a complete uninstall of all SQL 2008 components and tools followed by a complete re-install.  I wonder what your experiences with these instances are like.  Many people who work with SQL Server have issues like this - with no clear reason, no hardware issues in the system logs, no changes to configuration.

Prior to this, I followed detailed troubleshooting steps at SQL Authority.com, Microsoft KB and other cases on Experts-Exchange.  Spelling was checked, Firewall exceptions and ports checked and re-checked, the firewall completely disabled, services and protocols visited and re-visited.  All to no avail what-so-ever.

This seems to be an extremely commonly reported problem that people spend hours and days trying to resolve.  After this exercise, and going through system and error logs - I can't say that I understand how this happened or why this happened and ,more imprtantly, how to keep it from happening again.

Error reporting has come along way but has a much greater distance to go.  With the literally hundreds of blog entries, group discussions and KB articles on this very error - I can honestly say that I have no clue why a complete uninstall / re-install was necessary.  SQL Servers are a backbone of business across the world so episodes like this don't leave me with a feeling of confidence.  

0
All Courses

From novice to tech pro — start learning today.