A Windows service will remain shut down or return an error immediately after the attempt to boot.
Probable causes
- incorrect service account or password.
- addiction stopped
- port already used.
- missing configuration or binary file.
Verifications.
- Read the exact error. — Consult Services and the Observer of Events.
- Check account. — Control the log-in account, lock-up and log-on-as-service rights.
- Control addictions. – List the required services and their condition.
- Check ports. – If the service listens to a port, seek conflict.
Commands
sc query nomservice
Get-Service nomservice
Get-WinEvent -LogName System -MaxEvents 50
Solutions.
- correct service account.
- start or repair dependencies.
- correct port conflict.
- restore the expected configuration or binary.
When to climb?
Escalader if the critical service fails after an update, migration or application modification requiring a publisher.
See also:. Event ID 7000..