How To Verify Windows Service Attempted To Start

Owned by Knowledge Assistant
Last updated: Nov 11, 2024
1 min read
Description of Issue

A service is set to Automatic or Automatic (Delayed Start), but did not start on a reboot. How can we verify that the service attempted to start up?

Context

  • Windows Services

  • Event Viewer

  • Server Administration

  • TSM OnPrem

  • TSM SaaS

Cause

Informational

Resolution

  1. Connect to the server that has the service(s) in question not starting

  2. Open Event Viewer

  3. Expand Windows Logs

  4. Right click System > Filter Current Log...

  5. On Logged, select Custom range ...

    1. On From, change First Event to Event On

      1. Set the date to the last reboot time: How to Find Last Reboot Time

    2. On To, change Last Event to Event On

    3. Click OK

  6. On Event level, select Error and Critical

  7. Click OK

  8. Errors from the Service Control Manager source should appear shortly after the server reboot time.

    1. If you receive at least one of the errors below, follow Window Service Timed Out - How to Prevent.

      1. For instance: A timeout was reached (XXXXX milliseconds) while waiting for the XXXXX service to connect.

      2. For instance: The XXXXX service failed to start due to the following error: 
        The service did not respond to the start or control request in a timely fashion.  

    2. If you receive the error below, follow Windows Service Terminated Unexpectedly - How To Prevent

      • The XXXXX service terminated unexpectedly. It has done this XX time(s).

Additional Information

For further assistance or additional errors not listed, please contact Tyler Systems Management Support or log a case via the Online Support Client Portal