The Web Agent for IIS will not work

Question

Environment: NT4 Server, IIS4
I try to install the Web Agent in use with IIS but IIS fails to load the dll. After the installation I can read the event-log :
The HTTP server was unable to load the ISAPI Application 'C:\Oracle\Ora81\ord\web\bin\wsciis81.dll'. The data is the error.
And the Browser gives me:
A dynamic link library (DLL) initialization routine failed.
What can be wrong?

Answer 1

Note: On Windows NT, use \ instead of / to separate file system directory
paths.
1. Check the Web Agent's log file.
Look in <oracle_home>/ord/web/logs for a log file in the form
wsc_<yyyymmdd>_<pid>.log. If the file exists, review it for errors,
then take the necessary action to remedy the problem. Possible
problems that might be logged are non-recoverable errors in the Web
Agent's configuration file <oracle_home>/ord/web/admin/wsc.cfg. If the
configuration file or the <oracle_home>/ord/web directory hierarchy
doesn't exist, then re-do the installation.
2. Check the Web Agent's "last-chance" error log file.
If the <oracle_home>/ord/web/logs directory exists, but there are no
log files, check in the %SystemRoot% directory on Windows NT or the
/tmp directory on Unix for a file named wsclstch.err. This is the Web
Agent's "last-chance" error log file. The Web Agent will try to write
to this file if it encounters a fundamental startup error, such as a
problem initializing CORE or NLS, creating a log file, or opening its
message file. If the file exists, review it for errors, then take the
necessary action to remedy the problem. (In a command window on
Windows NT, type set SystemRoot to find where the wsclstch.err file
would be written.)
3. Check the web server configuration.
If the Web Agent failed to create either its normal log file or its
"last-chance" error log file, verify that the Web Agent has been
configured correctly for the particular web server being used and that
the web server is running.
o Microsoft IIS
Use the Internet Service Manager to verify that IIS has been
configured correctly for the Web Agent. Review the installation
and configuration instructions in the wsciis.html or wsciis.txt
files to verify that the Web Agent has been configured correctly
and to make any changes or fixes necessary. Check that the filter
is up and running and that the virtual path has been configured.
To check the filter, select the web site, then click the
properties button (or right-click the web site icon). Select the
Filters tab. The Web Agent should appear in the list with a green
up-arrow. If it appears with a red down-arrow, check the Windows
NT event log for any errors relating to the Web Agent. IIS
doesn't always write detailed error messages. For example, if a
DLL used by the Web Agent can't be located, then IIS typically
logs the fact that a load error occurred along with the message
"the data was the error". Note that the installation and
configuration instructions describe the case where the filter
must be installed manually if there were no existing filters
registered at the time the Web Agent for IIS was installed.
If the filter looks OK, check the oracle_intermedia_bin virtual
path by clicking the properties button (or right-click the
virtual path icon). The path should reference the
<oracle-home>\ord\web\bin directory, which should contain the
wsciis81.dll file. In the properties window, select the directory
security tab, then click the anonymous access and authentication
control button. Verify that Basic authentication has been checked
and that Windows NT challenge/response has been cleared.
To function correctly, the Oracle8i home must be specified
correctly for IIS. Use the Oracle Home Selector to verify that
the Oracle8i home is specified as the default home. Use the
System Control Panel to verify that the Oracle8i home /bin
directory is specified prior to any other Oracle homes in the
PATH environment variable.
null