locked
SCOMpercentageCPUTimeCounter.vbs RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    The following alert has generated by scom2012 can anybody tell me what is the solution of it.

    Forced to terminate the following process started at 10:04:33 AM because it ran
    past the configured timeout 300 seconds.


    Command executed:
    "C:\Windows\system32\cscript.exe" /nologo "SCOMpercentageCPUTimeCounter.vbs"
    ServerNamefalse 3
    Working Directory: C:\Program Files\System
    Center Operations Manager\Agent\Health Service State\Monitoring Host Temporary
    Files 58\555\


    One or more workflows were affected by this.



    Workflow name:
    Microsoft.SystemCenter.HealthService.SCOMpercentageCPUTimeCollection

    Instance
    name: ServerName

    Instance ID:
    {578A25B3-9F33-B80D-6B73-EC58D6EF8BA0}

    Management group: SCOM2012

    Tuesday, January 8, 2013 7:15 AM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    Kevin Holman explains this here:

    http://blogs.technet.com/b/kevinholman/archive/2010/02/23/a-new-script-error-scompercentagecputimecounter-vbs-invalid-class.aspx

    Cheers

    Graham

    Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

    • Marked as answer by Cloud_TS Tuesday, January 22, 2013 2:16 AM
    Tuesday, January 8, 2013 7:46 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks kevin for the reply i have go through your document but that document is not for me because in that there is INVALID CLASS is not in my alert i am also attaching my alert again for your reference.

    Kelvin Alert

    C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 2\4885\SCOMpercentageCPUTimeCounter.vbs(125, 5) SWbemRefresher: Invalid class

    My Alert

    Forced to terminate the following process started at 10:04:33 AM because it ran
    past the configured timeout 300 seconds.


    Command executed:
    "C:\Windows\system32\cscript.exe" /nologo "SCOMpercentageCPUTimeCounter.vbs" ServerNamefalse 3
    Working Directory: C:\Program Files\System Center Operations Manager\Agent\Health Service State\Monitoring Host Temporary Files 58\555\

    Regards,

    Tuesday, January 8, 2013 1:40 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi, first try to execute this command from the server infected
    • Marked as answer by Cloud_TS Tuesday, January 22, 2013 2:16 AM
    Thursday, January 10, 2013 6:56 PM