Error connecting to SQL Server

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 Provider, error: 40 -
Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

Explanation

The SQL Server client cannot connect to the server. This error could occur because either the client cannot resolve the name of the server or the name of the server is incorrect.

User Action

Make sure that you have entered the correct server name on the client, and that you can resolve the name of the server from the client. To check TCP/IP name resolution, you can use the ping command in the Windows operating system.
 
How do I ping?

Thanks,
DovbermanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jerry_JusticeCommented:
It looks like it is trying to connect using named pipes.

Is TCP/IP enabled on this workstation?  Start/Run - cliconfg

Make sure TCP/IP is an enabled protocol.

If you want to ping the server: Start/Run - cmd
At the C:> prompt type "ping servername"

That doesn't help a whole lot if SQL Server you are connecting to is a named instance, but at least it tells you if that server is responding to a ping by name.

Last - can other workstations connect remotely to this SQL server?  If not, is SQL Browser service running on the server?
1

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DovbermanAuthor Commented:
This is a local installation of SQL Server.  I just re-installed. The installation was successful.

However, I cannot find the new instance.
0
Jerry_JusticeCommented:
If you are running Windows Firewall, turn it off.  It may be blocking access.  But you still need to make sure SQL Browser service is running.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

DovbermanAuthor Commented:
I can connect with Windows authentication only.
0
DovbermanAuthor Commented:
I got it.

From the SQL Server Management Studio,

Use Windows Authentication to connect without a password.

Once connected, Choose Security-->Logins.

Choose SQL Server Authentication.

Enter a login name.  Enter a password .
0
DovbermanAuthor Commented:
Thanks for the ideas.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.