Websphere profile startup error - best way to fix?
![](http://jazz.net/_images/myphoto/8210b2ede10f6bb02484cea99c6f9b99.jpg)
Our environment is CLM V4.0.6, Applications are distributed across servers with QM and RM on different WAS profiles on the same VM. Yesterday the QM application became unresponsive. When the customer tried to restart it, it exited quickly with this error message in the Windows system log:
The IBM WebSphere Application Server V8.0 - <NodeName> service terminated with service specific error %%134219720
I've seen situations like this before and I fix it by setting all WAS profiles on the server to Manual start, reboot the server and then start the WAS profiles 1 at a time.
This has resolved the sitaution each time but I'm curious if anyone else has seen this and are there any better ways to resolve it that don't require restarting the server?
Thanks,
Fran
2 answers
![](http://jazz.net/_images/myphoto/8210b2ede10f6bb02484cea99c6f9b99.jpg)
If you are not familiar with the WASService.exe command, you may try the WASServiceCmd.exe which is supposed to be more user-friendly.
http://www-01.ibm.com/support/docview.wss?uid=swg21397335