Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


devonway
2012-04-10T22:53:56Z
Two nights ago I realized that our VC 5.7.4 Server wasn't starting any new jobs even though the server was started and a handful of jobs were still running.

Checking the log we started getting this error at 2:16:18 and every subsequent second:

4/9/2012 2:16:18 AM Err thisTimeTick was null in TimePicker

Stopping and starting the server from a client failed to resolve this. Only when we restarted the windows service did jobs then start normally. We haven't had this problem again since then.

It seems like VC was unable to query the time from the machine. This is a bare-metal machine and we use primarily custom time triggers. There is no obvious culprit for the initial error.
Sponsor
Forum information
Support
2012-04-11T07:24:59Z
Originally Posted by: devonway 

Two nights ago I realized that our VC 5.7.4 Server wasn't starting any new jobs even though the server was started and a handful of jobs were still running.

Checking the log we started getting this error at 2:16:18 and every subsequent second:

4/9/2012 2:16:18 AM Err thisTimeTick was null in TimePicker

Stopping and starting the server from a client failed to resolve this. Only when we restarted the windows service did jobs then start normally. We haven't had this problem again since then.

It seems like VC was unable to query the time from the machine. This is a bare-metal machine and we use primarily custom time triggers. There is no obvious culprit for the initial error.



Thank you for the report. This issue is fixed in 6.x.x versions.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top