Error-handling rules for missed jobs, BE2015
Hi all,
I've had BE2015 for a little more than 2 months now, and almost all of the issues are ironed out, but one niggling problem remains: I cannot create a functioning error-handling rule to address the 'missed job' e000e020 situation. I have tried to do this through the 'Configuration and Settings > Error-Handing Rules', and also by right-clicking on a Missed job in the Job Histories, and selecting 'Error Handling'.
The rules exist, they just don't seem to work, and I can find no record that they tried to run and failed, or any other detail. It's tricky to run the Debugger, because you never know when the missed job situation will actually arise, and if I let the Debugger run all weekend, I'll fill up the Applications volume with log files.
There is only one other rule Enabled, "Recovered Jobs", which I believe was automatically created by BE - I certainly didn't create it. That does appear to run when jobs end up as 'Recovered', a situation that doesn't happen at all frequently.
I had this rule set up in BE2010, and it worked perfectly. It was very handy because with over 50 jobs and 150 servers a 'Missed' condition happens every weekend, and this simple rule would catch those and automatically re-run them w/o human intervention. Now, I have to log in every weekend and re-run jobs.
My system is:
Win2008 R2 Std. - BE2015 (Ver 14.2 Rev. 1180, 64-bit) - no Antivirus - standalone physical server - up to date w/ patches and Hotfixes.
Any thoughts on why this rule wouldn't run?
Thanks!
.
Neil
I believe it cannot be configured for missed jobs since BE 2010 R3 (atleast if i recall and quite surprising that you were able to configure it). Would recommend to log a formal support case and reference https://support.symantec.com/en_US/article.TECH176762.html