Ask questions about the SQLSERVER AGENT error log

lf_168

Problem Description:
  The following three logs appear in the application log in Event Viewer:
  1. Error Source SQLSERVERAGENT Category: Alert Engine Event:

318 user N / A
    Description: Unable to read local eventlog (reason: event log

The file has been changed at read time. )
  2. Information Source SQLSERVERAGENT Category: Alert Engine Event:

311 user N / A
   Description: Attempting to to re-open the local eventlog ..
  3. Warning Source SQLSERVERAGENT Category: Alert Engine Event:

312 user N / A
   Description: successfully re-opened the local eventlog

-NOTE: Some event may have been missed
Then the application log is quickly full. The log event IDs that appear later are all 17055.
  The following two messages appear alternately every minute, and the time is described as follows
  Description: 17550: DBCC TRACEON 208, server process ID (SPID56)
  Description: 17550: DBCC TRACEON 208, server process ID (SPID61)
 

 What should I do to keep this error log from appearing? It is annoying that the application log is full soon. . I beg you for your help. . .

我是杀人狂

It can be deleted when full, or compressed ~~

lf_168

This is not the way, the log is deleted and it will be full soon.
I want to find a way to avoid these errors ..
The real master knows how to solve it?

lf_168

I want to ask what method can make this error of SQL not appear again, instead of letting it display in the event viewer,
If you filter out errors, warnings, and information, you wo n’t see other event logs.
Does any master know that sqlserver agent fundamentally solves this problem?

nity1118

1. In Enterprise Manager, right-click the server name, and then click Properties.
2. On the General tab, click Startup Parameters.
3. Add the following as new parameters:
-T2505
4. Restart the server

lf_168

If you want to prevent these messages from appearing in the error log, you can use the trace flag 2505 as the startup parameter

To use trace flag 2505 as a SQL Server startup parameter, use the following steps:

1. In Enterprise Manager, right-click the server name, and then click Properties.
2. On the General tab, click Startup Parameters.
3. Add the following as new parameters:

-T2505
4. Restart the server for the new parameters to take effect.

Solve it yourself..