?
Solved

SQL Express 2005 ODBC Connection Error 67 and 17

Posted on 2009-06-30
4
Medium Priority
?
4,314 Views
Last Modified: 2012-08-13
I have recently upgraded a database from SQL 2000 to SQL Express 2005.  The DB name is Pds.  I installed SQL Express 2005 along side SQL 2000, then I went in, detactched the DB from the old instance "SERVERNAME", and attached it to my new instance "SERVERNAME\SQLEXPRESS".  The program that uses this database can access everything just fine, but now I cannot create an ODBC driver to connect to this database.  When I attempt to connect via ODBC, I get this error:

Connection failed:
SQLState: '01000'
SQL Server Error: 67
[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 is denied.

I've looked all over, but I figure out what's wrong here.  I'm connecting via sa.  What am I missing?

Thanks
0
Comment
Question by:Jake Pratt
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 40

Accepted Solution

by:
Kyle Abrahams earned 1500 total points
ID: 24749101
Did you launch the configuration and enable Named Pipes/TCP IP?  By default this is disabled.
0
 
LVL 40

Expert Comment

by:Kyle Abrahams
ID: 24749108
Also check if you have any firewalls blocking the ports.  The configuration is for SQL 2005, so wherever that's installed you'll find the configuration utility.  Be sure to restart the service.
0
 

Author Comment

by:Jake Pratt
ID: 24749270
Thanks.  This is a Windows 2000 SP4 server, so there is no firewall in play.  As for the named pipes/TCP/IP, I actually already looked at that, but saw some weird results.  I launched the svrnetcn utility.  When I select the SQLEXPRESS instance from the drop down list, there are no protocols available to enable or disable.  Both boxes are completely blank.

As a side note, I just installed MDAC 2.8 SP1 as a shot in the dark.  I'm waiting for it to be after hours so I can reboot the server, though.

Any thoughts on why the protocols are blank in the sql server network utility?  Or any other thoughts on how to solve this?

Thanks
0
 

Author Comment

by:Jake Pratt
ID: 24749324
Ok, I got it figured out.  You were on the right track for sure, but I was using the wrong tool.  The "svrnetcn" tool is specifically a SQL 2000 tool, and can't configure options for SQL 2005.  I found some info in this article that helped
http://www.eggheadcafe.com/forumarchives/SQLServerserver/Feb2006/post26066300.asp
Anyway, I went into the SQL Server Configuration Manager, went into the network configuration, and enabled TCP/IP... voila!  That did it.  Thanks for your help!
0

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Question has a verified solution.

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

by Mark Wills Attending one of Rob Farley's seminars the other day, I heard the phrase "The Accidental DBA" and fell in love with it. It got me thinking about the plight of the newcomer to SQL Server...  So if you are the accidental DBA, or, simp…
I am showing a way to read/import the excel data in table using SQL server 2005... Suppose there is an Excel file "Book1" at location "C:\temp" with column "First Name" and "Last Name". Now to import this Excel data into the table, we will use…
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…
In this video, Percona Solutions Engineer Barrett Chambers discusses some of the basic syntax differences between MySQL and MongoDB. To learn more check out our webinar on MongoDB administration for MySQL DBA: https://www.percona.com/resources/we…

764 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