how to get rid of sqlserver instance specific error in sql server 2008 error 40

Question

0.00/5 (No votes)

See more:

SQL-Server-2008

i have installed sqlserver 2008 just now and trying to connect. but iam getting the following error

Cannot connect to HEMANTH-PC.

ADDITIONAL INFORMATION:

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)

in the server protocols - i have checked the tcp-ip port and set it to enable.
and named pipes to enable, and checked the instance it is running and i have added the port 1433 to the windows firewall also but still not able to connecting to the server. getting the same error please help me out. thanks in advance.

Posted 26-Jul-14 2:11am

raxhemanth

Updated 26-Jul-14 2:53am

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2014-07-26T06:17:00

Have you tried the simple stuff? Changes are that the Server instance name is wrong, or you have the wrong authorization type or username / password combination.
Try to connect via SSMS or the Visual Studio Server Explorer pane. When that works, you'll have a better idea what the connection string should be (VS will even give you a working string for a specific database)

If that doesn't do it, we'd need a fair amount more info as to exactly what you are toing to try to connect.