MonitoringHost.exe High CPU Usage on Exchange 2007 Server RRS feed

  • Question

  • Hi all,

    I'm having an issue with my Exchange 2007 server and SCE 2007 SP1.  Everything shows up correctly in SCE, reports and monitoring views display data with no problems.  However, when I look at the running processes on the Exchange server, MonitoringHost.exe is constantly runng between 70-95% CPU usage. 
    If I stop/start or restart the OpsMgr Health Service, MonitoringHost.exe returns to a more normal use between 0-10% and stays that way for several hours before kicking up to the 70-95% range.  Any ideas on what might be causing it to do this or how to fix it?

    Server details:
    Exchange Server 2007 SP1
    Windows Server 2003 R2 Standard SP2, 64-bit
    4GB RAM

    SCE 2007 SP1
    Windows Server 2003 R2 Standard SP2
    4GB Ram

    Thursday, June 25, 2009 4:05 PM

All replies

  • Hi Michael,

    Please install Hotfix 954903:

    The Monitoringhost.exe process may consume all the CPU resources when a large amount of performance data is created by using a managed data source module in System Center Operations Manager 2007


    This hotfix is for SCOM 2007 but is also available for SCE.

    Monday, June 29, 2009 9:54 AM
  • Hi Eric,

    I do have Hotfix 954903 installed on the Exchange server.  Problem is still occuring.  Any other places to look?

    Monday, June 29, 2009 1:02 PM
  • Hi Michael,

    Please check the  version of the Exchange 2007 MP on your SCE server and make sure that it's the latest version(6.0.6461.0).

    You can check the version in SCE console - Administration pane - Management Pack.

    If you have the old version, please download and import the latest version from this link:

    Download details: Exchange Server 2007 MP for SC Ops Mgr 2007


    Also, please make sure you have applied hotfix 951979,958253,960363 on your SCE server.

    And apply kb940284 and 955360 on your Exchange server, KB 940284 & 955360 cover the Windows Script 5.7 release. There are numerous leak and performance fixes in this release which are germane to SCE:

    Hotfix 951979: Problems occur on a management server that is running System Center Operations Manager 2007 Service Pack 1 when certain management packs are installed


    Hotfix 952853: When you try to view the Patch List property, the list of Operations Manager agent hotfixes may be truncated on System Center Operations Manager 2007 Service Pack 1 systems


    Hotfix 960363: Charts in a performance report are incorrectly scaled, or a report that contains multiple charts does not display the charts in the correct order in System Center Operations Manager 2007 SP1


    940284    When you use Internet Explorer 7 to visit a Web site that includes certain VBScript functions, Internet Explorer 7 may crash

    955360    WSH binaries are overwritten by Windows File Protection after you install Windows Script 5.7 on a computer that is running Windows Server 2003 or Windows XP

    Hope this helps.
    Tuesday, June 30, 2009 6:40 AM
  • Eric,

    I installed the udpates yesterday morning.  The problem seemed to have been resolved, as the MonitoringHost.exe was operating normally up until the time I left the offlice last evening.  However, when I came in this morning and started to check through things, it was running constantly between 90-99%.  Is there anything else we can do, as far as adjusting MP settings (or other updates) or is this a situation where we're just going to have to 'live' with restarting the OpsMgr service everyday?

    Wednesday, July 1, 2009 2:26 PM
  • Hi,

    Sometimes it is a antivirus software trying to scan every script SCE agent is running, and it is running scripts all the time.

    So if you have an ativirus software, pleasetry disable it for a while, and check whether the CPU usage will be back to normal.
    • Marked as answer by Eric Zhang CHN Wednesday, July 8, 2009 9:28 AM
    • Unmarked as answer by JMichael S Wednesday, July 8, 2009 12:25 PM
    Thursday, July 2, 2009 9:53 AM
  • Eric,

    Sorry it took several days to get back to you.  Disabling the antivirus software did not have any impact on the CPU usage.


    Wednesday, July 8, 2009 12:26 PM
  • Hi,

    Another solution we can try is to re-import Exchange MP on your SCE server.

    Note: Please backup SCE server before re-importing MP.

    1. Open SCE console, go to Administration space - Management Packs.

    2. Delete Microsoft Exchange 2007 monitoring, Microsoft Exchange 2007.

    3. Restart SCE server.

    4. Open SCE console, reimport above two MPs.
    Friday, July 10, 2009 10:28 AM
  • Have completed the removal and re-import process.  Will update next week on status.

    Friday, July 10, 2009 3:12 PM
  • Eric,

    Removing and re-importing the MP did not seem to do anything - MonitoringHost.exe is back to consistant high CPU usage.  Any other ideas?

    Monday, July 13, 2009 3:11 PM
  • Hey guys,

    I have been following your conversation. We are having the exact same issue. I've been trying the solutions as they're presented with the same results. Its happening across multiple servers and platforms. 2k3, 2k8, VM Guest, Host, standalone boxes. The high CPU usage is affecting our exchange 2k7 cluster and SQL 2k8 cluster and this is our primary concern. 

    My question is, does SCOM 2007 R2 address these issues? If so will the trial version on the site upgrade a licensed version of SCOM 2k7 SP1?
    Monday, July 13, 2009 3:38 PM
  • I've been looking around and this guy had the same issue with SCOM 2k7 R2. It looks like the problem revolves around windwos scripting host. Updating the scripting host was Eric's last suggestion however there isn't a x64 version publicly available. I'll try to open a case with Microsoft to get the x64 version.

    Wednesday, July 15, 2009 3:14 PM
  • Trevor,

    Thanks for the udpate.  It almost seems like the problem is getting 'worse' on our Ex2007 install.  I'm having to restart the OpsMgr service every few hours now to keep the CPU usage in a normal range.  Please let me know what you find out about the x64 version of WSH 5.7.

    Wednesday, July 15, 2009 3:37 PM
  • Hi Trevor&Michael,

    As above steps didn't work, opening a case with CSS will be a better solution, as we need to perform memory dump to find out the root cause of the high CPU usage.

    So if Trevor got the problem resolved, it will be appreciated if you can come back and provide the solution.

    Thansk for your cooperation.
    Thursday, July 16, 2009 10:46 AM
  • Ok, we were able to download the hotfix (http://support.microsoft.com/default.aspx/kb/955360) for 2k3 x64. I've applied it to a few of our problem servers. I also confirmed that the WSH files versions actually updated to the versions listed on the hotfix page. I'll know tomorrow if the problem has been resolved.

    Thursday, July 16, 2009 7:41 PM
  • No love from the Windows Scripting Host Gods. Our Exchange mailbox servers were both pegged at 100% usage this morning. Strange enough is the hub transport and client access servers have not been affected at all. We also had another 2k8 hyper v host in the same condition. I'll be upgrading to SCOM 2k7 R2 today in the hopes soemthing will change. Any suggestions will be greatly appreciated.
    Friday, July 17, 2009 1:50 PM
  • I know this thread is very old, but as others may stumble upon it during a search, I think that this Blog entry may prpose a fix with an underlying issue in MSXML6:



    Wednesday, April 28, 2010 5:58 PM
  • Hi All,

         You can go with few basic ideas which may resolve your issue.

    1. If you have installed any email security antivirus software in E2K7 environment.

    • Disable the Antivirus and check the performance.
    • Add exclusions for Exchange server

    2. Check whether the online backup is running during Maintenance Interval time, If it is so Reschedule your backup timings.

    Kindly follow this below notes:


    1. By default Online Defragmentation occurs automatically as part of database maintenance process, which detects and remove database objects that are  no longer being used. Also it reduces the database's size.

    2. By default, Exchange is configured to run online defragmentation daily between 01:00 and 05:00.

    Cause: If there is any backup running during the Maintenance interval it will hit the performance of Exchange.


    To increase the efficiency of maintenance and backup processes, you may want to schedule your maintenance processes and backup operations to run at different times.

    To schedule database defragmentation, use one of the following methods:

    1. To schedule database defragmentation for an individual database, use the Maintenance interval option on the Database tab of a mailbox store or of a public folder store object to configure the maintenance interval.

    2.To schedule database defragmentation for a collection of mailbox stores and of public folder stores, use the Maintenance interval option on the Database (Policy) tab of a mailbox store or of a public folder store policy to configure the maintenance interval.


    Reference: http://support.microsoft.com/kb/328804

    Wednesday, August 3, 2011 6:38 PM