UPDATE: After SP1, this issue is gone, and all services can be run normally. There’s a good chance this issue was fixed at CU3 as I’m seeing user feedback in posts I was following claim that CU3 fixed the problem. Either way, life is better on SP1.
This issue looks to be specific to Microsoft Exchange 2013 CU1. My environment is running Server 2008 R2 on a Server 2008 R2 Domain Level. At the time of this post, there is no telling if CU2 fixes the issue.
Issue:
Here’s what you’ll see in the Event Viewer:
The Microsoft Exchange RPC Client Access service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
Solution:
Disable the Microsoft Exchange Health Manager service.
Service Name: MSExchangeHM
Notes:
It would be nice if there was more to this issue, but for now all we can tell is that the Health Manager believes there’s something wrong with RPC and restarts the service to try and fix whatever it sees is wrong. Obviously, we want the Health Management Service to be enabled, but if it’s going to do more harm than good we’re going to have to disabled it until MS fixes this. I’ve seen a few posts with some registry fixes that don’t seem to solve the issue altogether. That’s all there really is at this point.
Recent Activity