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