We help IT Professionals succeed at work.

SQL Express 2005 ODBC Connection Error 67 and 17

Medium Priority
4,449 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
Comment
Watch Question

Senior .Net Developer
CERTIFIED EXPERT
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION
Kyle AbrahamsSenior .Net Developer
CERTIFIED EXPERT

Commented:
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.

Author

Commented:
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

Author

Commented:
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!
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.