Hi Gary,

I'm guessing that the reason this is happening is because one of your jobs has never been run, or under last_run_time/date there is something other than dates such as "Unknown"? I'll modify the script to handle this, but in the mean time, just give that job a dummy run date. The problem will only appear the first time you create a job and it has never been run. You can give it a dummy run either by doing so in the system table or by telling SSMS that the job should report Success on Failure. Then run it, then change it back to Success on Succeed. This can be done in the advanced tab of the job.