Windows Service
-
Hi, We have a Windows Service, written in VB.NET. This service is set to start Automatically on machine start. Authentication/log on parameters are included while setting the Service. However, we now notice that the service does not start on reboot, returning a Service Failed to log on error. Starting the service manually works without problem. Server: Win 2003, .NET 2.0 Any help towards a solution would be most appreciated. Regards, RB
-
Hi, We have a Windows Service, written in VB.NET. This service is set to start Automatically on machine start. Authentication/log on parameters are included while setting the Service. However, we now notice that the service does not start on reboot, returning a Service Failed to log on error. Starting the service manually works without problem. Server: Win 2003, .NET 2.0 Any help towards a solution would be most appreciated. Regards, RB
-
Hi, We have a Windows Service, written in VB.NET. This service is set to start Automatically on machine start. Authentication/log on parameters are included while setting the Service. However, we now notice that the service does not start on reboot, returning a Service Failed to log on error. Starting the service manually works without problem. Server: Win 2003, .NET 2.0 Any help towards a solution would be most appreciated. Regards, RB
Have you tried setting the service to retry it's startup if it fails? You can set it to retry after so many minutes after the 1st and 2nd failed attempts.
Steve Jowett ------------------------- Real programmers don't comment their code. If it was hard to write, it should be hard to read.
-
Hi, We have a Windows Service, written in VB.NET. This service is set to start Automatically on machine start. Authentication/log on parameters are included while setting the Service. However, we now notice that the service does not start on reboot, returning a Service Failed to log on error. Starting the service manually works without problem. Server: Win 2003, .NET 2.0 Any help towards a solution would be most appreciated. Regards, RB
You may have some other services or resources on the system that are not ready when the Windows service is started, for example SQL server usually will usually not be ready when your Windows service started. You should trap the exception to debug what is causing the failure, ie using AppDomain.CurrentDomain.UnhandledException or Application.ThreadException (can't remember which one for services, don't have the code with me now).