Wednesday, August 7, 2013

Microsoft Exchange Health Manager service does not start automatically

I installed two new Exchange 2013 servers (1x CAS & 1x MBX) with latest CU2 (build 15.0.712.24).

Issue: Microsoft Exchange Health Manager service does not start automatically after reboot.

Event Viewer System log:

Event ID:      7000
Level:         Error
Description:
The Microsoft Exchange Health Manager service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

Event ID:      7009
Level:         Error
Description:
A timeout was reached (30000 milliseconds) while waiting for the Microsoft Exchange Health Manager service to connect.

No problem manually starting Microsoft Exchange Health Manager service. When you set the service to ‘Automatic (Delayed Start)’ it starts fine after each reboot.

I've posted comments at http://blogs.technet.com/b/exchange/archive/2013/07/29/now-available-updated-release-of-exchange-2013-rtm-cu2.aspx

http://howexchangeworks.com/2013/08/exchange-health-manager-service-wont-start-automatically-after-installing-2013-cu2-v2.html#comment-3391 describes that recreating Health mailboxes may solve this problem. Recreating the Health mailboxes doesn’t fix the problem. Service has not been started after reboot. However, after some time (10-15 minutes) the service starts automatically.

So, this still seems to be an issue because the Exchange Health Manager service has not been started automatically after a reboot (only after 10-15 minutes).

1 comment: