none
SCOM 2012 R2 agent CPU spike issue RRS feed

  • Question

  • Hi All,

    We are seeing frequent high CPU spike in our agent servers running Windows Server 2008 R2. When checking with perfmon, it was found that the DCOM service is triggering disk performance collection for the SCOM agent and the CPU spike doesn't come down after the action is completed. We are currently in SCOM 2012 R2 and the agents are in UR2 version.

    NOTE: We see this issue on IIS, SharePoint and SQL servers mostly

    Is there any patch for Windows Servers that needs to be installed or what is it that we can do to fix this issue

    Thanks,

    Shreeram


    Thanks, Shreeram

    Tuesday, March 15, 2016 3:33 AM

Answers

  • Hi All,

    We have identified the root cause of the CPU spike. There was no exclusion policy set for the antivirus to exclude the health service state folder of SCOM agent, which results in a deadlock. We tried disabling the antivirus to test this theory and the CPU utilization came down considerably.

    Many thanks to Roger & Yan for their assistance


    Thanks, Shreeram


    • Edited by Shreeram S Wednesday, March 16, 2016 6:10 AM
    • Marked as answer by Shreeram S Wednesday, March 16, 2016 6:20 AM
    • Unmarked as answer by Shreeram S Wednesday, March 16, 2016 6:21 AM
    • Marked as answer by Yan Li_Moderator Friday, March 18, 2016 6:58 AM
    Wednesday, March 16, 2016 6:09 AM

All replies

  • Please check the following hotfixs
    1)The WMI service and the WMI providers stop responding when you use WMI performance classes to monitor performance on a computer that is running Windows 7 or Windows Server 2008 R2
    https://support.microsoft.com/en-us/kb/2547244
    2) The CPU usage of an application or a service that uses MSXML 6.0 to handle XML requests reaches 100% in Windows Server 2008, Windows Vista, Windows XP Service Pack 3, or other systems that have MSXML 6.0 installed
    https://support.microsoft.com/en-us/kb/968967
    Roger
    Tuesday, March 15, 2016 4:07 AM
  • Hello,

    In addition, I would like to suggest you also try to clear health service state and caches for those agent servers and check the result.

    Please patch your servers with needed updates and hotfixs.

    Regards,

    Yan Li


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, March 15, 2016 8:41 AM
    Moderator
  • Hi All,

    We have identified the root cause of the CPU spike. There was no exclusion policy set for the antivirus to exclude the health service state folder of SCOM agent, which results in a deadlock. We tried disabling the antivirus to test this theory and the CPU utilization came down considerably.

    Many thanks to Roger & Yan for their assistance


    Thanks, Shreeram


    • Edited by Shreeram S Wednesday, March 16, 2016 6:10 AM
    • Marked as answer by Shreeram S Wednesday, March 16, 2016 6:20 AM
    • Unmarked as answer by Shreeram S Wednesday, March 16, 2016 6:21 AM
    • Marked as answer by Yan Li_Moderator Friday, March 18, 2016 6:58 AM
    Wednesday, March 16, 2016 6:09 AM