8 Replies Latest reply on Feb 14, 2013 8:13 AM by Justin Hearnsberger

    Job still "running" over a month

      We have an issue where on January 9th, 2013 we had a scheduled job run. This job only takes about 3 minutes to run and runs every 2 hours. The next occurrance of the scheduled job failed on all servers. Then...amazingly...it failed every since run after that. Keep in mind that the January 9th run is still marked "Running". We have had the infrastructure down for hardware maintenance at our NOC and the systems have been restarted twice since this time for software maintenance and patching. Any thoughts as to how we can get around this? Anything that doesn't involve decommission / commission of the systems in question? Any help is much appreciated.