SCOM Troubleshooting: constant high cpu usage of monitoringhost.exe and event 3006



On a couple of Exchange 2010 servers monitored by Operations Manager, a constantly high CPU usage is reported for the monitoringhost.exe process. Restarting the agent including clearing the cache do not fix the issue. Meanwhile, the application log is being flooded with events with id 3006 and source EvntAgnt.


The solution is to restart the SNMP service on the affected machine, this will stop the eventlog-flooding and drop the monitoringhost’s CPU usage to normal levels.

The exact same issue and solution where blogged a long time ago by Cameron Fuller for a Server 2003 system, but the issue can apparently also occur on a Server 2008 R2 SP1 machine.

This entry was posted in #scom, #sysctr. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s