| Product(s): | APM Implementation and Performance Management | ||
| Version(s): | All | ||
| Environment: | All | ||
| Area: | Server Management |
When applying a OS patch or needing to reboot a Server Machine running multiple (3+) APM Server Service, sometimes not all of the APM Services come back up. They can subsequently be started without problem.
Changing the Service startup timeout in Windows is a fix for this problem.
"The Microsoft Windows Service Control Manager controls the state (i.e., started, stopped, paused, etc.) of all installed Windows services. By default, the Service Control Manager will wait 30,000 milliseconds (30 seconds) for a service to respond. However, certain configurations, technical restrictions, or performance issues may result in the service taking longer than 30 seconds to start and report ready to the Service Control Manager.By editing or creating the ServicesPipeTimeout DWORD value, the Service Control Manager timeout period can be overridden, thereby giving the service more time to start up and report ready to the Service.