> This is an interesting question about what the appropriate behavior > should be, though at a minimum you should get a decent error.
I agree with that, there should be a messagebox popping up saying that the event log is full. What happens now if the event log is full is: The service just hangs in the services panel, displaying "starting service" for ever. No clue whatsoever what's the problem. Because we recently changed a detail in the implementation of the startup procedure of our service, we of course thought it is a problem with our code. Since it is not possible to actually debug the start of a service, we had a hard time finding out what the actual problem was... luckily it was only on a test system, otherwise the whole company would have been down for 1/2 day!! Urs You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
