SQL 2008 Connection Failed when connecting through ODBC

Connection failed:
SQLState: '01000"
SQL Server Error: 2
[Microsoft] [ODBC SQL Server Driver][Shared Memory]
ConnectionOpen (Connect ()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.

I'm at a loss. This is a named instance, not listening on port 1433.  I can connect to the database in the management studio with no problem. Any help would be appreciated.
Who is Participating?
dhlotterConnect With a Mentor Commented:
try connecting through odbc datasource by specifying your servername like this

servername\instancename   (note the backslash)

in the client configuration, make sure you have TCP/IP selected and that the server alias and server name are both the same as the format above. also have 'dynamically determine port' enabled.

this should do the trick.
Have you tried turning off the firewall for minute to see if thats the issue ?
ITGhostAuthor Commented:
I have turned off the Firewall, but tried immediately afterward.  This is on a single server, however.
A proven path to a career in data science

At Springboard, we know how to get you a job in data science. With Springboard’s Data Science Career Track, you’ll master data science  with a curriculum built by industry experts. You’ll work on real projects, and get 1-on-1 mentorship from a data scientist.

Please make sure that Shared Memory is turned on for the Client Protocols on your SQL Server.

1. Open SQL Server Configuration manager
2. Browse to SQL Native Client x.xx Configuration
3. Click on Client Protocols.

Are Shared Memory, TCP/IP, and Named Pipes enabled?
ITGhostAuthor Commented:
All three are enabled.
when you create your odbc in servername dialog do this

servername/instance,portnumber - eg testserver/testdb,3306

you must specify port number when you have changed from default. Use the tcp protocol seems like you using named pipes, because named pipes uses shared memory.PLEASE MAKE SURE YOU  ARE USING THE CORRECT INSTANCE NAME - common mistake when using named instances. look in services for correct instance name if not sure

the backslash is quite right, mistake in my comment.

ITGhostAuthor Commented:
Thanks for this answer.
pleased we could help
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.