| Product(s): | APM Implementation and Performance Management | |
| Version(s): | 7.1.x and below | |
| Environment: | APM Application Service | |
| Area: | N/A | |
| Subarea: | N\A | |
Problem
The APM application service will not automatically restart after the server has been rebooted. We have to manually start the service.
Solution
Some customers experience problems with the service not restarting after a server reboot. It’s not a problem with the application. It seems to be a timing issue, perhaps with starting the database server. We have implemented a change in the 7.2 version, to delay starting as service until the database server is active.
Without the 7.2 change, a work-around is required.
When the service is created, the default is set to start automatically. The “Startup type” is set to Automatic. Try setting it to Automatic (Delayed Start). The delay is 2 minutes after the server has started after rebooting, which is controlled by the AutoStartDelay registry value in HKLM\SYSTEM\CurrentControlSet\Control.
In necessary, you may also want to experiment with the “Restart service after” setting on the Recovery page. The default is 1 minute. However, if the Automatic (Delayed Start) setting doesn’t help, and you don’t want to increase its time to more than 2 minutes, changing this value from 1 minute to 2 minutes, may provide the additional time required.
See Also
N/A.
| Original Author: | Roy Suthers | |