Error while connecting to sql server

Question

0.00/5 (No votes)

See more:

Hi,
I have created an application in .NET that connects to an SQL Server Instance that runs in a remote machine. The problem I am getting is, some users can connect and normally use that application but for some users, this error message is coming...

"An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)"

I googled and tried the following :-
1) Enabled the Named Pipes and TCP/IP in Sql Server Configuration Manager.
2) Added the exceptions to my Firewall : a) sqlsrvr.exe b)sqlbrowser

Still I am getting the same error. I am not understanding what I need to do to resolve that as some users are able to connect but some users are not...
Please help...............

THANKS in ADVANCE...
Regards
Jashobanta

Posted 4-Jul-12 4:54am

Jashobanta

Add a Solution

Comments

Zoltán Zörgő 4-Jul-12 11:21am

Can you connect with Management Studio using tcpip on the server? Have you restarted the server? Have you checked if server is listening to that ports? Can you connect with Management Studio using tcpip on the client? Have you traced the connection status with sysinternals tcpview?

2 solutions

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)

DamithSL · Answer 1 · 2012-07-04T05:20:00

Solution 1

check below link
http://www.scrumdesk.com/Articles/HowToEnableSQLServerRemoteConnections.html[^]
http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx[^]

Posted 4-Jul-12 5:20am

DamithSL

Updated 4-Jul-12 5:36am

v2

Sandeep Mewara · Answer 2 · 2012-07-04T09:01:00

Generally, it is surface area configuration error or sql service configuration issue. Have a look at this thread for potential reasons and resolutions: Resolving A network-related or instance-specific error occurred while establishing a connection to SQL Server[^]

If needed, See steps for setting up Surface area configuration here..

Here, look at the following blog entries related to the same:
Under the default settings SQL Server does not allow remote connections[^]
It says:
I. Make sure that Remote Connections are enabled in Surface Area Configuration tool
II. Check Whether TCP/IP protocol is enabled in the SQL Server Configuration Manager
III. Make sure that SQL server Browser service is running