SCOM 2007 Script error
Hi,
we are running SCOM 2007 on a 2008 R2 box and are getting the following error regularly from some of our monitored servers
Alert: Script or Executable Failed to run
Source: xxxxxxxxxxx
Path: xxxxxxxxxxx
Last modified by: System
Last modified time: 15/09/2011 3:12:43 PM Alert description: Data was found in the output, but has been dropped because the
Event Policy for the process started at 3:07:19 PM has detected errors.
The 'ExitCode' policy expression:
[^0]+
matched the following output:
259
Command executed:
"C:\WINDOWS\system32\cscript.exe" /nologo "CollectLogicalDiskStatistics.vbs" false
Working Directory:
D:\program files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 4\202\
One or more workflows were affected by this.
Workflow name: Windows.LogicalDrives.CollectVolumeSize.Rule
Instance name: S:
Instance ID: {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}
Management group: SunRice
Many thanks for any info.
September 15th, 2011 9:10am
Hi,
Based on my research, I would like to suggest the following:
1.
Regarding the script error, please try the methods in the following post:
Getting lots of Script Failed To Run alerts? WMI Probe Failed Execution? Backward Compatibility Script Error?
http://blogs.technet.com/b/kevinholman/archive/2009/06/29/getting-lots-of-script-failed-to-run-alerts-wmi-probe-failed-execution-backward-compatibility-script-error.aspx
2.
Check Ant-virus exclusions:
Antivirus Exclusions for MOM and OpsMgr
http://blogs.technet.com/b/kevinholman/archive/2007/12/12/antivirus-exclusions-for-mom-and-opsmgr.aspx
Leon Liu - Technical Lead
Free Windows Admin Tool Kit Click here and download it now
September 20th, 2011 8:12am
Hi,
The first suggestion you made referred to Hotfixes that were designed for Windows 2003 and will not run on 2008 R2. Also the exclusions were already in place for the Anti Virus.
Also do not appreciate you marking yourself as answered the question when the suggestions had not been tried and do not solve the issue
October 17th, 2011 6:01pm
what is drive S: size? just curious if it is greater/less than 2TB.
Free Windows Admin Tool Kit Click here and download it now
October 17th, 2011 6:10pm
Drive S: does not exist on that server. It has existed on older Windows 2003 servers as a LOGS drive of usually around 40GB.
October 17th, 2011 8:02pm
Hi
On the server itself, can you do the following:
- Start, Run, WBEMTest (this fires up the windows management test utility)
- Connect to the root\cimv2 namespace (click the connect button and this is the default)
- click query and run the following SELECT * FROM Win32_LogicalDisk
This should return the logical disks - just check to see if an S: drive is returned.
Cheers
GrahamNew SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
November 7th, 2011 4:28am
Hi
On the server itself, can you do the following:
- Start, Run, WBEMTest (this fires up the windows management test utility)
- Connect to the root\cimv2 namespace (click the connect button and this is the default)
- click query and run the following SELECT * FROM Win32_LogicalDisk
This should return the logical disks - just check to see if an S: drive is returned.
Cheers
GrahamNew SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/
November 7th, 2011 12:27pm