CODEWITHSUNDEEP
vb.netwindows-services
Martin
Martin

Reputation: 1213

Failing a Windows Service with an exit code

I want my service to be able to be restarted remotely (by a TCP client which is not part of this question). I configured the service to restart on failure on the Recovery tab for my service. In my code I set the ServiceBase.ExitCode to a non-zero number, say 1. I did not use Environment.Exit to stop the service because it isn't necessary to terminate the process. When I test my service it stops correctly and the Windows System Log reports that my service has stopped with an error. It also names the error. But my service does not restart! When I instead use Environment.Exit(1) the Windows System Log reports that my service has stopped unexpectedly without naming the error. It then does restart the service as if it has failed (like it should).

My question is, why doesn't the service restart with just a non-zero exitcode? The service stops with an error but that isn't failing? Is Environment.Exit the only way to properly trigger a service restart on failure? I liked using the ExitCode better because the System Log is cleaner and more accurate that way.

Upvotes: 1

Views: 1355

Answers (1)

CoreTech
CoreTech

Reputation: 2433

Did you check the "Enable actions for stops with errors" checkbox on the Recovery tab?

enter image description here

From the technical documentation, the service's exit code is only consulted if that option is checked.

Upvotes: 2

Related Questions