Friday, March 22, 2013 7:40 PM
For some reason earlier today one of the ad-hoc reports ran into problem and got stuck since then... it's still showing in the runningjobs table with the timeout = -1. This causes a serious problem for us, since it prevents other report schedules to run - the following reports schedules are all in 'pending' status right now... Is there some way that I can simply kill the one stuck in the runningjobs table and resume those in pending status?
I've already tried restarting the reportServices, also restarted the reporting server.
Please help! We need any assistance asap...
Friday, March 22, 2013 10:26 PM
have you tried to stop report execution in SSMS?
Please mark as helpful and propose as answer if you find this as correct. nosekz.eu
Monday, March 25, 2013 3:52 PM
The problem is there was nothing showing as active even though there were quite a few records in the RunningJobs table. That's why I said those report jobs were stuck... But after a few hours, the queue seemed to be cleaered out and nothing was left in that table anymore... I'd like to understand why this even happens from time to time, but unfortunately I didn't find too much information on the internet...
Monday, March 25, 2013 5:25 PMBy the way, the problem happened again this morning...