Alert not triggering

I've configured an alert for the TLog that when the server generates error
9002 (out of log space) to kick off a job that will backup the TLog to clear
it. I am testing the alert and I receive the error message, but the it will
not activate the alert. I've ensured that it is enabled and that the job
works, but for some reason the alert is not working. Can anyone help?
Andrew
Does the error show up in the `Windows event log?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Big Ern" <BigErn@.discussions.microsoft.com> wrote in message
news:0BD5E05C-F708-43D7-ADC1-6CCC75F61D26@.microsoft.com...
> I've configured an alert for the TLog that when the server generates error
> 9002 (out of log space) to kick off a job that will backup the TLog to clear
> it. I am testing the alert and I receive the error message, but the it will
> not activate the alert. I've ensured that it is enabled and that the job
> works, but for some reason the alert is not working. Can anyone help?
> Andrew
|||Yes the error appears in both the SQL and Windows event logs.
"Tibor Karaszi" wrote:

> Does the error show up in the `Windows event log?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Big Ern" <BigErn@.discussions.microsoft.com> wrote in message
> news:0BD5E05C-F708-43D7-ADC1-6CCC75F61D26@.microsoft.com...
>
|||The last think I can think of is that agent isn't started. If that isn't the case and you can't find
anything obvious in Eventlog, I'm out of ideas, I'm afraid...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Big Ern" <BigErn@.discussions.microsoft.com> wrote in message
news:7AA07BA5-5744-4DC1-BF8F-310C1C700A49@.microsoft.com...[vbcol=seagreen]
> Yes the error appears in both the SQL and Windows event logs.
> "Tibor Karaszi" wrote:
sql