The Start & Stop Service Action allows for the automation of all Windows service status changes, including starting, stopping, pausing, resuming, and restarting services.
Create no-code workflows with a few easy mouse clicks to intelligently start, stop, or restart a service and all its dependent services. Automation Workshop detects and manages dependent services fully automatically.
|Service||Select a service to manage. Choose it from the list, or type a service name, or use a variable. Kernel and filesystem drivers are also supported:|
|Service info||Shows the current status of a service, for example:|
The tooltip displays extended service information in real-time.
|Activity||Choose a service management activity:|
|Parameters||It is possible to provide startup parameters, if the Start service activity is selected. Those parameters are passed to the |
|Reason||An optional service stopping reason that is logged in the Event Log and can later be queried or observed in the Event Viewer · Preview|
|Major||Provide an optional major service stopping reason:|
|Details||An optional minor service stopping reason:|
|Comment||An optional comment for the stop service operation. The maximum length or the comment is 127 characters.|
|Variable Wizard||Use dynamic data input—substitute a parameter from a file, web, connected Trigger, other Actions, date and time presets, etc.|
- The start service activity automatically starts all dependencies (linked services), however, this is not reflected in the service.log file. On the other hand, the stop service activity logs all stopped dependencies, if any.
- The pause and resume activities are only supported if the selected service is specifically designed to support them.
- When working with kernel and filesystem drivers, consult the documentation of the particular driver of its supported activities.
- It's important to note that service management is a complex task, however, Automation Workshop allows you to create automated workflows without writing complex scripts or custom apps. It's always recommended to test the service automation in a non-production environment before implementing it in production.
- By default, Windows Servers have the ability to log the stopping reasons when services are stopped, while this feature is not enabled on Windows workstations.
- The same stopping reason is also logged for all dependencies (linked services) that are stopped during the specific service stop procedure.
When stopping a Windows service with a reason, it is logged in the Windows Event Log under the System logs category. The default source of such events is Service Control Manager and the events are logged under 7042 event identifier.
The Event Properties shows additional and detailed information about the logged stop reason. The textual part shows a service display name and your specified stopping reason in a hexadecimal and textual representation. Your provided comment is also displayed here.
Additional details such as a computer name and the exact date and time of the event is also displayed there. Usually, it is enough to select a standard service stop reason from the system predefined values, however, the comment field allows you passing any custom text that can be generated automatically at runtime using Variable Wizard.
If you have any questions, please do not hesitate to contact our support team.