Exchange Health Manager Service Wont Start Automatically After Installing 2013 CU2 V2
After installing Exchange 2013 CU2 Version 2, the Exchange Health Manager service does not start automatically! The service has been set to start automatically. But, even after a reboot, the service remains in the same state. All the three recovery steps of the service is to restart the service, but nothing! The only…
After installing Exchange 2013 CU2 Version 2, the Exchange Health Manager service does not start automatically!
The service has been set to start automatically. But, even after a reboot, the service remains in the same state.
All the three recovery steps of the service is to restart the service, but nothing!
The only dependency is on Windows Event Log service, which is running. If I start the service manually, it starts up and runs without any complaints.
If I restart the server after that, it again goes back into the stopped state. I am having the same problem on a brand new install of 2013 CU2 V2 – CAS and Mailbox role.
Anyone else seeing this issue?
Recreating the healthmailboxes 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.
Thanks for the update Martijn. It seems to be a “hit and miss” – works for some, but not all ;-)
I’ve the same problem, but recreating the healthmailboxes doesn’t fix the problem in my test enviroment…
http://theucguy.net/2013/08/recreate-exchange-2013-health-mailboxes.html fixed the issue for me.
Does the service start, say after 10-15 minutes?
Also had this issue in a customer with Exchange CU 2 V2. =(
Thanks Tiago. http://theucguy.net/2013/08/recreate-exchange-2013-health-mailboxes.html seems to fix the issue.
I also have this issue. See my comments at http://blogs.technet.com/b/exchange/archive/2013/07/29/now-available-updated-release-of-exchange-2013-rtm-cu2.aspx
Update regarding: Microsoft Exchange Health Manager service does not start automatically after reboot
Exchange Health Manager service has not been started after reboot with event viewer IDs 7000 & 7009.
However, after some time (10-15 minutes), Exchange Health Manager service automatically starts. I’ve tested this with Windows 2012 & Exchange 2013 CUv2. So, this seems to be a (small) issue.
Recreating the health mailboxes starts the service automatically. http://theucguy.net/2013/08/recreate-exchange-2013-health-mailboxes.html
I’m experiencing a big problem after installing CU2..
All Exchange Server 2013 servers crash regularly, and when I check the minidump it’s always caused by this service.
The only difference is that indeed the service doesn’t start automatically when the CU2 (version 2) is installed.
It’s a bit strange to me that in CU2 version 1, this service causes our systems to reboot regularly, and in CU2 version 2, it doesn’t start up automatically anymore…
Glad that I am not alone. Is it a VM?
is it running in vm
mine was vm(but I also saw it in physical with other products) where the load at boot is so “high” that some services wont start right(lync , ocs,tmg array on r2) and only workaround was this delayed start.
It is a VM, but a beefy one with 8GB RAM and running on full SSD.
Try recreating the HealthMailbox. You can safely delete and recreate health mailboxes. Be aware that any local Managed Availability probes that are using the these mailboxes will fail until the Microsoft Exchange Health Manager is restarted. Once that service is restarted, it will recreate any mailboxes that it needs. Hopefully that will resolve this issue.
Recreating the health mailbox have solved the issue. Although restarting the health manager service doesn’t create ALL health mailboxes. When compared with the original ones, one health mailbox is missing. It only creates two (one database only), but the default install had created three.
I have seen this before, where an additional mailbox creation will create two more health mailbox taking the total to five. Looks like there is one per server? Is that the case?
I think this could be because i haven’t installed a SCOM Agent – or any other monitoring tool. In Exchange 2010 it gave the Exchange Monitoring Service, which was used by a monitoring tool like SCOM. The difference here is, that in 2010, the service startup type is default set to manual..but that’s just a guess :)
No SCOM in my lab and this is happening, and that too even on a brand new forest with clean CU2 V2 install.
Service is set to automatic.
Also had this issue, but when you set the service to ‘Automatic (Delayed Start)’ it starts fine after each reboot.
Thanks Frank. I thought I was the only one with this issue.
set it to delayed startup works for me
Microsoft with their clunky services….
This should work automatically TurboMCP.
Since manually starting works fine, I am not sure what is blocking it in the first place.
And nothing in event viewer as well.
there may be a problem with healthmailboxes. Try “setup.exe /preparead” from CU2-v2
Mailboxes are fine. Any other ideas?
Weird. I just noticed it this morning before seeing your post. I’m the same as you: Exchange 2013 CU2 multi-role and the service is doing the exact same thing as you described.
Thanks Cameron for the update. Good that I am not the only one ;-)