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 script extension is not properly registered.
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.