locked
Operations Manager failed to start a process RRS feed

  • Question

  • Hi,

    We are on SCOM 2012 SP1.

    I am getting alert daily for every monitored client machine "Opeartions Manager failed to start a process"

    what could be the issue?

    
    Monday, March 10, 2014 10:55 AM

Answers

  • Hi

    To figure out which rule causes this error run...

    Get-SCOMRule -Name MomUIGeneratedRule767.... <= Use here the complete Workflow Name from the description.

    Check which instances / client causes this error by running

    Get-SCOMMonitoringObject -ID 8FB8766..... <= Use here the complete GUID from Instance ID from the alert description.

    The check the script and run it in a command window on that Client / Server as the command is written in the alert description. This should give you some more details why this error happens...

    Cheers,

    Stefan


    Blog: http://blog.scomfaq.ch

    • Marked as answer by Juke Chou Monday, March 24, 2014 3:08 AM
    Monday, March 10, 2014 8:03 PM

All replies

  • Could be a datatype issue which is overflowing, check out the line 20 in PercentNetworkUtilisationScript.vbs

    Faizan

    Monday, March 10, 2014 1:03 PM
  • To fix your issue, you can refer below link

    http://nicolewelchscom.wordpress.com/2013/10/01/operations-manager-failed-to-start-a-process/


    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"

    Monday, March 10, 2014 2:56 PM
  • May be you'll have to use conversion functions in line 20 which is holding the variables, for sure the script is hanging there and getting timedout

    Faizan

    Monday, March 10, 2014 7:22 PM
  • Hi

    To figure out which rule causes this error run...

    Get-SCOMRule -Name MomUIGeneratedRule767.... <= Use here the complete Workflow Name from the description.

    Check which instances / client causes this error by running

    Get-SCOMMonitoringObject -ID 8FB8766..... <= Use here the complete GUID from Instance ID from the alert description.

    The check the script and run it in a command window on that Client / Server as the command is written in the alert description. This should give you some more details why this error happens...

    Cheers,

    Stefan


    Blog: http://blog.scomfaq.ch

    • Marked as answer by Juke Chou Monday, March 24, 2014 3:08 AM
    Monday, March 10, 2014 8:03 PM