PQ63507: AFTER INSTALLING WAS 4.0 TO USE IIS 5.0, GET A 404 PAGE NOT FOUND WHEN REQUESTING VIA PORT 80. | |||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||
APAR status Closed as unreproducible in next release. Error description The customer has attempted to do a manual custom install of the IIS plugin for WAS 4.0 and has discovered a 16-bit DOS path issue which is keeping the ISAPI filter from finding the iisWASPlugin.dll.The customer can point to the \bin directory the 32 bit where the full path is used and this corrects the problem.Local fix There are two ways to avoid this problem: *********************************** 1. Install WebSphere Application Server in a directory that does not contain spaces (Example: C:\WebSphere\AppServer). *********************************** 2. Procedure for fixing a manual install of WAS 4.0 with IIS. Open up the IIS ISAPI filter. IIS ->properties ->WWW service (edit button) ->ISAPI filter tab ->sePlugins ->edit Note that the path to the iisWASPlugin.dll is the 16 bit DOS path with ~1 appended to the long file names. This is what occurs when the custom install is used. By browsing to the WebSphere\AppServer\bin directory the 32 bit full path is used. This allows the ISAPI filter to find the iisWASPlugin.dll. Now delete the sePlugins virtual directory and recreate it pointing to the WebSphere\AppServer\bin directory. Restart IIS and the ISAPI filter will work. ***********************************Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server 4.0 AE and AEs * * users on a Windows environment. * **************************************************************** * PROBLEM DESCRIPTION: The IIS plugin would not work * * correctly if a user installed WebSphere * * in a directory that contained spaces. * **************************************************************** * RECOMMENDATION: * **************************************************************** IIS has trouble resolving the 16 bit shortened name for a directory that has a long file name. For example if WebSphere is installed in the directory C:\Program Files\WebSphere\AppServer the path in IIS that points to the plugin file in the C:\Program Files\WebSphere\AppServer\bin directory will look like this: c:\PROGRA 1\WEBSPH 1\APPSER 1\bin\iisWASPlugin_http.dll Since IIS does not like this path the IIS plugin for WebSphere will not be loaded.Problem conclusion Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ63507
IBM Group: Software Group
Modified date: Sep 27, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.