Job Failed alert is not raised for some jobs that fail

Monitor, diagnose and receive alerts to problems across your SQL Servers.

Job Failed alert is not raised for some jobs that fail

Postby Matt » Wed Jun 26, 2013 5:40 pm

I've noticed that some jobs don't raise an alert when they fail. I suspect it has to do with whether or what sort of error code is returned, but so far I've been unable to find the difference between jobs failures that raise the alert and ones that don't.

Here are two examples of recent job failures that didn't raise an alert:
1) transaction log backup failed because it was missing a full backup.
2) DBCC CHECKDB reporting consistency errors for a database.

I've verified that run_status = 0 in sysjobhistory, and that the job step is configured to "quit the job reporting failure" when the step fails. Both jobs are part of Maintenance Plans, but failures of those types of jobs have raised the alert before.

So I really have a two-part question.

First, why aren't these job failures triggering the "job failed" alert? i.e. what's different about them?

Second, and more importantly, how can I get alerts on them in the future? I really do want to know when log backup fail or I have consistency/corruption issues with databases. Basically, if I see a "red X" icon in the job history via SSMS, I think I'd like to get an alert via SQL Monitor.

Posts: 2
Joined: Wed Jun 26, 2013 5:08 pm

Postby priyasinha » Thu Jun 27, 2013 12:13 pm

Hi Matt,

SQL Monitor should notify you for all jobs which had run_status of anything other than 1.

The only issue I can think of is that we had a bug with job failure alert pre v3.4 release where it wouldn't notify of some job failures. The description of the bug can be found in release notes against bug number SRP-8159.

If you are experiencing this issue in v3.4 or later then I would suggested to raise a support request at so that we could investigate it.

Posts: 549
Joined: Wed Jan 03, 2007 4:02 pm

Postby Matt » Thu Jun 27, 2013 3:44 pm

Hi Priya,

That bug-fix looks like it applies to at least one of the failed jobs, so I'll go ahead and upgrade to 3.4. If I'm still having issues with the other job after that, I'll escalate to support.

Thanks for your help.
Posts: 2
Joined: Wed Jun 26, 2013 5:08 pm

Return to SQL Monitor Previous Versions

Who is online

Users browsing this forum: No registered users and 0 guests