Error alerts from the DNS MP – script failures, WMI Probe failed?

re: Error alerts from the DNS MP – script failures, WMI Probe failed?

Scott Breen — Mon, 22 Oct 2012 04:26:30 GMT

Thanks Kevin. Those alerts were really starting to annoy me. I never would have found the solution without this article. Yet to see if it solves all servers, but I'm hopeful!

re: Error alerts from the DNS MP – script failures, WMI Probe failed?

Nicole Welch — Tue, 11 Sep 2012 20:41:53 GMT

I'm getting the same error as Bryan on about 10% of my servers...

Event Type: Warning

Event Source: Health Service Modules

Event Category: None

Event ID: 11052

Date: 9/11/2012

Time: 3:18:12 PM

User: N/A

Computer: []

Description:

Module was unable to convert parameter to a double value

Original parameter: '$Data/Property[@Name='EventLogLevel']$'

Parameter after $Data replacement: ''

Error: 0x80020005

Details: Type mismatch.

One or more workflows were affected by this.

Workflow name: UIGeneratedMonitor1dcc5008a0b240b4bc900ca8fea84206

Instance name: []

Instance ID: {1B2459E9-E4CC-5F8E-4C5C-1582DDC253C4}

Management group: CCC_OpsMgr

Any idea why this would arise? My event logging level is to to NULL on these machines.

re: Error alerts from the DNS MP – script failures, WMI Probe failed?

Neil McLoughlin — Mon, 12 Sep 2011 14:24:53 GMT

This issue has also been drivign me nuts for weeks aswell! Thanks for the work around, seems to work perfectly

re: Error alerts from the DNS MP – script failures, WMI Probe failed?

Mike Celone — Thu, 24 Mar 2011 14:57:21 GMT

Thank you! This has been driving me nuts since we implemented the DNS management pack. All our Windows 2003 DCs with DNS were giving us these errors. Without this fix the management pack is almost useless. I understand Windows 2003 is old at this point but Microsoft should really fix the root cause of the issue since it makes the DNS Management pack almost useless. At least provide a hotfix for companies using SCOM to deploy...

re: Error alerts from the DNS MP – script failures, WMI Probe failed?

Bryan C. — Thu, 30 Dec 2010 18:53:42 GMT

I implemented the monitor described in the blog post. Seems I've traded one unwanted alert for another. Now I get this alert:

Generic Performance Mapper Module Failed Execution

Module was unable to convert parameter to a double value

Original parameter: '$Data/Property[@Name='EventLogLevel']$'

Parameter after $Data replacement: ''

Error: 0x80020005

Details: Type mismatch.

One or more workflows were affected by this.

Workflow name: UIGeneratedMonitor77a23b731c894ea182b44113e8f657de

Instance name: host.domain.com

Instance ID: {9C068BE3-4F78-A2B0-F224-1F9F12C9B424}

Management group: MgmtGroupName

The workflow name was validated to map back to the custom DNS monitor.

Any suggestions?

re: Error alerts from the DNS MP – script failures, WMI Probe failed?

Lumoder — Thu, 28 Oct 2010 12:55:48 GMT

Kevin!

Thanks a lot for your MP! It really works for me!

re: Error alerts from the DNS MP – script failures, WMI Probe failed?

Kevin Holman — Fri, 15 Oct 2010 12:41:19 GMT

1. There are several reasons, but at this time - Microsoft does not have plans to fix this specific TLS slot leak from the DNS WMI namespace provider. Since this only affects Windows 2003 in rare cases where something queries the DNS WMI namespace on frequent cycle, but less often than 5 minutes, the workarounds resolve the issue. SImply increase the frequency.

2. No - you do not need to Migrate to 2008 to resolve this - workarounds have been provided. However, there are many benefits to migrating to Windows 2008 R2 so that is always recommended.

Suggested workaround is always applicable. If you dont have MOM or SCOM or some other monitoring tool constantly querying the WMI DNS namespace provider - then the issue WILL NOT surface. If you feel for some reason you are impacted without a monitoring tool in place - you could still create your own solution for this using task scheduler.

re: Error alerts from the DNS MP – script failures, WMI Probe failed?

The Sjoerd — Fri, 15 Oct 2010 09:13:19 GMT

1) is this issue being picked up by MS , and will there be a update/fix for it ?.

2) Do we need to migrate to another platform eg 2008 to resolve this issue ?

suggested mp workaround isnt applyable in some cases. eg , no mom or scom, i hope MS takes action on this issue.

re: Error alerts from the DNS MP – script failures, WMI Probe failed?

Kevin Holman — Fri, 01 Oct 2010 12:27:20 GMT

Alex - this is still Server 2003 then - and has the leak in WMI. You MUST use something like my MP to keep the provider from unloading, or you will be affected. This is a textbook example. You can hotfix and patch and tweak to your hearts content - you will not solve the root cause. The root cause is that when the DNS WMI provider unloads after a period of inactivity - it leaks a TLS slot. If you use my example MP, this will qury the provider enough to keep it from unloading, and you will work around the issue in the Windows WMI provider.

re: Error alerts from the DNS MP – script failures, WMI Probe failed?

Lumoder — Fri, 01 Oct 2010 08:06:11 GMT

Kevin,

All my DNS servers are Windows 2003 R2 and I get this error from all this servers. I have 3-6 WMIPRVSE processes with 5-20 MBs of memory. I have upgraded SCOM to R2 version adn will try your MP on this version too - on SCOM 2007 it has no effect.