Missing the obvious - Help please

Question

I am trying to setup the ODBC driver for the the SQLServer 2012 trial version that I downloaded and installed. I was following the steps to configure it from this site.

http://ihewiki.wustl.edu/wiki/index.php/Installation_Guide:_Windows_/_Binary#Database_Installation

I know the instructions are for SQL 2005 but this part should not have changed. It has been the same since 2000. Anyway, below are the responses that I am getting from the server. Where do I begin troubleshooting. Or am I missing the obvious? I have been away from the SQL world a long time. I have been using Apache and MySQL for over the past 10 years. This application has forced me back to SQL and it has me stumped still. (Just thought I would share some history.) 

Thanks for your help.

Microsoft SQL Server ODBC Driver Version 06.01.7601

Data Source Name: LocalServer
Data Source Description:
Server: local
Database: (Default)
Language: (Default)
Translate Character Data: Yes
Log Long Running Queries: No
Log Driver Statistics: No
Use Regional Settings: No
Prepared Statements Option: Drop temporary procedures on disconnect
Use Failover Server: No
Use ANSI Quoted Identifiers: Yes
Use ANSI Null, Paddings and Warnings: Yes
Data Encryption: No

Microsoft SQL Server ODBC Driver Version 06.01.7601

Running connectivity tests...

Attempting connection
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.

TESTS FAILED!

---

what?

Answer 1

Hello,

Are the SQL Server and the SQL Browser services running? Is the SQL Server as default or as named instance installed? Can you connect to it using SSMS = SQL Server Management Studio.

---

Olaf Helper

Blog Xing

Answer 2

Yes I can connect using the SQL Server Management Studio that is why the ODBC failing don't make sense. I believe the SQL Server is running as default the only thing I did different was to set a password for the sa account. Everything else during the installation process I left to defaults.

The SQL Browser service was in the disabled condition. I turned it on now and tried the connection again and

Microsoft SQL Server ODBC Driver Version 06.01.7601

Running connectivity tests...

Attempting connection
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.

TESTS FAILED!

Thanks!

---

what?

Answer 3

Hello,

I have seen :  "[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied"

Usually, it means that the user used to connect has no permission to connect to the database ( Windows user if Windows authentification,SQL Server login if SQL Server authentification ).

I have been surprised to see in your 1st post "Database: (Default)" , it seems that you have not defined the database name to use to connect .

I am far to be a specialist of ODBC, but i think that the name of your SQL Server instance is LocalServer. Is it true  ( or is it the name of the computer on which the SQL Server is installed ) ?

Have a nice day

---

Mark Post as helpful if it provides any help.Otherwise,leave it as it is.

Answer 4

HI,

The instance name is SQLExpress. I was instructed to write that down during the installation process is the only reason I have it. I have not created any databases yet. The only database that is there are the default ones. Is that the problem that I need to create a database first?

Thanks for the reply,

Sherwin

---

what?

Answer 5

http://social.msdn.microsoft.com/Forums/en/sqlgetstarted/thread/27684811-1a59-4273-b7ed-3cc990b4f20a

This thread fixed my problem.

The server name was the problem.

It needed to be the yourlocalserver\SQLEXPRESS.

Microsoft SQL Server Native Client Version 11.00.3000

Running connectivity tests...

Attempting connection
Connection established
Verifying option settings
Disconnecting from server

TESTS COMPLETED SUCCESSFULLY!

---

what?

Answer 6

The server name was the problem.

It needed to be the yourlocalserver\SQLEXPRESS.

That's why I asked: Is the SQL Server as default or as named instance installed?
It is a named instance SQLEXPRESS

---

Olaf Helper

Blog Xing

Answer 7

Hello,

Since the release of SQL Server 2005, if you are trying to connect to a SQL Server instance installed on the same computer  ( local connection ), you can use the .\SQLExpress syntax ( a dot before the backslash )

Another syntax is (local)

See http://blogs.msdn.com/b/sql_protocols/archive/2008/09/19/understanding-data-source-local-in-sql-server-connection-strings.aspx

but i am prefering the 1st one ( shorter )

Have a nice day

---

Mark Post as helpful if it provides any help.Otherwise,leave it as it is.