I'm running the beta of CU10 and it still happens. I think it was first reported in TAP at CU5. There are several reports of it in the TAP bug database. It hasn't made it high enough to hit the bar to be fixed.
Generally speaking, MSFT doesn't admit bugs until after they are fixed. From: [email protected] [mailto:[email protected]] On Behalf Of Jonathan Raper Sent: Wednesday, August 5, 2015 9:45 PM To: [email protected] Subject: Re: [Exchange] RE: Exchange Health Manager service terminated unexpectedly LOL, ok, so no solution? Just ignore them? Is there any publicly available kb to reference? Is it resolved in a newer CU? I searched for a while and only came across community posts and maybe one blog, but again it seemed to be a bigger or slightly different problem than what I am experiencing. Thanks, Jonathan Sent by Outlook<http://taps.io/outlookmobile> for Android On Wed, Aug 5, 2015 at 5:02 PM -0700, "Michael B. Smith" <[email protected]<mailto:[email protected]>> wrote: This is a known problem. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jonathan Raper Sent: Wednesday, August 5, 2015 5:35 PM To: [email protected]<mailto:[email protected]> Subject: [Exchange] Exchange Health Manager service terminated unexpectedly Hoping someone here has some ideas about this. I have a couple of 2013 Exchange Servers (Hybrid servers) , running CU7, that occasionally have the MSExchangeHM service stop. I can't seem to find a rhyme or reason as to why. The service eventually (within minutes) restarts successfully. We have a monitoring system (Zenoss) that detects this, and so a case is generated any time it stops (or fails to restart on the first try). As tempted as I am to have the monitoring system ignore the alert, I would like to know why and fix this. Nothing in any of the event logs that I can see gives any clue as to why.... This is evidenced by Event ID 7031, 7009,7000, and eventually clears via 7036 with a source of Service Control Manager: * 7031: The Microsoft Exchange Health Manager service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service. * 7009 (does not always happen): A timeout was reached (30000 milliseconds) while waiting for the Microsoft Exchange Health Manager service to connect. * 7000 (does not always happen): 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. * 7036: The Microsoft Exchange Health Manager service entered the running state. If anyone has any thoughts as to why or some pointers as to where to look, I'd appreciate it. Everything I have found online so far points to a constant recurence, which is not my issue. It might happen several times in a day or it might happen a few times a month, but not with any regularity or consistency, and it isn't filling up the event logs as others have reported. Thanks, Jonathan
