On a brand new Windows 2008 server R2 I have experienced that the VC service did not start up after a reboot.

The Event log says

The VisualCron service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

A timeout was reached (120000 milliseconds) while waiting for the VisualCron service to connect.

Where do i find the reason?

Could you please send server_startup.txt and log_serverDATE.txt?

Also, did it start if you tried it manually later?

---

It did start up when started manually. It seems like server_startup.txt has been overwritten.

Can I send the files by mail?

Yes, please send it to support@visualcron.com. Which time did you reboot?

---

It happend again. I have send the logfiles + timestamp.

I think it has something to do with a "System Startup" trigger which starts a job. This could take 1-2 minutes

By the way I'm running v 5.5.3

Thanks for the info. While we are thinking of how to handle this you could do a temporary fix which increases timeout.

Open registry editory and go to Local machine->SYSTEM\CurrentControlSet\Control

and set:

ServicesPipeTimeout

This is a value in milliseconds. Please let us know if that fixes the problem. Then we can work with a better fix.

---

Thanks, this fixed the problem. Of course I like a fix that doesn't start the scheduled jobs in the service startup event (Microsoft recommendations)

Stig

Will this be fixed?

Yes, it will. We have this on our to do list for next version.

---