SQL Server Database Connection | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

SQL Server Database Connection

Has anyone come across the following error message? If yes, how did you resolve it? Connection failed:
SQLState ‘0100’
SQL Server Error: 161
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect)
Connection failed:
SQLState ‘08001’
SQL Server Error: 17
[Microsoft][ODBC SQL SERVER Driver][DBNETLIB]Sql server does not exist or access denied
Some of our users are getting this error when they try and connect to one of our databases. Jason
Exactly what it says: client application is trying to contact a server under a name that no longer exists, or the server is not available (server perhaps not on-line, or it could even have run out of diskspace) or the login has failed for the credentials supplied by the client application. Try if you can make a new connection with the same user name and pwd from QA. Also, do all users have the problem, or just some of them?
The strange thing is that it’s only some of them that have the problem and all pc’ss have MDAC2.8 installed.
Do you have a workstation pre-MDAC 2.8 that you can use for testing?
KBA –http://support.microsoft.com/default.aspx?kbid=328306 – potential causes for SQL server does not exists message. HTH Satya SKJ
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
Can the PCs reach the server at all? Can you ping it by IP? Can you telnet to the SQL server port? Does domain name resolution (DSN) work on those computers so that they can find the server by name? Is there a firewall between some of the PCs (that are on another network maybe) and the sql server? Simple test 1.
Try connect to the sql server by IP (if it works, name resolution is your problem) Simple test 2.
Open a command prompt on the user PC and type:
telnet x.x.x.x 1433 where x.x.x.x is the server IP and 1433 is the sql port (unless you changed it). If you get a blank screen the sql service is responding. If not you get something like "Could not open connection to host on port 1433, connect failed". In that case you have a network issue (like a firewall in the way or something).
We are able to ping the server and can telnet the server port. Our network guys are looking at the DNS setting on those computer and checking the firewall. Thanks for you help with this Jason