Hi ! After upgrading my installations from 5.3.1 to 5.4.7 the visualcron service doesn't start anymore

I'm receiving the following

Log Name: System
Source: Service Control Manager
Date: 03.12.2009 17:38:51
Event ID: 7000
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: AIDDE2LL8077098.international.intra.abbott.com
Description:
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.

Any help is highly appreciated.

Thanks a lot.

Karsten

Could you send the log file (log_serverDATE.txt) to support@visualcron.com

---

Hi,

i have sent you the logfile.
The problem is that nothing is written to file after the upgrade.😊

Regards,
Karsten

Please send server_startup.txt and also check in the event log for any errors.

---

We've had similar issues before (not while upgrading though) and discovered that the service wouldn't start is the VC tray was still running.

Stopped the tray and the service restarted.

I just upgraded from 5.3.1 to 5.4.7 without issue

Mike,

when you say "stop the tray" do you mean just exit (kill) it? And then start the service again?

We've had similar issues before (not while upgrading though) and discovered that the service wouldn't start is the VC tray was still running.

Stopped the tray and the service restarted.

I just upgraded from 5.3.1 to 5.4.7 without issue

---

Yes - when we were having the issues detailed in the long posts, we'd try to top and restart the service. The VC service woud stop but would not restart. Killing the tray service allowed the VC service to start.

I'll put in a feature request to make the tray installation optional.

Mike,

when you say "stop the tray" do you mean just exit (kill) it? And then start the service again?

We've had similar issues before (not while upgrading though) and discovered that the service wouldn't start is the VC tray was still running.

Stopped the tray and the service restarted.

I just upgraded from 5.3.1 to 5.4.7 without issue

We have received reports from another customer. The problem is related to .NET 2.0 SP2 install. This update requires a reboot - and VisualCron is dependent on it.

---