FIX: Alerts Triggered Incorrectly When Security Auditing is Enabled

By default, Security Auditing informational messages have a severity of 14. However, after you set up Security Auditing on the server, you may encounter a scenario where Security Auditing informational messages raise alerts with a variety of severity levels. The alerts may be randomly triggered.

When handling the audit login messages the server incorrectly initializes the severity variable and the latter is a random value.

SQL Server 2000

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix

NOTE: The following hotfix was created prior to Microsoft SQL Server 2000 Service Pack 1.

The English version of this fix should have the following file attributes or later:

SQL Server 7.0

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 7.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

SQL Server 2000
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 1.

SQL Server 7.0
This problem was first corrected in Microsoft SQL Server 7.0 Service Pack 4.

The alerts that occur are determined by what severity-based alerts you have currently defined. By default, SQL Server installs severity-based alerts with a severity ranging from 19 to 24.

An example of a typical Security Auditing information message is: You may see an alert e-mail sent to you that contains the following type of severity information: