Getting lots of Script Failed To Run alerts? WMI Probe Failed Execution? Backward Compatibility Script Error?
<!--[if lt IE 9]>
<![endif]-->
Comments
Anonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
I have some machines that run very heavy processes for several hours each day. I have noticed those machines report many of these errors, more of the script failures than WMI issues, and they are all time stamped during the heavy resource use times. Is there a way to keep the scripts and WMI queries from running while the server is low on available resources to see if this quiets down the failures? Great Post, Thanks!Anonymous
January 01, 2003
James - I would run a procmon and capture the cscript.exe processes and scripts they are running, and record what scripts are running, and when. Armed with this data - it would help you solve the problem, as you might not even need all that stuff running all the time, or as frequent. Additionally, you could place the instances of classes which have script workflows targeting them, into scheduled maintenance mode, for the known busy periods, accepting the fact that whatever these scripts do - they wont be doing, during these busy times.Anonymous
January 01, 2003
Hi keven, it's my first time on your awsome blog. (excuse my poor english, i'm French Canadian) I know this is a pretty old post, but i was wondering if there is any fix for those types of errors for 64bits OS Windows Server 2008 sp2. The 5 alerts above are also the top 5 of my site. I monitor a lot of 2008 windows servers. Thanks.Anonymous
January 01, 2003
Click the "show for all platforms" in the download - there is one for x86 and one for x64.Anonymous
January 01, 2003
Hi Patrick - The fixes are the same for any OS - look at the alert - what the alert description describes as the reason, then look at how often it is happening. From this - you should be able to determine if this is a transient issue, or an indication of a serious server health problem where scripts aren't running, or WMI is unhealthy.Anonymous
January 01, 2003
The comment has been removedAnonymous
July 24, 2009
Thanx for this post. I'm going to try this. This needs a couple of days to find out if it work.Anonymous
August 18, 2009
The comment has been removedAnonymous
November 11, 2009
I get quite a few of these as well, even after R2 was installed; 2003 as well as 2008 servers. Most of them seem to be related to Health VBS scripts. Does anybody have any ideas to get these corrected? Is this indicative of a true server performance issue or a matter of how the MPs were written? If it's the MPs, I would have expected that MS to have known about this and corrected it by now.Anonymous
November 12, 2009
Is it just me, or does the hotfix ONLY apply to i386? How can I update WSH to version 5.7 for 64bit OS Windows 2003?Anonymous
June 11, 2010
Awesome document! I merely stumbled upon this. I don't know how many searches I have done on WMI issues and came up with completely trivial responses "Restart WMI", Reboot the system" etc. The explanation of how to test proved to be a huge help and teh Registry mods I've never seen before in any documentation.Anonymous
March 01, 2011
Kevin, this is right on and it helps to have the process roughed in. Is there a script one could run on the ill server which would either fix or at least diagnose the problem? I have too many agents with these sorts of errors to fix them by hand. The flow of these events into our scom environment is affecting the overall performance of SCOM. Fixing the individual problem servers is an ongoing and apparently never ending process. Is there a way to set the event collection to do it less frequently or to summarize the data flowing into SCOM? I am considernig disabling the "Collect WMI Probe Module Events" rule. What kinds of reports, rules, monitors, etc. would "break" if the event data stops flowing in?Anonymous
September 15, 2011
Can anyone help me in creating simple (basic) SCOM monitor or rule using WMI event alert as every time i try to make one it fails . A basic WMI query is requestedAnonymous
September 04, 2012
Can we create a WMI health monitor to clearly idently the root cause? And then ideally suppress the other alerts....Anonymous
February 07, 2013
The comment has been removedAnonymous
March 12, 2013
Hello, I have a related error with scom 2012 Context Date and Time: 12.03.2013 14:30:29 Log Name: Operations Manager Source: Health Service Modules Event Number: 10363 Level: 2 Logging Computer: SRV10P120.ad.int.kkh.de User: N/A Description: Das Modul konnte die WMI-Daten nicht auflisten. Fehler: 0x80041032 Details: Call cancelled Mindestens ein Workflow ist hiervon betroffen. Workflowname: Microsoft.Windows.2008.Cluster.NetworkInterface.StateMonitoring Instanzname: Private Cluster Network Instanz-ID: {7FEC9A23-1B0A-522A-BCF5-D32F69BA1E7B} Verwaltungsgruppe: MGKKH Event Data: < DataItem type =" System.XmlData " time =" 2013-03-12T14:30:29.4768481+01:00 " sourceHealthServiceId =" 7DCE0BA6-1903-23B9-676B-C9592B9E07DB " > < EventData > < Data > MGKKH </ Data > < Data > Microsoft.Windows.2008.Cluster.NetworkInterface.StateMonitoring </ Data > < Data > Private Cluster Network </ Data > < Data > {7FEC9A23-1B0A-522A-BCF5-D32F69BA1E7B} </ Data > < Data > 0x80041032 </ Data > < Data > Call cancelled </ Data > </ EventData > </ DataItem > Do you have any idea. Repeat count is 25 until yet. Thanks and regards.Anonymous
July 07, 2013
Same Problem on 2008 R2.Anonymous
November 12, 2014
See http://blogs.technet.com/b/kevinholman/archive/2009/01/27/which-hotfixes-should-i-apply.aspx for Common related Windows Operating System Hotfixes:
2954185, 2790831, 2692929, 2547244 etcAnonymous
May 16, 2016
It would be great, if we can have the latest/updated info for the same issues on SCOM 2012 SP1