How do I troubleshoot high CPU utilization issues with the NetIQmc.exe process? (NETIQKB41388)

The NetIQmc.exe (NetIQmc) process is consuming a large amount of CPU resources.

Windows Task Manager periodically indicates CPU utilization spikes of over 90% for the NetIQmc.exe process.

The following list includes troubleshooting tips for CPU utilization spikes caused by the NetIQmc.exe process:

• Ensure that your antivirus software is not configured to scan the AppManager installation path.
• Ensure that backups are not running against the client local repository at the time of the CPU spike.  If you find that backups are running, disable backups for the NetIQ directory.
• Verify that AppManager jobs have staggered run times:
  
  
  1. Open the AppManager Operator Console.
  2. Select the server experiencing the CPU utilization issue.
  3. Right-click the server and select Troubleshooter > Job Info > Job Detail.
  4. Review the jobs listed to verify that their schedules are not running at the same time, and the individual schedules are not overlapping themselves.
  5. If necessary, job iteration schedules can be "staggered" by setting the following registry value on each agent machine:
     
     HKEY_LOCAL_MACHINE\Software\NetIQ\AppManager\4.0\NetIQmc\Config\JobSpacingInterval
     
     The JobSpacingInterval value should be specified in seconds (for example, 5). Once the agent services are restarted, this adds a timed stagger in each job start to not run at the exact same time, even if they have the same run schedule.  This lowers the overall system resources being used to run am AM job.  For more information on this value, see the AppManager Administrator's Guide
     or the product Help.
     
     
• Orphaned jobs can also cause CPU spikes.  To remove these orphaned jobs, perform a cold start on the services:
  
  1. From the client machine, start the Services application.
  2. Select the Client Resource Monitor service.
  3. On the Action menu, click Properties.
  4. Click Stop to stop the service.
  5. Type -oa in the Startup parameters: field and click Start to restart the service.
  6. Click OK to close the Properties window.
  7. Repeat Steps 2 through 6 for the Client Communication Manager service.
     
• Ensure that third party services running on the client machine are not conflicting with AppManager port communication.  AppManager should be the only application communicating on 9999 and 9998 (the ports you specified during the AppManager installation or configuration).
• Ensure all modules are up-to-date on the agent machine as well the running jobs.

Formerly known as NETIQKB41388