• Management Pack:  SCOM 2016
  • MP Version:  1.0
  • Released:  10/19/2018
  • Publisher:  Microsoft

Workflow Initialization: Failed to start a process or script Rule

  • ID:  Microsoft.SystemCenter.BatchResponseModule.AlertOnFailedCreateProcess
  • Description:  This rule generates alerts when a rule or monitor attempts to execute a process and the process cannot be started.
  • Target:  Health Service
  • Enabled:  Yes

Overridable Parameters

Parameter Name Default Value Description Override
Priority 1  
Severity 1  

Run As Profiles

Name
Default

Alert Details

Message Priority Severity
Workflow Initialization: Failed to start a process or script Medium Warning

Rule Knowledgebase

Summary

The System Center Management Health Service was attempting to run an executable and was unable to create the process.

This may affect some monitoring or discovery.

Causes

This can be caused by:

  • The executable could not be found.

  • The computer does not have enough resources (for example; memory) to run the executable.

  • The script extension is not properly registered.

Resolutions

The alert description and context has information indicating which rule or monitor failed. The following link will display all events indicating a failure to run the executable:

View Batch Response Events

After reviewing the error in the context, check:

That the path to the executable exists on the computer.

That the computer is not over utilized.

  • Check Task Manager to see if there is enough free memory.

  • Check Task Manager to see if there are any processes consuming all the CPU.

  • To ensure that all script extensions are registered, follow the steps in the “Let me fix it myself” section of Knowledge Base article 949140 (http://go.microsoft.com/fwlink/?LinkId=181825).

Note that if the executable could not be found, the rule is misconfigured. Open the rule was executing the response and update the rule configuration with the right path to the executable or install the executable on the target system.

Lastly, you should check the working directory and application file path for errors and also verify the action account has access to the application/directory.

External References
This rule does not contain any external references.

See Also for SCOM 2016 Management Pack


Downloads for SCOM 2016 Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED