A Windows Service is Down. Now What?
It doesn't matter if it's SQL Server, IIS, a background agent, or a custom app — when a Windows service goes down, the investigation is always the same five moves.
- Confirm service status and start type before taking action
- Map service transitions using Event ID 7036 in Windows logs
- Read application's own logs for reason service stopped
