We’ve been getting a few calls on this here in product support so I think it’s probably worth a quick mention just in case you happen to run into it too. Usually the call will start out where the customer says he or she is running System Center Operations Manager 2007 and receiving Alerts (Warning severity) similar to 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 2007\Health Service State\Monitoring Host Temporary Files 73\3456\ScriptName.vbs"
Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 73\3456\
One or more workflows were affected by this.
And you know what usually turns out to be the problem? If you read the title of this post then you probably do but I’ll say it again anyway. Usually it’s anti-virus software that for whatever reason is blocking VBS or JS scripts. Fortunately the solution to this is easy: Configure your anti-virus software to not block the OpsMgr scripts from running. How you do that will depend on the A/V software you use so if you’re unsure you’ll probably have to check the documentation for your particular anti-virus product.
I hope you don’t run into this yourself but if you do at least maybe this will help save you some time tracking down the problem.
J.C. Hornbeck | Manageability Knowledge Engineer