SQL Express 2005 ODBC Connection Error 67 and 17

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
Jake PrattAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Kyle AbrahamsSenior .Net DeveloperCommented:
Did you launch the configuration and enable Named Pipes/TCP IP?  By default this is disabled.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Kyle AbrahamsSenior .Net DeveloperCommented:
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
Jake PrattAuthor 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
0
Jake PrattAuthor 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!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.