Script or Executable Failed to run
Any one know about this alert .. i am only left with this error rest my network is all upto date... Please help if some one has solution to this: ------------------------------------------------------------------------- Script or Executable Failed to run Alert Description Source: CSR-02.ordernet Forced to terminate the following process started at 9:09:49 AM because it ran past the configured timeout 30 seconds. Command executed: "C:\WINDOWS\system32\cscript.exe" /nologo "CheckWUAgentConfig.vbs" OL-SRV-BACKUP_MG Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 2\1193\ One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.Essentials.CheckWUAgentConfigMonitor Instance name: CSR-02.ordernet Instance ID: {6D97405D-2200-A800-79E6-E7E2931C1FB0} Management group: OL-SRV-BACKUP_MG Path: CSR-02.ordernet\CSR-02.ordernet Alert Rule: Alert on Failed Batch Responses Created: 5/27/2008 9:10:47 AM Knowledge: View additional knowledge... Resolution: 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. 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 params, policy, timeout) could be wrong causing no output or timeout. 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. Summary: The Health Service was attempting to run an executable and was unable to create the process. This may affect some monitoring or discovery. Related Links: No related links were found for this problem. Hide knowledge
May 28th, 2008 8:56pm

Hi,Did you patch the SCE server with SP1?If not, please donwload and install SP1,then check whether the error will occur:Download details: System Center Essentials2007 SP1 Upgrade (x64 & x86),Eric Zhang
Free Windows Admin Tool Kit Click here and download it now
May 30th, 2008 1:46pm

Hi,To prevent the rule, you can disable the rule, please do the following steps to change the timeout:1. Open SCE console, navigate to Monitoring space.2. Click "Active Alert". right click the specific error. choose "Override" - "Disable the rule" - "For the obejct:"--------------------Regards,Eric Zhang
June 2nd, 2008 3:34pm

Hi Imran,The error indicated that the script is failing with the timeout. After my research, this script is contained within ManagementPack Objects/Monitors/Agent/Entity Health/Availability/Managed Computer update serverconfiguration monitor/This monitor belongs to System Center Essentials 2007 Management Pack which is sealed, that's the reason why we cannot modify the time out value..I'd like to confirm whether this error occured on several clients or just one specific client?--------------------Regards,Eric Zhang
Free Windows Admin Tool Kit Click here and download it now
June 10th, 2008 10:43am

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

Other recent topics Other recent topics