Database access after upgrading to IIS 6.0

bubbleboy · March 16th, 2004, 06:38 PM

I have a program that queries a SQL database for information that now cannot access the database since we have upgraded to Windows 2003 and IIS 6.0.
Nothing has changed with the asp files, but I try a DSN and a DSN-less connection, the connection is not being made and I get a "This Page cannot be displayed" error message.
What do I have to do to set up IIS 6.0 to be able to access the database?
Any ideas?

Imar · March 17th, 2004, 03:37 AM

Hi there,

Did you recreate the DSN on the new machine, or did you just upgrade an older server?

To get more information about the error, make sure "Friendly http error messages" are enabled. For the browser (IE), open the Options panel, switch to the Advanced tab and disable Show friendly HTTP error messages. For IIS, open your site, click the Configuration button on either the Directory or Home Directory tab, and then switch to the Debugging tab. Make sure that Send detailed ASP error messages to client is checked.

Then run the page, and post the error message you see. Maybe that will shed some light over this problem.

HtH,

Imar

---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

bubbleboy · March 17th, 2004, 01:20 PM

Thanks for responding. Yes, I did recreate the DSN on the new machine.
To make this clear, all of this worked on iis 5.0 and only now that we upgraded to Windows 2003 and iis 6.0 has it stopped.
The error message that I get with detailed error messages is:

error '8007007f'
/wic/Default.asp, line 17

Line 17 is "conn.open cst" - this is my connection to the database.
I have tried this on 2 other asp applications with the same error message at the same lines that connects to the database (DSN-less). And this all works on iis 5.0.
I have tried all the normal changes in iis manager.

Any ideas? Thanks for your time.

Imar · March 17th, 2004, 02:36 PM

What does Google say for the error number you mentioned in combination with "server 2003"? I wouldn't be surprised if this was a common problem.....

Imar

---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

Imar · March 17th, 2004, 02:42 PM

One more thing. Does SQL Server run on the Win 2003 box? Is SQL Server even running?

You'll need the latest service packs to successfully start SQL on a Win 2003 machine....

Imar

---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

bubbleboy · March 17th, 2004, 05:09 PM

I found the answer at:
http://www.webservertalk.com/showthr...light=8007007f
Read this and go to the link at the bottom for anyone else having this problem.

Basically, I downloadeded and ran Component Checker "Comcheck.exe" from the Microsoft site and found that I had the wrong version of the oledb32.dll file based on my current version of MDAC. I followed the instructions at the above site and all was fixed.

Thanks for your help.