Hi,
I upgraded a couple of production servers to version 5.7.0 last week from 5.6.9 to fix the sql parameter length problem, which all went ok when I launched jobs manually as a test, but I've just discovered a couple of days later that my timed triggers are no longer working.
The "next run" times on the tasks get updated when the trigger fires, but the Execute task doesn't actually run. After a bit of digging around I found the following in the VisualCron "log_server<date>.txt" file when one of the tasks was supposed to run at 01:00:
27/11/2010 01:00:00 Err Unhandled error in looplist (Job: <MyJobNameHere>): System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.GHAMFGCEDFOEIDCMEENNAFIOCECPBDKLJMLG.PHAOGBOCFMEIDJACKKLGMGMMNBFIJCANFHPJ(String ) in C:\sourcefiles\code\VisualCronService\Jobs\apiJob.vb:line 59
at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.GHAMFGCEDFOEIDCMEENNAFIOCECPBDKLJMLG.MCEGBAJCFDNLGODPIHJCNEKNENECINEKEDMI(BLCNDEBFOPPCAMEEPMEOIENEBOLAFPMBCDIK ) in C:\sourcefiles\code\VisualCronService\Jobs\apiJob.vb:line 840
This is happening on two separate servers which both upgraded from 5.6.9 to 5.7.0. I've downgraded them both back to 5.6.9 now which seems to have temporarily fixed the problem, but I'd really like to get the sql parameter fix in 5.7.0 in place.
Can you shed any light on what the issue might be? I renamed some notifications and made some other changes to jobs and tasks so that might have affected it, but I can't think of anything that should cause interval triggers to stop working.
Cheers,
M