Solved

SQL 2008 Connection Failed when connecting through ODBC

Posted on 2010-08-16
9
805 Views
Last Modified: 2012-05-10
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.
0
Comment
Question by:ITGhost
  • 3
  • 2
  • 2
  • +2
9 Comments
 
LVL 1

Expert Comment

by:Wiebren
ID: 33450072
Have you tried turning off the firewall for minute to see if thats the issue ?
0
 
LVL 1

Author Comment

by:ITGhost
ID: 33450096
I have turned off the Firewall, but tried immediately afterward.  This is on a single server, however.
0
 
LVL 7

Expert Comment

by:lundnak
ID: 33450130
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?
0
The Eight Noble Truths of Backup and Recovery

How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.

 
LVL 1

Author Comment

by:ITGhost
ID: 33450139
All three are enabled.
0
 
LVL 8

Expert Comment

by:Julianva
ID: 33452236
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



0
 
LVL 2

Accepted Solution

by:
dhlotter earned 500 total points
ID: 33453772
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.
0
 
LVL 8

Expert Comment

by:Julianva
ID: 33453870
dhlotter
the backslash is quite right, mistake in my comment.

0
 
LVL 1

Author Closing Comment

by:ITGhost
ID: 33455316
Thanks for this answer.
0
 
LVL 2

Expert Comment

by:dhlotter
ID: 33461566
pleased we could help
0

Featured Post

Microsoft Certification Exam 74-409

VeeamĀ® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

This article explains how to reset the password of the sa account on a Microsoft SQL Server.  The steps in this article work in SQL 2005, 2008, 2008 R2, 2012, 2014 and 2016.
For both online and offline retail, the cross-channel business is the most recent pattern in the B2C trade space.
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.
Viewers will learn how to use the INSERT statement to insert data into their tables. It will also introduce the NULL statement, to show them what happens when no value is giving for any given column.

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question