Partager via

Script or Executable Failed to run

  • Article

A reason for this could be the antivirus software blocks script execution in System Center Operations Manager

 

You will receive warnings as the following:

 

Script or Executable Failed to run

The process started at 10:41:22 AM failed to create System.PropertyBagData, no errors detected in the output. The process exited with 1

Command executed: "C:\WINDOWS\system32\cscript.exe" //nologo "C:\Program Files\System Center Operations Manager <version>\Health Service State\Monitoring Host Temporary Files 73\3456\ScriptName.vbs" 

Working Directory: C:\Program Files\System Center Operations Manager <version>\Health Service State\Monitoring Host Temporary Files 73\3456\

One or more workflows were affected by this.

 

Cause:

This problem occurs because some antivirus software blocks Visual Basic scripts or Java scripts.

 

Resolution:

To resolve this problem, verify that your antivirus software is not blocking scripts from running.

Comments

  • Anonymous
    January 01, 2003
    Is there another reason this may happen? I've gotten this message on machines where no av is installed and on machines where i've explicitly allowed *.vbs, cscript.exe and wscript.exe to be executed.

  • Anonymous
    January 01, 2003
    The comment has been removed