Sounds like you may have a corrupt entry in your tblScheduledItems table. That error message might occur if the next execution date field in the database entry has passed. Run this query to find the rows:
select * from tblScheduledItem where pkID ='8de3f2b0-6e12-4716-a6f9-736f7e2f8944'
Blog posts for tips on debugging and logging from the scheduler:
Thanks Arild, the second link was helpful for me: after deleting the rows from the scheduler tables, the scheduler runs good again.
I have a weird problem with a scheduled job: when triggered by the scheduler, the scheduled job results in status FAILED, message "Object reference not set to an instance of an object". Also, no message is logged in the log file.
When the scheduled job is started manually, the scheduled job results in status OK; and it does write to the log file.
I don't think the cause of the error is in the scheduled job code (I placed a breakpoint in the code, this only gets triggered when I start the scheduled job manually), but here is my code anyway:
BTW, the log file also contain the following logging: "DataAbstraction.ScheduledJob - 3.1.3 Scheduled job has already been executed 8de3f2b0-6e12-4716-a6f9-736f7e2f8944. "
Hope you can help!