The name-of-your services on Local Computer started and stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service.
I had fun with this one for a bit. Developing Windows Service is one of those "I rarely do this" activities. So when I got one of these errors when I start my service, immediately I switch into "Ah I must have forgotten something" mode.
- May be the process started and didn't do anything and finished
- May be the timer didn't go off
- Perhaps I need to spawn a thread to listen / sleep
I couldn't attach a debugger to the service given that it doesn't stay running. So that limited my options a bit.
Turns out, the "informational message" was pretty misleading, I had the following in my event log.
Service cannot be started. System.NullReferenceException: Object reference not set to an instance of an object.
at MyService.MyService.OnStart(String args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)
Fixed that error, and the service starts successfully.