PQ74134: Installing WAS50 Fix Pack 1 on Windows to product default directories will prevent WebSphere service from starting. | |||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description Customer installs WebSphere Application Server V5 on a Windows platform using the default directories suggested by the installation program. (e.g., C:\Program Files\WebSphere\AppServer.) Customer installs Fix Pack 1 some time later. After a successful installation of Fix Pack 1, customer attempts to start the service, "IBM WebSphere Application Server V5 - server1". Windows will throw an error containing the phrase "Error 193: ... is not a valid Win32 application". Alternatively, it may report: "Could not start the ... service on Local Computer Error 193: 0xc1"Local fix Workaround: Delete the "C:\Program" file erroneously generated during the Fix Pack 1 install. Fix Pack 1 makes various calls to external programs during its updates. During one of the WebSphere MQ updates, the installer calls the amqicsdn.exe program. This program is directed to generate a log file named "MQCSDLog.txt". This file should be generated in the <WAS_HOME>/properties/version/log directory, but it is not. Instead, the path to this file is truncated at the first space. If the file is "C:\Program Files\...\MQCSDLog.txt", the file name is truncated to "C:\Program". The MQCSDLog.txt file content is dumped into this file. This problem can also be prevented if the registry key containing the "Image Path" to the executable file for the service is generated correctly. The path to the executable should be surrounded by quotes. Currently, the WAS50 installer does not do this.Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users running * * on the Windows platform whose machine has a * * problem with spaces in the path to a * * service's executable. * **************************************************************** * PROBLEM DESCRIPTION: Error 193: ... is not a valid Win32 * * application when starting the WAS * * service. * **************************************************************** * RECOMMENDATION: * **************************************************************** When starting the WAS service the following error message appears: "Error 193: ... is not a valid Win32 application" As a result the service does not start.Problem conclusion To avoid this problem, quotes have been added around the service's ImagePath.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
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ74134
IBM Group: Software Group
Modified date: Jun 25, 2003
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.