We have multiple jobs that run every 15 minutes all day long. They almost always work correctly within VisualCron. However, every so often one of the jobs will not finish and eventually time-out (22 hours later). This happens even if it is processing no data on a simple copy function. The only thing I can see that may be common is that these jobs use IP Addresses to access files for parsing and copying. (Note: these are .bat and .cmd jobs submitted through an execute command.)

Also note that these jobs have run for years using Windows task scheduler and have never had a time-out issue once. Now that they run on VisualCron, we get at least one hanging every day.

Is it possible that VisualCron is losing connection to these jobs and never is notified that it completes? This does, of course, keep the job from being resummitted so we go for hours without data being processed. (No, we cannot run it more than once concurrently).

1. Are you talking about Execute Tasks only?
2. Are they foreground Tasks?

---

They are execute tasks only. Not foreground. Will run fine 15/20 times in a row (or more) then get stuck. Not sure if it is the IP connection or not but it does seem to be a common function.

Upon further research, it appears to be a problem using KLOG_Net.dll. (Kiwi Syslogger). Are you familiar with this product and have any issues been raised? It simply performs an asynchronous syslog message send. We seem to be getting hung on that call within VisualCron.

Have not heard anyone using it that way. I remember a long time ago when we implemented the SysLog notification that we tested on Kiwi. Can't you use the Notification instead?

---