Event ID 4999 or 1007 if diagnostics service crashes repeatedly in Exchange Server 2013

Applies to: Exchange Server 2013 EnterpriseExchange Server 2013 Service Pack 1Exchange Server 2013 Standard Edition

Symptoms


Microsoft Exchange diagnostics service crashes repeatedly in a Microsoft Exchange Server 2013 environment. Therefore, the diagnostics service can't create or start performance logs. Additionally, you receive the following error messages in the event logs:

Error 4999 Date/Time  Watson report about to be sent for process id: ProcessID, with parameters: E12IIS, c-RTL-AMD64, VersionNumber, M.E.Diagnostics.Service, M.E.Diagnostics.PerformanceLogger, M.E.D.P.PerformanceLogSet.StartLog, System.ArgumentException, 95c6, VersionNumber.%nErrorReportingEnabled: False %n MSExchange Common ServerName.Contoso.com

Error 1007 Date/Time  Failed to create or start performance logs with error: System.ArgumentException: Value does not fall within the expected range.
at PlaLibrary.DataCollectorSetClass.start(Boolean Synchronous)
at Microsoft.Exchange.Diagnostics.PerformanceLogger.PerformanceLogSet.StartLog(Boolean synchronous)
at Microsoft.Exchange.Diagnostics.PerformanceLogger.PerformanceLogMonitor.CheckPerflogStatus(). Performance log: ExchangeDiagnosticsPerformanceLog. MSExchangeDiagnostics ServerName.Contoso.com

The Task Scheduler stores the old tasks' GUID in memory, and the only way to clear them is to restart the service and clear the tasks manually.

Cause


This issue occurs because the failure counter that's triggered by Task Scheduler exceeds the threshold, and can't retrieve information from associated files.

Resolution


To fix this issue, install Cumulative Update 19 for Exchange Server 2013 or a later cumulative update for Exchange Server 2013.

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References


Learn about the terminology that Microsoft uses to describe software updates.