SQL Server Agent error logs

Microsoft explained:
Http://support.microsoft.com/default.aspx? SCID = KB; en-US; 811484

The following information source:
Http://blog.csdn.net/sfqy9907/archive/2007/03/14/1528727.aspx
Problem description:
The following three logs appear in the application logs in Event Viewer:
1. Error Source: SQLServerAgent type: Alert engine event:

318 user N/
Description: unable to read local EventLog (reason: Event Log

The file has been changed at the read time .)
2. Information Source SQLServerAgent classification: Alert engine event:

311 user N/
Description: attempting to re-open the local EventLog ..
3. Warning source SQLServerAgent classification: Alert engine event:

312 user N/
Description: successfully re-opened the local EventLog.

-Note: Some event may have been missed
Then the application logs will soon be full and the log event IDs will be 17055
The following two messages appear alternately every minute. The time is described as follows:
Description: 17550: DBCC traceon 208, server process ID (spid56)
Description: 17550: DBCC traceon 208, server process ID (spid61)

Solution:

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 From the shortcut menu.
2. on the General tab, click Start parameters.
3. Add the following as a new parameter:

-T2505
4. Restart the server to apply the new parameters.