SQLSERVERAGENT warning: Event ID: 312_MySQL

This article mainly introduces SQLSERVERAGENT warning: Event ID: 312, information: Event ID: 311, error: Event ID: 318, for more information, see Successfully re-opened the local eventlog-NOTE: Some events may have been missed.

Attempting to re-open the local eventlog...

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: 17:08:17

User: N/

Computer: B-SERVER

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: 17:08:17

User: N/

Computer: B-SERVER

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: 17:08:17

User: N/

Computer: B-SERVER

Description:

Unable to read local eventlog (reason: the event log file has been changed between reads .).

For more information, see help and support center in http://go.microsoft.com/fwlink/events.asp.

Solution:

When the SQLSERVERAGENT service is enabled, if the application logs in the system logs are cleared, the preceding three logs (errors, messages, and warnings) are displayed ). No special processing is required.