FIX: SQL Server Agent does not send an alert quickly or does not send an alert when you use an alert of the SQL Server event alert type in SQL Server 2005
Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.
When you try to use a SQL Server Agent alert of the SQL Server event alert type in SQL Server 2005, you experience the following symptoms depending on the version of the SQL Server 2005 that you are running:
The original release version of SQL Server 2005 (SQL Server 2005 RTM)
SQL Server Agent does not send an alert for the first event after you clear all the events in the Application log in Event Viewer. However, SQL Server Agent sends alerts for the successive events. Additionally, an event that resembles the following is written to the Application log in Event Viewer:
Event Type: Error
Event Source: SQLSERVERAGENT
Event Category: Alert Engine
Event ID: 318
Date: 12/20/2006
Time: 3:14:59 PM
User: N/A
Computer: ComputerName Description:
Unable to read local eventlog (reason: The event log file has changed between read operations).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
SQL Server 2005 Service Pack 1 (SP1)
Unless you restart the SQL Server Agent service, SQL Server Agent does not send alerts after you clear all the events in the Application log in Event Viewer.
SQL Server 2005 build 2181 and later builds
SQL Server Agent may not quickly send alerts. Additionally, SQL Server Agent sends alerts for all the events in the Application log in Event Viewer. These events may include events that are linked to alerts that SQL Server Agent has previously sent. This problem occurs when the size of the Application log is 20 KB or more.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
You must have SQL Server 2005 Service Pack 1 (SP1) installed to apply this hotfix.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest service pack for SQL Server 2005
Restart information
You do not have to restart the computer after you apply this hotfix.
Registry information
You do not have to change the registry.
Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
Back to the top
