locked
Power Shell Script failed to run RRS feed

  • Question

  • Hi

    I think this alert is due to a faulty management pack, specifically in the module mentioned. I'm trying to investigate further. We have this on multiple servers and across different roles. 

    How do I get access to this script so I can find out what it is timing out on? Where's the output of this script kept? 

    I'm still new to SCOM2012 and think while its and improvement its still got bugs left over from 2007.


    Alert description: Forced to terminate the following PowerShell script because it ran past the configured timeout 300 seconds.

    Script Name:    CheckMaxConcurrentAPI.ps1
    One or more workflows were affected by this.
    Workflow name: Microsoft.Windows.Server.2008.MaxConcurrentAPI.Monitor
    Instance name: Microsoft Windows Server 2008 R2 Enterprise
    Instance ID: {81CDE473-D76E-3459-58B1-5DB67AC6B574}
    Management group: OM2012

    Tuesday, March 24, 2015 1:33 AM

Answers

  • This workflow came from Windows Server 2008 Max Concurrent API Monitor.
    The most likey cause of tmeout is due to permission issue.
    Please make sure that your default action account has the following right on local mcahine
    • Member of the local users group
    • Member of the local Performance Monitor Users group
    • Granted Log On Locally rights
    Beside, you can find the script on
    SCOM 2012 R2
    c:\Program Files\Micosoft Monitoring Agent\Agent\Health Service state
    SCOM 2012
    c:\program Files\System Center Operations Manager\Agent\Health Service state

    Roger

    • Proposed as answer by Yan Li_ Tuesday, March 31, 2015 9:06 AM
    • Marked as answer by Yan Li_ Tuesday, April 7, 2015 7:43 AM
    Tuesday, March 24, 2015 3:59 AM
  • Hi,

    Please check this ReSearch This KB article: http://www.systemcentercentral.com/research-this-kb-max-concurrent-api-reached-alert/


    http://OpsMgr.ru/

    • Proposed as answer by Yan Li_ Tuesday, March 31, 2015 9:06 AM
    • Marked as answer by Yan Li_ Tuesday, April 7, 2015 7:43 AM
    Tuesday, March 24, 2015 4:14 AM

All replies

  • This workflow came from Windows Server 2008 Max Concurrent API Monitor.
    The most likey cause of tmeout is due to permission issue.
    Please make sure that your default action account has the following right on local mcahine
    • Member of the local users group
    • Member of the local Performance Monitor Users group
    • Granted Log On Locally rights
    Beside, you can find the script on
    SCOM 2012 R2
    c:\Program Files\Micosoft Monitoring Agent\Agent\Health Service state
    SCOM 2012
    c:\program Files\System Center Operations Manager\Agent\Health Service state

    Roger

    • Proposed as answer by Yan Li_ Tuesday, March 31, 2015 9:06 AM
    • Marked as answer by Yan Li_ Tuesday, April 7, 2015 7:43 AM
    Tuesday, March 24, 2015 3:59 AM
  • Hi,

    Please check this ReSearch This KB article: http://www.systemcentercentral.com/research-this-kb-max-concurrent-api-reached-alert/


    http://OpsMgr.ru/

    • Proposed as answer by Yan Li_ Tuesday, March 31, 2015 9:06 AM
    • Marked as answer by Yan Li_ Tuesday, April 7, 2015 7:43 AM
    Tuesday, March 24, 2015 4:14 AM
  • This looks spot on. I'm still investigating this and will update with findings in about a week.
    Tuesday, March 31, 2015 2:58 AM
  • Checking another server that has the issue, the Microsoft Monitoring Agent service is logged on as Local System account.  A lot of other servers are configured this way.



    • Edited by incr42 Wednesday, April 15, 2015 1:16 AM
    Wednesday, April 15, 2015 1:15 AM