Service not starting after reboot (Full Version)

All Forums >> [Networking & Security] >> GFI EventsManager



Message

mblinde -> Service not starting after reboot (17.Aug.2009 12:59:33 PM)

I'm experiencing an issue after every reboot where the Events Manager service is not starting in a timely manor ("That time frame is deemed by Microsoft Windows Server 2008 64 bit"). After the server is up and running though I can start the service after 2 trys every time. The recovery options are set to restart the service if it stops at least twice but by the 3rd attempt it is set to run a VBScript to notify us that the service has failed to start. This is running on a 2008 64 bit server running in a VMware environment with 4 gigs of ram. The server is strictly running only LANguard and Events manager. The database is housed on 2003 server running SQL 2005. That database server is sitting at a very low CPU utilization with plenty of resource to spare.

I'd like to know if there are any other EventsManager admins runnning into the same issue or if there is something that can be done to help resolve this.



DrewE -> RE: Service not starting after reboot (17.Aug.2009 1:38:07 PM)

Many users report that method 3 of these steps work: http://support.microsoft.com/kb/941990
This is increasing the Timeout settings so the windows service will try longer to start before giving up.
Also, does this machine have an Internet connection?



mblinde -> RE: Service not starting after reboot (17.Aug.2009 2:35:32 PM)

I have made the modifications as shown in the article and will try a reboot early tomorrow morning. If the problem persits I'll respond back here in this thread. I've opted to give it more time then the article gave so we'll see how it pans out.



candlewood -> RE: Service not starting after reboot (16.Dec.2009 8:34:21 AM)

Im having the same problem, is a internet connection required?  I have a fully stand alone network which cannot touch the internet.



DrewE -> RE: Service not starting after reboot (16.Dec.2009 9:16:16 AM)

Having no Internet connection could be the cause of this, as the service tries to verify its digital signature expiration before starting. Without an Internet connection this process can take longer than the default 30 seconds Windows allows. Try running the steps above (method 3 of KB/941990) and let us know what happens.



Page: [1]