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

Workflow Initialization: Failed to start a workflow that runs a process or script Rule

  • ID:  Microsoft.SystemCenter.BatchResponseModule.AlertOnFailedInitialization
  • Description:  This rule generates alerts when failed to start a workflow that runs a process or script.
  • 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 workflow that runs 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 antivirus software on the computer blocking Visual Basic scripts or Java scripts. The following link is a link to the KB article regarding this issue.

  • The script extension is not properly registered.

Antivirus software blocking script execution

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.

The antivirus software is not blocking scripts from running.

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).

Check the error information in the event or alert context for the script path and name. There could be a problem with the script not handling an error correctly and exiting. If the script exits without outputting the data that is expected (e.g. property bag data), this error is raised.

Another error can be caused by the misconfiguration of the workflow executing this script. The configuration (script parameters, policy, timeout) could be wrong causing no output or timeout.

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