Alerts not firing off jobs.

sql2k
sp3
Howdy all. I set up an Alert for deadlocks (# 1205) and have the checkbox
checked to fire off a job when it occurs. I then generate a deadlock, but the
job never gets fired off. Some important fun facts:
1; I ran dbcc traceon with 1205 and 1205 to log deadlocks.
2; I've tried running different jobs manually. They both work.Is the alert itself firing? Make sure that the EventLog
service and SQL Agent are running. Check the Event log to
make sure that it is not full. Check if the event is writing
to the Application log. There is also a topic in books
online with more information on troubleshooting alerts.
Check the topic: Troubleshooting Alerts
-Sue
On Thu, 13 Apr 2006 15:36:02 -0700, ChrisR
<ChrisR@.discussions.microsoft.com> wrote:
>sql2k
>sp3
>Howdy all. I set up an Alert for deadlocks (# 1205) and have the checkbox
>checked to fire off a job when it occurs. I then generate a deadlock, but the
>job never gets fired off. Some important fun facts:
>1; I ran dbcc traceon with 1205 and 1205 to log deadlocks.
>2; I've tried running different jobs manually. They both work.
>

Alerts not firing off jobs.

sql2k
sp3
Howdy all. I set up an Alert for deadlocks (# 1205) and have the checkbox
checked to fire off a job when it occurs. I then generate a deadlock, but th
e
job never gets fired off. Some important fun facts:
1; I ran dbcc traceon with 1205 and 1205 to log deadlocks.
2; I've tried running different jobs manually. They both work.Is the alert itself firing? Make sure that the EventLog
service and SQL Agent are running. Check the Event log to
make sure that it is not full. Check if the event is writing
to the Application log. There is also a topic in books
online with more information on troubleshooting alerts.
Check the topic: Troubleshooting Alerts
-Sue
On Thu, 13 Apr 2006 15:36:02 -0700, ChrisR
<ChrisR@.discussions.microsoft.com> wrote:

>sql2k
>sp3
>Howdy all. I set up an Alert for deadlocks (# 1205) and have the checkbox
>checked to fire off a job when it occurs. I then generate a deadlock, but t
he
>job never gets fired off. Some important fun facts:
>1; I ran dbcc traceon with 1205 and 1205 to log deadlocks.
>2; I've tried running different jobs manually. They both work.
>

Alert didn't fire

Hi, I create a alert for login failed, the error number
is 18456, although the severity is 14, but when I create
the alert, it is forced by SQL server to write to
application log. Then I go to query analyzer, use a wrong
password for SA, but the alert didn't fire, I go to check
application log, and there is the error message. Would you please tell me
why and how to solve it?
Thanks a lot
Arturo
Message posted via http://www.sqlmonster.com
Did you setup an operator for the alert?
"Arturo Aguilar Landero via SQLMonster.com" <forum@.SQLMonster.com> wrote in
message news:41680c273cbd45c99a3f8d0e735706cf@.SQLMonster.c om...
> Hi, I create a alert for login failed, the error number
> is 18456, although the severity is 14, but when I create
> the alert, it is forced by SQL server to write to
> application log. Then I go to query analyzer, use a wrong
> password for SA, but the alert didn't fire, I go to check
> application log, and there is the error message. Would you please tell me
> why and how to solve it?
> Thanks a lot
> Arturo
> --
> Message posted via http://www.sqlmonster.com
|||yes, already check the operator and works correctly,
with another alert
Message posted via http://www.sqlmonster.com