|
Problem(Abstract) |
Plug-in will not load when trying to configure the IBM
WebSphere Application Server plug-in module in Microsoft Internet
Information Services (IIS) V5.0 (all releases) and V6.0 (all
releases). |
|
|
|
Cause |
Two different ISAPI filters are loading the same module.
Problem details
See the information center articles Configuring
the plug-in for Microsoft Internet Information Services 6.0 on Windows
2003 server and Manually
configuring supported Web servers.
After following the preceding documents and trying to load the plug-in,
the ISAPI filter will have a red arrow and will not load. This is due to
two ISAPI filters, sePlugin and iisWASplugin, loading
the same plug-in module and plug-in file.
Notice that when you right-click on the Web Sites folder, there is a tab
called ISAPI Filters. When you look at this tab, it indicates the
status of sePlugins is Loaded (represented by a green up
arrow):
However, when you look at the IIS plug-in filter, the plug-in is not
loaded:
|
|
|
Resolving the
problem |
- Backup the plug-in module (iisWASPlugin_http.dll) and the
plug-in file (plugin-cfg.xml), as deleting the ISAPI filters will
remove the modules associated with it.
- Remove the sePlugin ISAPI filter, but make sure you deselect
the registry entry for the plug-in when you remove the sePlugin
filter. Also remove the iisWASPlugin filter.
- Put the plug-in module (iisWASplugin) back to where it
belongs (install_root/AppServer/bin). You can
also run the custom install of the plug-in if you do not want to backup
and copy the module.
- Follow the instructions to configure the plug-in for IIS and configure
ISAPI filter for WebSphere plug-in. This time it should load the plug-in
module.
|
|
|
|