Overview
The error message Failed on Service is logged when the Start & Stop Service Action encounters an error while trying to start, stop, pause, resume, or restart a service / driver.
The error message not only shows the failure that has occurred, but it also provides additional details and context through the inclusion of a specific Windows error code. This additional information can aid in troubleshooting and resolving the issue at hand.
Event examples
See some examples of the Failed on Service Event messages:
- Task "Backup CRM" Action "Start & Stop Service" failed on "CRMdb Service". The system cannot find the file specified. [os:2; aw:3]
- Action "Start & Stop Service" failed on "Hyper-V Service". Access is denied. [os:5; aw:3]
- Failed on "IIS Admin Service". The service cannot accept control messages at this time. [os:1061; aw:4]
- Failed on "Task Scheduler Service". The requested control is not valid for this service. [os:1052; aw:5]
- Failed on "ERP Service". The dependency service does not exist or has been marked for deletion. [os:1075; aw:3]
- Failed on "OraDB23 Service". The dependency service or group failed to start. [os:1068; aw:3]
- A stop control has been sent to a service that other running services are dependent on. [os:1051; aw:4]
- The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. [os:1058; aw:3]
- The service has not been started. [os:1062; aw:5]
Syntax reminder
The Start & Stop Service Action may fail with a "syntax" error if no input is provided (an empty string) or some special characters (symbols that are not allowed in service names) are used. See an actual error message:
- The filename, directory name, or volume label syntax is incorrect. [os:123]
Notes
The System cannot find the file specified (os:2) may indicate that the service path, executable, or its arguments are misspelled during the service installation, or incorrect symbol escaping is used.
The Dependency service or group failed to start (os:1068) usually means that one or more service dependencies are disabled and can not be started. Enable the dependent service to fix the issue.
The error A stop control has been sent to a service that other running services are dependent on (os:1051) usually means if you are trying to stop a service with dependencies, and the dependent services are not stopped. Using the activity Stop service + linked services will fix this error.
The Service has not been started (os:1062) may indicate that during the service startup process some other app or user has stopped the service.
Marked?
An error the specified service has been marked for deletion may be fixed by closing the following apps…
- Task Manager.
- Service Control Panel.
- Windows Event Viewer.
- Microsoft Management Console · MMC.
- Sysinternals Process Explorer.
- Any other app that displays Windows services.
Need assistance?
If you have any questions, please do not hesitate to contact our support team.