The Exchange Server Health Management Worker process restarts frequently in a Microsoft Exchange Server 2013 environment. This problem occurs after you add or change a server monitoring override by using the add-servermonitoringoverride cmdlet.

In this situation, you may see the following events reported as frequently as every five minutes:

You can determine whether you're experiencing these symptoms by checking for these event items in the event log. Additionally, you can verify these events by checking the output from the Get-Servermonitoringoverride <servername> |fl *Name, *Time cmdlet for the following conditions:

  • The ExpirationTime value on any overrides uses something other than the DD/MM/YYYY date format. For example, the value uses a MM/DD/YYYY format.

  • The date value (DD) is greater than 12 (the twelfth day of the month).


This problem occurs if a server monitoring override is added and the server is configured to use non-US regional settings. This causes date formats that don't follow the MM/DD/YYYY format.

In this scenario, the expiration date for the override is populated by using the localized date format (for example, DD/MM/YYYY). If the expiration date falls on a day that is later than the twelfth day of the month, the Managed Availability system can't evaluate the expiration date correctly.

This problem can also occur when a server monitoring override is created on a date greater than the twelfth and the Duration parameter isnt' specified. In this scenario, the server monitoring override is created having an expiration date one year from the date of creation.


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


  • After you apply the update, any new server monitoring overrides won't exhibit the symptoms because the date format will align with Global Monitoring overrides.

  • After you apply the update, any existing server monitoring overrides that still have an ExpirationTime value in a date format such as DD/MM/YYYY and a date value that is greater than 12 must be re-created.

To work around this problem, remove any server monitoring overrides that have an incorrect ExpirationTime value a date value that is greater than 12.

Re-create the override, and use the -duration parameter to make sure that the expiration date occurs earlier than the twelfth day of the month.


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


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

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!