Fix (APAR):  PQ96461

Status:  Fix

Release:  5.0.2.8,5.0.2.7,5.0.2.6,5.0.2.5,5.0.2.4,5.0.2.3,5.0.2.2,5.0.2.1,5.0.2,5.0.1,5.0.0

Operating System:  Windows

Supersedes Fixes:  

CMVC Defect:  PQ96461

Byte size of APAR:  26872

Date: 2004-11-03

Abstract:  Error 100 when trying to start service through service GUI

Description/symptom of problem:  For services that were created with no LogRoot parameter specified, 
it is possible in some environments that the service will be unable
to start.  ( Japanese is one known environment this can happen on ).
For pre CF6 systems, this may be due to problems parsing the server's
pid from the stdout logs.  On post CF6 systems, there were problems
with how the LogRoot path was defaulted and built for services 
that had no LogRoot explicitly set.  

   This fix takes care of both classes of problem.  Many different
things can cause the "Error 100" symptom, so here is a quick way
to tell if this problem is the cause of an Error 100:  after
verifying no LogRoot parameter was set when the service was created,
re-create the service with a LogRoot specified.  If the service
starts after this is done, then PQ96461 is the problem.

    ( Note for above test: the LogRoot should be set to the log directory for the server, which 
would be "WAS_ROOT\logs\<ServerName>" for customers who haven't
modified the directory structure of their installs )

Directions to apply fix:  NOTE:  YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
       The Fix Installer can be downloaded from the following link:
       http://www-3.ibm.com/software/webservers/appserv/support/index.html

1) Create temporary "fix" directory to store the jar file:
          Windows: c:\temp\WebSphere\fix

2) Copy jar file to the directory

3) Shutdown WebSphere

4) Follow the Fix installation instructions that are packaged with the Fix Installer on how to install the Fix.

5) Restart WebSphere

6) The temp directory may be removed.

Directions to remove fix:  NOTE:  FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT REMOVE A FIX UNLESS
     ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED FIX.

Example:  If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be
          removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.


1) Shutdown WebSphere

2) Follow the instructions that are packaged with the Fix Installer on how to uninstall the Fix.

3) Restart WebSphere

Directions to re-apply fix:  1) Shutdown WebSphere

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere

Additional Information:  Recreating the service with the LogRoot specified is a valid workaround for customers unable to apply this fix.