| Previous | Next |
| ERROR_CANNOT_DETECT_PROCESS_ABORT | ERROR_SERVICE_NOT_IN_EXE |
ERROR_NO_RECOVERY_PROGRAM
The service has no recovery command configured
SCM failure actions can restart a service, reboot the computer, run a command, or take no action. SERVICE_FAILURE_ACTIONS contains an optional command string used when an action is SC_ACTION_RUN_COMMAND. ERROR_NO_RECOVERY_PROGRAM identifies a recovery path that expects a program but has no command configured.
Query SERVICE_CONFIG_FAILURE_ACTIONS and inspect the action array together with lpCommand. Do not assume that the service executable itself is the recovery program: run-command recovery is an explicit configuration field. If the desired policy is restart-service, configure SC_ACTION_RESTART instead of inventing a helper command. If a recovery program is required, store a fully controlled executable path and review its security context because SCM launches the configured recovery action as part of service failure handling.
What to inspect
- Query failure actions and identify every SC_ACTION_RUN_COMMAND entry.
- Verify lpCommand is configured for command actions.
- Use restart actions directly when no external recovery program is needed.
References
- Microsoft: Service Failure Actions
- Microsoft: SERVICE_FAILURE_ACTIONS
- Microsoft: ChangeServiceConfig2W
Looking for a different code? Search another status or error code.