Geek Answers Handbook

Determining why Windows .net service is not starting

I am trying to determine why the .NET service, which I can successfully install on a large number of machines, does not start on specific machines.

When a service starts on these machines, the service stops immediately, so my assumption is that users do not have sufficient privileges to install the service, or there is a problem with the service; however, both of these conditions are false (the service is running and they have sufficient privileges).

What steps should I take to determine the reason why the service will not start?

Edit

I realized what was wrong, thanks to some of the answers provided, see my answer for what was my decision.

+5
source share
2 answers

So I figured it out thanks to viewing the event log from @Matthew Steeples and @Ben M.

The problem was that the service writes to the event log at startup when it connects to the server; however, this machine event log was full, so when the service tried to write to the event log, it failed, forcing it to throw an exception that again could not be written to the full event log.

So, if you are writing an event log, make sure it is empty or you are handling an exception!

+3
source

The application event log should contain information about any exceptions. Net that occurred during the start of the service. This can help diagnose the problem.

( ) debugview Sysinternals, , .

+6

More articles:


All Articles