Friday, February 24, 2012

Cant make alert job work.

sql2k
sp4
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 1204 and 1205 to log deadlocks.
2; I've tried running different jobs manually. They both work.
On the advice I got last week, I have verified that the Event Log service
and SQL Server Agent are both running. Its probably worth noting though that
while I do see the deadlock in the SQL Error Log, it doesnnt show up in the
Event Viewer.
Any ideas?
TIA, ChrisRYou need to configure 1205 so it is written to the eventlog. In EM, right-click the server, Manage
Messages. Here you search for 1205 and check to write to eventlog. In 2005, you cannot customize
system messages this way, though.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:EA439440-08D7-4BBA-8EA5-E69C4DEC6C44@.microsoft.com...
> sql2k
> sp4
> 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 1204 and 1205 to log deadlocks.
> 2; I've tried running different jobs manually. They both work.
> On the advice I got last week, I have verified that the Event Log service
> and SQL Server Agent are both running. Its probably worth noting though that
> while I do see the deadlock in the SQL Error Log, it doesnnt show up in the
> Event Viewer.
> Any ideas?
> TIA, ChrisR
>|||I keep trying to add this but it doesnt save it. I add it, hit OK, reopen and
its gone. Im logged in as local admin so I know thats not it. Any ideas?
"Tibor Karaszi" wrote:
> You need to configure 1205 so it is written to the eventlog. In EM, right-click the server, Manage
> Messages. Here you search for 1205 and check to write to eventlog. In 2005, you cannot customize
> system messages this way, though.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:EA439440-08D7-4BBA-8EA5-E69C4DEC6C44@.microsoft.com...
> > sql2k
> > sp4
> >
> > 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 1204 and 1205 to log deadlocks.
> > 2; I've tried running different jobs manually. They both work.
> >
> > On the advice I got last week, I have verified that the Event Log service
> > and SQL Server Agent are both running. Its probably worth noting though that
> > while I do see the deadlock in the SQL Error Log, it doesnnt show up in the
> > Event Viewer.
> >
> > Any ideas?
> >
> > TIA, ChrisR
> >
>|||Tibor I just realized this is more of a "not write to error log" issue, so I
reposted accordingly, thanks.
"Tibor Karaszi" wrote:
> You need to configure 1205 so it is written to the eventlog. In EM, right-click the server, Manage
> Messages. Here you search for 1205 and check to write to eventlog. In 2005, you cannot customize
> system messages this way, though.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:EA439440-08D7-4BBA-8EA5-E69C4DEC6C44@.microsoft.com...
> > sql2k
> > sp4
> >
> > 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 1204 and 1205 to log deadlocks.
> > 2; I've tried running different jobs manually. They both work.
> >
> > On the advice I got last week, I have verified that the Event Log service
> > and SQL Server Agent are both running. Its probably worth noting though that
> > while I do see the deadlock in the SQL Error Log, it doesnnt show up in the
> > Event Viewer.
> >
> > Any ideas?
> >
> > TIA, ChrisR
> >
>

No comments:

Post a Comment