I have seen this before and the culprit turned out to be a malformed string in the .config file I was using for service parameters.
The way I found this was to pull the service code into a winForms app, add a startup time and then call the you on start code. I tend to use a service start timer, when testing, this is set to 30 seconds. This gives enough time to get the debugger hooked up. Any, run the code inside a winForm, the system will then be able to throw the exception and you will get a message as to what the problem is. Maddening problem to be sure, it burnt the better part of six hours for me before I finally found it. HTH Doug Nelson -----Original Message----- From: Van Vreede, Douglas P [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 10, 2004 11:32 AM To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] Service stays in "starting" status first time its started I have not seen this problem either and my service does not call base.OnStart. Decompiling ServiceBase.OnStart, shows an empty virtual method. There must be some other explanation. Doug > Just looked at my code and I call base.OnStart() at > the end of my OnStart(). I imagine that the base > class calls SetServiceStatus() to tell the OS that > your service is running. =================================== This list is hosted by DevelopMentor(r) http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
