Solved

SQL Express 2005 ODBC Connection Error 67 and 17

Posted on 2009-06-30
4
4,283 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
  • 2
  • 2
4 Comments
 
LVL 40

Accepted Solution

by:
Kyle Abrahams earned 500 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

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

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

INTRODUCTION: While tying your database objects into builds and your enterprise source control system takes a third-party product (like Visual Studio Database Edition or Red-Gate's SQL Source Control), you can achieve some protection using a sing…
Data architecture is an important aspect in Software as a Service (SaaS) delivery model. This article is a study on the database of a single-tenant application that could be extended to support multiple tenants. The application is web-based develope…
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…

808 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