PK16872: PROBLEMS WITH JAPANESE MACHINES AND WINDOWS SERVICES.

 Fixes are available

5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Solaris
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Windows
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Windows
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for AIX
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for HP-UX
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for AIX
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Linux
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for HP-UX
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Linux
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for HP-UX
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Solaris
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Windows
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for AIX
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Solaris
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Windows
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for HP-UX
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for AIX
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Linux
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Linux
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Solaris



APAR status
Closed as program error.

Error description
Customer using version 5.0.2.13 Base.

Error occurs in the event log.when the user starts/stop
application server (server1) by service of windows2003.
status of the server disappears just after changing the status
of application server to start. However the application works
fine
and it has a pid file.and when they try to stop the application
by service of windows20003 The given beloow error occurs in the
windows application event
logs.

on Windows application event logs shows the error
-----------------------
Event ID: 109
Description:
The description for for Event ID ( 109 )  in source
(IBMWAS5Service - server1 )
cannot be found. The local computer may not have the necessary
registry information or message DLL files to display messages
from a local computer.
-------------------
Local fix
n.a
Problem summary
****************************************************************
* USERS AFFECTED: WebSpher Application Server users who run    *
*                 WebSphere Application Server as a service    *
*                 and use certain translations (japanese       *
*                 reported) that add extra characters to the   *
*                 end of the log file Microsoft Windows        *
*                 services parses for the process ID.          *
****************************************************************
* PROBLEM DESCRIPTION: Error occurs in the event log.when      *
*                      you start or stop application           *
*                      server (server1) by service on          *
*                      Microsoft Windows2003.                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Error occurs in the event log.when you start or stop
application server (server1) by service. The status of the
server disappears just after changing the status of application
server to start. However the application works fine and it has
a pid file. When you try to stop the application by service of
Microsoft Windows20003. The following error occurs in the
application event logs:

 -----------------------
 Event ID: 109
 Description:
 The description for for Event ID ( 109 ) in source
(IBMWAS5Service - server1 ) cannot be found. The local computer
may not have the necessary registry information or message DLL
files to display messages from a local computer.
-------------------
Problem conclusion
More robust parsing code was added.

The fix for this APAR is currently targeted for inclusion
in cumulative fixes 5.02.16 and 5.1.1.9.
Please refer to the recommended updates page for delivery
information:

http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix Comments
APAR information
APAR number PK16872
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2005-12-15
Closed date 2006-01-10
Last modified date 2006-01-10

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
WASERVIC          

Publications Referenced

Fix information
Fixed component name WAS BASE 5.0
Fixed component ID 5630A3600

Applicable component levels
R003 PSN    UP
R00A PSN    UP
R00H PSN    UP
R00I PSN    UP
R00P PSN    UP
R00S PSN    UP
R00W PSY    UP
R103 PSN    UP
R10A PSN    UP
R10H PSN    UP
R10I PSN    UP
R10P PSN    UP
R10S PSN    UP
R10W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PK16872
IBM Group: Software Group
Modified date: Jan 10, 2006