Error message
Today, when maintaining the Web SERVER (Windows 2003 Enterprise Edition SP2 + SQL server 2000 + ASP. NET) of the group company, an error was reported as soon as I logged on to the system:
Event Type: Error
Event Source: SQLSERVERAGENT
Event Type: Alert Engine
Event ID: 318
Date: 2011-2-16
Event: 21: 44: 52
User: N/
Computer: Siutung. Org
Description:
Unable to read local eventlog (reason: the event log file has been changed between reads .).
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Type: Alert Engine
Event ID: 312
Date:
Event: 10:06:37
User: N/
Computer: LENOVO-T280-G3
Description:
Successfully re-opened the local eventlog-NOTE: Some events may have been missed.
For more information, see help and support center in http://go.microsoft.com/fwlink/events.asp.
Event Type: Information
Event Source: SQLSERVERAGENT
Event Type: Alert Engine
Event ID: 311
Date:
Event: 10:06:37
User: N/
Computer: LENOVO-T280-G3
Description:
Attempting to re-open the local eventlog...
For more information, see help and support center in http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: SQLSERVERAGENT
Event Type: Alert Engine
Event ID: 318
Date:
Event: 10:06:37
User: N/
Computer: LENOVO-T280-G3
Description:
Unable to read local eventlog (reason: the event log file has been changed between reads .).
Note:
This error is generated by SQL SERVER 2000.
Solution 1:
Ms SQL Server Enterprise Manager-> Manage-> SQL Server proxy-> alert, delete all alerts (right-click, delete all alerts)
Solution 2:
To prevent error logs, you can use the trace flag 2505 as the startup parameter.
To use trace flag 2505 as an SQL Server startup parameter, follow these steps:
1. Enterprise Manager, right-click the server name, and select "properties ";
2. On the "General" tab, click "startup parameters ";
3. Add the following as a new parameter:-T2505 (note:-T2505 is a whole with no space character in the middle !);
4. Restart the server to apply the new parameters.