Don't know whether I'd call it a bug or not... If the Start call doesn't come back correctly, you get the symptoms you describe. Services write a 'Started' message in the log. If the log file is full, the Start call doesn't return correctly.
If I were in MS's position, I'd argue that it was not a bug in the Service or SCM but a problem with the local environment - and that that problem is the correct thing to fix. I might even agree with them in this case. (This problem has bitten me too, recently. I now make it a habit to check all logs sizes and over-write behaviour.) Simon -----Original Message----- From: Dave Adair [mailto:[EMAIL PROTECTED]] Sent: Tue 15 October 2002 13:56 To: [EMAIL PROTECTED] Subject: [ADVANCED-DOTNET] .NET Windows Services won't start if event log is full? I've read several posts around the net from people saying that their Windows Services written in .NET don't start correctly when the event log is full. The service continually shows as "Starting" in the services manager. I am now seeing this same behaviour since the event log on my test server become full. I set the log to "overwrite events as needed" and the service is starting correctly now. Can anyone confirm that this is a bug in .NET? I haven't seen anything official from Microsoft yet. I'm using .NET SP2. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
