Blueprint TaskMaster service fails to start on reboot
- 29 Feb 2024
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
Blueprint TaskMaster service fails to start on reboot
- Updated on 29 Feb 2024
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
The Blueprint TaskMaster service fails to start after a reboot, causing the following error to be written to the Event Log:
The Pharos Systems TaskMaster service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
On a reboot, the .NET Framework performs a number of checks before starting the Blueprint TaskMaster service. On a slow machine, this can cause a timeout error before the TaskMaster service is started.
Manually start the Pharos Systems TaskMaster service from the Windows Services manager (Administrative Tools > Services).
Was this article helpful?