Fix (APAR): PQ72390 Status: Fix Release: 5.0.1,5.0.0 Operating System: Windows (General) Supersedes Fixes: PQ72196 CMVC Defect: PQ72390 Byte size of APAR: 23079 Date: 2003-04-21 Abstract: Windows 1053 service timeout error Description/symptom of problem: Error: 1. Microsoft Management Console: Could not stop the IBM WebSphere Application Server V5 -server1 service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion. 2. The Windows event log shows: Event ID: 7011 Description: Timeout (30000 milliseconds) waiting for a transaction response from the IBMWAS5Service - server1 service. Directions to apply fix: NOTE: YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX. The Fix Installer can be downloaded from the following link: http://www-3.ibm.com/software/webservers/appserv/support/index.html 1) Create temporary "fix" directory to store the jar file: UNIX: /tmp/WebSphere/fix Windows: c:\temp\WebSphere\fix 2) Copy jar file to the directory 3) Shutdown WebSphere 4) Follow the Fix installation instructions that are packaged with the Fix Installer on how to install the Fix. 5) Restart WebSphere 6) The temp directory may be removed. Directions to remove fix: NOTE: FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED. DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED. YOU MAY REAPPLY ANY REMOVED FIX. Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied. 1) Shutdown WebSphere 2) Follow the instructions that are packaged with the Fix Installer on how to uninstall the Fix. 3) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere 2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Additional Information: NOTE: If the server takes over a minute to complete its start sequence, the service will go to the "started" state with the stop functionality disabled to avoid the 1053 error. After the server's start sequence is successfully completed the service will enable the stop functionality upon a refresh of the services dialog.