PQ47674: WEBSPHERE ERROR IN WINDOWSNT EVENTLOG HAS NO DESCRIPTION


APAR

APAR status
Closed as program error.

Error description
When you go to Windows Start button -> Admin Tools ->
Event Viewer -> Application Log there are many WebSphere
information events, but NO decription for the events when you
open them.
The customer consulted with Windows support and WebSphere does
not follow the Windows Application guidelines for event
reporting.
The application which wants to write log in event log should
install the EventMessageFile and register it in registory,
then pass the corresponding event ID to Windows system.
But WebSphere does not install the dll in Windows registory
nor pass the event ID (all the WebSphere event has event ID (0))
The install should create a registry entry to keep these types
of messages from appearing in the Event Viewer.  The registry
entry needs to be in:
 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog
 \Application\WebSphere
"EventMessageFile"=""
"TypesSupported"=dword:00000007
The value for EventMessageFile will be the WebSphere file
containing the messages needed to satisfy the Event Viewer.
entry needs to be in:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\WebSphere"EventMessageFile"="""TypesSupported"=dword:00000007The value for EventMessageFile will be the WebSphere filecontaining the messages needed to satisfy the Event Viewer.
Local fix
Problem summary
The registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
\Services\EventLog\Application\WebSphere
must be created during installation and it must
have the following subkeys and values:
type String key - "EventMessageFile" value - $(WAS_HOME)\bin
                   \wasmessage.dll
type DWORD key - "TypesSupported" value - 0x07
.
Finally "wasmessage.dll" must installed in the location
$(WAS_HOME)\bin
have the following subkeys and values:type String key - "EventMessageFile" value - $(WAS_HOME)\bin\wasmessage.dlltype DWORD key - "TypesSupported" value - 0x07.Finally "wasmessage.dll" must installed in the location$(WAS_HOME)\bin
Problem conclusion
com/ibm/ejs/sm/util/process/win32service/wasmessage.mc
com/ibm/ejs/sm/util/process/win32service/eventlog.h
com/ibm/ejs/sm/util/process/win32service/wasmessage.c
com/ibm/ejs/sm/util/process/win32service/TrMakeFile
com/ibm/ejs/sm/util/process/win32service/service.c
com/ibm/ejs/sm/util/process/win32service/eventlog.c
com/ibm/ejs/sm/util/process/win32service/bootfile.c
Temporary fix
Comments
APAR information
APAR numberPQ47674
Reported component nameWAS STANDARD NT
Reported component ID5648C8301
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2001-04-08
Closed date2001-05-01
Last modified date2001-05-01

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:


Modules/Macros
EJS
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information
Fixed component nameWAS STANDARD NT
Fixed component ID5648C8301

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ47674
IBM Group: Software Group
Modified date: 2001-05-01