Operations Manager failed to start a process

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?


March 10th, 2014 7:01am

Could be a datatype issue which is overflowing, check out the line 20 in PercentNetworkUtilisationScript.vbs
Free Windows Admin Tool Kit Click here and download it now
March 10th, 2014 9:09am

To fix your issue, you can refer below link

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

March 10th, 2014 11:02am

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
Free Windows Admin Tool Kit Click here and download it now
March 10th, 2014 3:28pm

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

March 10th, 2014 4:08pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics