Steps to troubleshoot SQL connectivity issues

re: Steps to troubleshoot SQL connectivity issues

Waleed — Mon, 02 Jun 2008 15:13:22 GMT

i'm using oledb connection.

while deploying my application to client pc i can't connect to sqlserver 2005 developer ed.

while from my pc (i have vb.net 2003) i'm connecting

error message

[DBNETLIB][Connection Open(Connect()).]SQL Server does not exist or access denied

How to Change the Dynamic Port of the SQL Server Named Instance to an Static Port in a SQL Server 2005 Cluster

SQL Server Tips & Tricks — Thu, 12 Jun 2008 03:04:18 GMT

In SQL server the default instance has a listener which listens on the fixed port which is TCP port 1433.

re: Steps to troubleshoot SQL connectivity issues

Marker — Fri, 13 Jun 2008 14:30:24 GMT

I am not able to connect to SQL 2005 DB in windows authentication mode remotly from web application. Is it required to configure kerberos auhentication?

What could be the cause of this?

re: Steps to troubleshoot SQL connectivity issues

Victor — Fri, 27 Jun 2008 17:59:15 GMT

Hi!... I have this configuration:

1 SQL Server 2000 Enterprise Edition mounted on a Windows 2003 Server (wich we will call Server A). SQL Server is listening trough port 1433

1 Windows 2003 Server (wich we will call Server B)

Both Servers are on the same network group

What I need is to create an SQL Server System DSN to connect from B to a SQL Server Database located in A.

When I do This i get the following error:

[DBNETLIB]SQL Server does not exist or access denied

[DBNETLIB]ConnectionOpen (Connect()).

If I try to use the osql command, everytime i get the same error...

What might be causing this????

re: Steps to troubleshoot SQL connectivity issues

AlexWCY — Tue, 01 Jul 2008 11:04:05 GMT

Hi, I am having below error in my production server that running ASP.NET2.0 and SQL Server 2005. Can someone tell me why this error happen? Thanks.

Source = .Net SqlClient Data Provider

Error = A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - Not enough storage is available to complete this operation.) | at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)

at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)

at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)

at System.Data.SqlClient.SqlConnection.Open()

re: Steps to troubleshoot SQL connectivity issues

Ernst — Fri, 18 Jul 2008 01:06:26 GMT

Thank for Help on Step 2, it seems SQL Express defaults these all to off. SO remote access doesnt work.

re: Steps to troubleshoot SQL connectivity issues

Cor — Tue, 22 Jul 2008 20:43:58 GMT

I am having occasional/rare connection problems with ADO/ADO .Net connection pooling. The connections use aliases set up for TCP/IP. Could the problems be occurring because of Kerberos Ticket Expiration with the pooled connections or could it be that SQL Server is Orphaning the pooled connections or could it be some sort of socket problem? Perhaps someone has another suggestion as to what may be wrong. I am considering using Named Pipes instead to get around Kerberos authentication.

re: Steps to troubleshoot SQL connectivity issues

Harvey — Wed, 23 Jul 2008 17:50:16 GMT

In my case, the SQL application slows down to a crawl when the customer loses his internet service. When the service was restored by the provider, it started working like is should. Any thoughts . . .

re: Steps to troubleshoot SQL connectivity issues

SQL Protocols — Thu, 24 Jul 2008 00:16:47 GMT

Harvey, it's probably Windows Authentication and/or SSL handshaking are tring to connect the DC or some network entity.

For all other guys, some are general cases. Please ask questions in the forum so that somebody can help you troubleshooting. We need more detailed info about the failure and its circumstance!!!

Thanks.

Xinwei

re: Steps to troubleshoot SQL connectivity issues

Sarah — Wed, 20 Aug 2008 19:33:00 GMT

I've also found that running a quick trace to catch login failures is useful. App teams generally don't believe that their app is configured wrong. They will insist that the server is down even though all connectivity tests we use work. We will start the trace and have them try to connect. If you don't see a failure, you can absolutely point to a problem outside of MSSQL. It sometimes takes this to get folks to check other possibilities.

re: Steps to troubleshoot SQL connectivity issues

PuckStopper — Fri, 29 Aug 2008 23:02:56 GMT

I'm having an issue connectiont to SQL server through Access. It only occurs during testing when we set the PC date forward on the client machine. Has anyone come accross this? ErrorMsg: -2147467259 Cannot generate SSPI Context

Thanks

re: Steps to troubleshoot SQL connectivity issues

Shai — Tue, 09 Sep 2008 22:20:42 GMT

We're seeing an issue in our environment where we have a .NET 1.1 web application on a Windows 2003 server machine and SQL Server on a Windows 2000 server machine. In the application, we use SQL logins to connect to the db. What we are seeing is, when we put a bad password to log in, an error message is generated (login failed) in the event log which is what's expected, but then we continually see the same error message repeating for the next few hours as if the connection is still alive and retrying automatically. Any ideas why? Thanks

re: Steps to troubleshoot SQL connectivity issues

Nathan — Thu, 20 Nov 2008 02:48:43 GMT

I am trying to connect to a MSSQL 2005 server from a Windows NT box through a system DSN. I know 2005 prefers you use SQL Native Client to connect, however, all that is on this machine is the SQL Server driver. How can I make this work?

re: Steps to troubleshoot SQL connectivity issues

dmickel — Fri, 19 Dec 2008 00:22:51 GMT

I just installed MSSQL 2008 Server on my laptop XP SP3 for evaluation purposes. All SQL services start except for the engine. I get the following message in event viewer.

SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

When I research this I get lots of different things but none seems to help my issue.

Thanks in advance for any help.

re: Steps to troubleshoot SQL connectivity issues

SandorVigh — Fri, 19 Dec 2008 16:41:48 GMT

Please help to find the solution to problem.

We used MSSQL 2000 without any problems with ODBC , and now we tried to use MSSQL2008. Approximately on every fifth PC we cannot set the ODBC connection with SQL server, we receive error logs :

SQL State '1000'

SQL Server error 10060

SQL State '08001'

SQL server error 17

we tried everything, it seems that on some clients something missing, but I have no idea what is this.

The clients MSSQL ODBC version : 03.85.1132

with this version on one PC it is working, on the pother isn't.

I tried to turn of the firewall : no effect.

What to do ?

re: Steps to troubleshoot SQL connectivity issues

SQL Protocols — Fri, 19 Dec 2008 20:54:49 GMT

SandorVigh,

error 10060 is:

A connection attempt failed because the connected party did not properly respond after a period of time, or established

connection failed because connected host has failed to respond.

This still looks like a firewall issue if the server name is correct. Did you tried to follow my steps to troubleshoot? Is your server machine Vista/Windows Server 2008? Turning off the firewall on Vista/W2k8 is little tricky as it involves different domains.

I would suggest you post your follow up question on our forum (mentioned at the end of the blog)

Thanks,

Xinwei

re: Steps to troubleshoot SQL connectivity issues

SQL Protocols — Fri, 19 Dec 2008 20:57:43 GMT

dmickel,

Can you post a question on our forum and post the info in SQL Server Errorlog file?

Thanks.

re: Steps to troubleshoot SQL connectivity issues

SM — Tue, 17 Mar 2009 13:58:35 GMT

I am getting an error :

"Message:[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified ".

Just to brief about my setup , It goes like this;I have a SQL server 2008 installed on Win 2008 (x64)and I also have a clinet machine installed with Win 2003(32-bit).

Now I am trying to establish a connectivity between them by using SNAC tool (v10.0).

Actually I am running one benchmark application script on Client machine which first tries to establish the database connectivity .

Now I think some one can give me some clue what could be the reason for the error.I also have created Aliases on both server as well as Client machine (Was not very sure where they required to be created).

I have been strugling all alone for quite a time now.Hope someone can help me to reach at the solution.

Thanks & Regards,

SM.

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied

Sanjay — Thu, 02 Apr 2009 00:35:33 GMT

I am getting an error :

"[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied"

While accessing SQL Server 7.0 from a MS Access 2007 application. My client m/c OS: Windows XP Service Pack 2. The same access application is working on other desktop (XP SP2) in the same network. I have performed the following steps, but no hope.

#1: I found sqloledb.rll file was missing, i placed the above resource file in appropriate location. No luck.

#2: Tried repairing MDAC from INF folder, no luck.

Any suggestion? Thank you in advance.

re: Steps to troubleshoot SQL connectivity issues

thussain — Fri, 22 May 2009 02:15:26 GMT

I am getting this error sometime only when connecting to my sql server 2000 from my client machine using isql

OLE DB provider "SQLNCLI" for linked server "oa-citrix02" returned message "Login timeout expired".

OLE DB provider "SQLNCLI" for linked server "oa-citrix02" returned message "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.".

apple

Server: Msg 50000, Level 16, State 1, Line 15

Named Pipes Provider: Could not open a connection to SQL Server [5].

OrangeNamed Pipes Provider: Could not open a connection to SQL Server [5].

Steps to troubleshoot SQL connectivity issues

akhilpatel2 — Tue, 25 Aug 2009 18:44:17 GMT

Hello,

I seem to be in deep trouble over a linked server setup. I have 2 servers running SQL server 2005 standard x64 SP3. I am trying to create a linked server from one to another.

I createa link server and map a login called testuser2 (sql login) on both servers, and has sysadmin permissions. However, after running sp_addlinkedserver and sp_addlinkedsrvlogin, if I attempt running a query or run "Test Connection" the query times out or gives an error " login failed for NT AUTHORITY\ANYONYMOUS LOGON..with the client name.

If I check in the server logs (to which I was trying to query ), it gives me an error

Error: 18456, Severity: 14, State: 11.

I tried pinging and doing an nslookup from client machine and it succeeds. These are servers on same domain and in the same location. I have also ensured that both servers have named pipes enabled on them..

I also sometimes get error 7399. Linked server authentication failed, even through I can connect remootely through the same login 'testuser2' on either server.

Any help would be appreciated.

Regards

Akhil

re: Steps to troubleshoot SQL connectivity issues

SQL Protocols — Wed, 26 Aug 2009 20:48:43 GMT

Akhil,

Can you check this blog see if it can solve your problem?

http://blogs.msdn.com/sql_protocols/archive/2006/08/10/694657.aspx

Thanks.

Xinwei

re: Steps to troubleshoot SQL connectivity issues

Larry Kagan — Thu, 27 Aug 2009 17:46:06 GMT

Hi,

We have some erratic performance with our .net app which uses connection pooling and has a VERY high throughput to our SQL Server 2005 database.

We were wondering when is it appropriate to configure an additional port for SQL Server to listen on.

There are NO error messages in the SQL Server log nor in the client logs indicating a particular problem, but netstat reports a high number of TCP failed connections.

TCP Statistics for IPv4

Active Opens = 690858

Passive Opens = 140956

Failed Connection Attempts = 650737

Reset Connections = 6829

Current Connections = 24

Segments Received = 2971348717

Segments Sent = 1947969915

Segments Retransmitted = 5448550

Note our SQL Server version string is:

The server is a cluster using ipv4 and listening on 1433.

Thank you,

-Larry

re: Steps to troubleshoot SQL connectivity issues

keik — Thu, 15 Oct 2009 07:00:04 GMT

Sometimes the port is not 1433

Look in the registry using regedit.exe at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SQLEXPRESS\MSSQLServer\SuperSocketNetLib\Tcp.

One of the nameValue pairs has name TcpPort and a value, which is the port that the SQL Server is listening on (mine was set to 1030).

re: Steps to troubleshoot SQL connectivity issues

S. Balakrishnan — Fri, 06 Nov 2009 06:54:58 GMT

Hai,

We have 2008 Server & SQL 2008.

Networking load balancing also has been installed.

for 6 ips and virtual ip is 192.168.1.100

Nat policy has been created in sonicall to route the static ip to local ip.

Now i am trying to conect the odbc it say server does not exist.

What must be the issue

please help me.

Thanks & REgards

S. Balakrishnan

re: Steps to troubleshoot SQL connectivity issues

S. Balakrishnan — Fri, 06 Nov 2009 07:03:00 GMT

Hai

We have 2008 Server & SQL 2008

Networking Load Balance has been configured

the virual ip is 192.168.1.100

Nat policy has been created throguh sonicwall to this ip from the public ip (static Ip).

Now i am strying to connect the odbc. it says server does not exist

Please help me to trouble shoot

Thanks

S. Balakrishnan

edp@rajparkchennai.com

re: Steps to troubleshoot SQL connectivity issues

Aaron Barr — Wed, 09 Dec 2009 22:24:38 GMT

Thank You so much Keik. You helped determine the last port I had to unblock. I am running SQL 2008 on WS 2008. For anyone else having this issue for me I did this.

On my Windows Server 2008 I did the following:

1.Added an exception for the SQL Browser exe file.

2.Added an exception for the UDP Port 1434.

3.Found out what the listening port was by following Keik's advice which is

"Look in the registry using regedit.exe at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SQLEXPRESS\MSSQLServer\SuperSocketNetLib\Tcp.

One of the nameValue pairs has name TcpPort and a value, which is the port that the SQL Server is listening on (mine was set to 1030)."

Mine was 51070 then added the exception to that tcp in the windows firewall.

Then boom all access finally granted. Thank you Keik for suggesting that as it finally became unblocked and now works like a champ. I have spent litterally 2 days getting this to work and I had figured that it was a simple firewall issue but was lost on where to find the information. God Bless you Sir!