The Windows Monitor Agent is experiencing very high processor utilization. This is likely to occur on domain controllers, in particular.
This behavior occurs if the operating system has very busy NT Event Logs and there are any NT Event based Monitor Solution rules enabled. The Monitor Agent architecture for parsing NT Event Logs cannot keep up with the activity on the machine.
This is a defect and has been submitted to development.
The Monitor Agent architecture has been better optimized to handle busy NT Event Logs in the SP5 release of Monitor Solution for Servers.
Monitor Solution for Servers SP4 HF1 7.0.7722 (and previous versions)
AeXMetricProv.exe consumes high CPU on machines with very busy NT Event logs
Imported Document Id
This is machine translated content
Login to Subscribe
Please login to set up your
For security reasons, your link to this document has expired. Please click on the attachment link to access this file.
The attachment that you are looking for no longer exists.
There has been an issue retrieving your attachment. Please try again.
Didn't find the article you were looking for? Try these resources.