APAR status
Closed as program error.
Error description
Windows Services (WASService.exe) does not start wsinstance
created nodes. You will be able to create and remove new
Services for the wsinstance node, but cannot start the service.
When you start the service it will look at the original node
to start the service for that server if it exist.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users who *
* create alternate instances of WebSphere *
* Applicaition Server with wsinstance . *
****************************************************************
* PROBLEM DESCRIPTION: The Windows services does not start *
* wsinstance created nodes. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The user will be able to create and remove new services for the
wsinstance node, but cannot start the service. This will
produce a Windows Error 100.
When the service is started, it will look at the original node
to start the service for that server if it exists.
Problem conclusion
A parameter was added to the code to specify the location of the
setupCMD.bat. This will point the enviroment to the location of
the created instance.
Temporary fix
Added a parameter to specify the location of the setupCMD.bat
script.
Comments
APAR information |
APAR number |
PQ75427 |
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 |
2003-06-19 |
Closed date |
2003-07-31 |
Last modified date |
2003-07-31 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSN |
UP |
R00A PSN |
UP |
R00H PSN |
UP |
R00I PSN |
UP |
R00P PSN |
UP |
R00S PSN |
UP |
R00W PSY |
UP |
|