June 23, 2014 at 1:36 pm
So I have a logon trigger in place and it's working fine but I wanted to put in an alert to disable the trigger if it should get an error number 17892 "Logon failed for login due to trigger execution." So I put the alert in place (see script) and then forced an error in the trigger.
EXEC msdb.dbo.sp_add_alert @name=N'LoginFailure',
@message_id=17892,
@severity=0,
@enabled=1,
@delay_between_responses=0,
@include_event_description_in=1,
@category_name=N'[Uncategorized]',
@job_id=N'f2db23e5-bae8-4da1-9212-723df88bb71c'
GO
The logon trigger failed and according to the job history the disable trigger job was successful but the trigger is still enabled. The alert calls a job that contains only
DISABLE TRIGGER [MyTrigger] ON ALL SERVER
Job history says this alert fired and called this command, which successfully ran and yet the trigger is still enabled and denying connections.
Ideas?
Regards,
Erin
June 24, 2014 at 9:50 am
*bump*
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply