Filtering specific error reporting from Severity 20 Alerts

• Glen Moffitt-317424

  Old Hand

  Points: 301

  More actions

  September 25, 2009 at 2:53 pm

  #139012

  Our general alerting setup for sql server 2005 is to set up Severity level alerts for levels 11 - 25. Generally this works pretty well. However one new application system is generating numerous errors of a specific type that are included in the level 20 category.

  The vendor has told us to ignore those ("The connection has been dropped because the principal that opened it subsequently assumed a new security context, and then tried to reset the connection under its impersonated security context. This scenario is not supported. See "Impersonation Overview" in Books Online".)..for the moment things are working ok.

  Question is what is the best approach to keep getting other Severity 20 errors but not this particular one? Is there a better approach to defining the alert that would work for us?

  Thanks