Unable to connect with Active Server Pages
I have been unable to get Active Server Pages to make a valid connection to an Oracle database on one of our web boxes.
What I'm running:
IIS 5 on Windows 2000 Service Pack 2, ADO 2.6, Oracle client software installed from the 8.16 CD, VBScript Version 5.5.6330.
What works:
Using SQL*Plus, Oracle Connection tester, and a VB 6 application I wrote to test making connections. Using my VB app, I can make a connection using either Microsoft's ODBC driver, Oracle's ODBC driver, or OLE DB. I can make the connection either using a DSN or a DSN-less connection string. Since all of these tools work, I've just about ruled out any problems with the install of the Oracle client software.
What doesn't work:
Making any kind of connection to Oracle using any driver from Active Server Pages. The error message changes depending on the driver being used:
...when using the OLE DB connection string: "Microsoft OLE DB Provider for Oracle error '80004005' Oracle client and networking components were not found. These components are supplied by Oracle Corporation (etc)".
...when using Oracle's ODBC driver: "Microsoft OLE DB Provider for ODBC Drivers error '80004005' Specified driver could not be loaded due to system error 5 (Oracle ODBC driver)."
...when using Microsoft's ODBC driver: "Microsoft OLEDB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed"
What I've tried:
I've used the same ASP test scripts on two other machines, and if functions properly. So I know it's not a problem with my connect strings. I've searched the internet and news groups, and while this seems to have been a problem for some other people, I haven't found a real solution. It appears to be some kind of permissions problem with ASP, IIS, the IUSR or IWAM account, but I can't pin it down to anything specific. I've looked at the more obvious file-level permissions (like the Oracle directory, the WINNT directory, and Program Files\Common Files\System). There don't seem to be any differences between the machines that work and the machine that doesn't.
Does anyone have suggestions of other things I can try? Since this is a production server some of our options are a little limited (we can't rebuild the box ;-)
---------------------------------------------------------------------
Todd W. Hensley
Global Information Technology Group
Dana Corporation