We are running WebSphere 9.0.5.6 on windows 2019 and having trouble starting the service with WASService. When we try to start the server with WASService, we get error code 87. However we can start the server with startServer.bat just fine. Below is the error we are encountering:

…

…

Mar08 15:27:08 P:7880 T:8604 - stdout: ADMU0128I: Starting tool with

the AppSrv01 profile

Mar08 15:27:08 P:7880 T:8604 - stdout: ADMU3100I: Reading configuration

for server: nkam_ip-172-20-128-1Node01

Mar08 15:27:08 P:7880 T:8604 - stdout: ADMU3200I: Server launched.

Waiting for initialization status.

Mar08 15:27:08 P:7880 T:8604 - stdout: ADMU3000I: Server

nkam_ip-172-20-128-1Node01 open for e-business; process id is

Mar08 15:27:08 P:7880 T:8604 - parsePidFromStdOut[2328]: Found started

message (ADMU3000I)

Mar08 15:27:08 P:7880 T:8604 - parsePidFromStdOut[2352]: extracted pid

() from message

Mar08 15:27:08 P:7880 T:8604 - WASServiceMain[2691]: Attaching to

process(0) using OS OpenProcess command.

Mar08 15:27:08 P:7880 T:8604 - WASServiceMain[2769]: OpenProcess failed

for pid 0. Return value (87): Meaning: The parameter is incorrect.

Mar08 15:27:08 P:7880 T:8604 - WASServiceMain[2771]: setting service

state to STOPPED with exit code indicating OS error code.

Mar08 15:27:08 P:7880 T:8604 - WASServiceMain[2782]: finished. Could

not connect to process.

Mar08 15:27:08 P:7880 T:8668 - main[1780]: StartServiceDispatcher --

WASService exiting; service no longer running.

Mar08 15:27:08 P:7880 T:8668 - main[1791]: finished

There are 3 known issues related to wasservice in WebSphere

version 9.0.5.6 and this is one of the errors resulting from WebSphere

service code being modified to extract the pid from multiple lines and from any

position within the message.

See this APAR: https://www.ibm.com/support/pages/apar/PH32837

The solution is to provided in 9.0.5.7. Upgrading to this version should resolve the issue.

Remove and add the service after the upgrade.

9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7:

https://www.ibm.com/support/pages/node/6427015

Other WASService related known issues in 9.0.5.6:

1) PH30529: 'WASSERVICE ENTERED THE RUNNING STATE.' MSG IS SOMETIMES RECORDED TWICE.

https://www.ibm.com/support/pages/apar/PH30529

2) PH32837:WEBSPHERE WINDOWS SERVICE DOES NOT INDICATED STARTED ON GERMAN, DUTCH AND JAPANESE ENVIRONMENTS.

https://www.ibm.com/support/pages/apar/PH32837

3) PH33299: WEBSPHERE APPLICATION SERVER WINDOWS SERVICE CONTINUES TO RUN WHEN WEBSPHERE ENDS UNEXPECTEDLY

https://www.ibm.com/support/pages/apar/PH33299