Howdy SCN SAPers!
Here is a juicy and delicious one--couldn't find anything about this happening to others, though some people have mentioned jobs failing or sitting in pending status due to predecessor jobs that were very large and failed or simply just so large they could have lapsed into the start time of other scheduled jobs.
We have been experiencing an issue with WebIntelligence, BO 3.1 SP6, where we have scheduled jobs to run, but we are finding them in Pending status with the Next Run Time to be 35 years in the past and the Submission Time to be today! We have these jobs scheduled to run in the wee hours of the morning, primarily to be able to provide all of the available resources we can to run ad-hoc jobs during the day. Does anyone know what could be causing this issue and also how to resolve it permanently? Don't mind restarting the processing server, but to restart it every day really detracts from the idea of automation. We have not restarted the server, but have been asking users to simply reschedule the reports, but they continue to go to pending status with a next run time in the past as well as other reports.
Sincerely,
Omar