Hi We are getting the following error on a daily basis. As far as I can see it's the MonitoringHost.exe that's unexpectedly closed on our Exchange 2007 server. Alert: System Center Management Health Service Unloaded System Rule(s) Source: EXCH01.contoso.com Path: Microsoft.SystemCenter.AgentWatchersGroup Last modified by: System Last modified time: 7/18/2012 8:04:46 PM Alert description: The System Center Management Health Service BA9F45A8-8052-48A1-BA2E-C4AD79802CDD running on host EXCH01.contoso.com and serving management group with id {537B2B36-3DB2-4273-BFE8-1292C90FD446} is not healthy. Some system rules failed to load. When I receive the alert from our SCOM I also get an event in the Application log on the Exchange server with "Faulting application MonitoringHost.exe". I have just upgraded to CU1 and will see if that solves the problem! Lasse /Lasse

What version of the Exchange 2007 MP are you using? The R2 version or the one made for SP1. I can tell you that the monitoringhost.exe will exceed 5000 handle counts, which causes the agent to bounce itself. This also forces a monitor reset from the Exchange 2007 management pack (resets everytime the agent is stopped, I forget which monitor). While doing tuning, i noticed an Exchange 2007 Monitor was on my list for noisy. I started to look into this and noticed that on all of my Exchange 2007 servers, the agent (SCOM) was restarting several times a day. I enabled the monitors for agent restarting because of handlecount leak or privatebyte leak. I created performance collection rules. I overrode the limit of handle count to 10K from the 5K that is in the mp already. They still bounce, the handles keep leaking. Apparently there are some hotfixes for .net that are thought to be the cause, but when we tried one that was suggested, the servers reported they already had these hotfixes. Other servers are also bouncing agents, but the majority are Exchange 2007 servers in my environment, raising the limit just puts the bounces further out. We are on CU3 or 4 btw, so CU doesn't fix this issue. The issue is with .net or something in windows that can't release used handles.Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/

What version of the Exchange 2007 MP are you using? The R2 version or the one made for SP1. I can tell you that the monitoringhost.exe will exceed 5000 handle counts, which causes the agent to bounce itself. This also forces a monitor reset from the Exchange 2007 management pack (resets everytime the agent is stopped, I forget which monitor). While doing tuning, i noticed an Exchange 2007 Monitor was on my list for noisy. I started to look into this and noticed that on all of my Exchange 2007 servers, the agent (SCOM) was restarting several times a day. I enabled the monitors for agent restarting because of handlecount leak or privatebyte leak. I created performance collection rules. I overrode the limit of handle count to 10K from the 5K that is in the mp already. They still bounce, the handles keep leaking. Apparently there are some hotfixes for .net that are thought to be the cause, but when we tried one that was suggested, the servers reported they already had these hotfixes. Other servers are also bouncing agents, but the majority are Exchange 2007 servers in my environment, raising the limit just puts the bounces further out. We are on CU3 or 4 btw, so CU doesn't fix this issue. The issue is with .net or something in windows that can't release used handles.Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/

Hi Blake Thanks for the reply. We use the R2 version. We only see the agent restart issue on our Exchange 2007 SP3. We also have a CAS but it doesn't have the same issue, or at least not yet. After I wrote the post yesterday I updated our SCOM 2012 with CU1 and re-installed the agent on the Exchange server, and I actually haven't received the errror since. /Lasse

Well I would still ensure you are collecting handle count and private bytes for monitoringhost.exe and the healthservice.exe I believe.Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/

Well I would still ensure you are collecting handle count and private bytes for monitoringhost.exe and the healthservice.exe I believe.Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/