dns2003discovery.vbs script or executable failed to run

if you’re seeing an error similar to this --

The process started at 2:58:15 AM failed to create System.Discovery.Data. Errors found in output:

C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 2\4484\DNS2003Discovery.vbs(478, 9) Microsoft VBScript runtime error: Type mismatch

Command executed: "C:\WINDOWS\system32\cscript.exe" /nologo "DNS2003Discovery.vbs" {C8655A28-E27E-C6ED-B158-8569219A71A6} {641B9BD1-C4B4-E747-235B-362A0629EC54} <YOUR-DC-FQDN> false

 

it may be environmental as is the case for me.  at some point in the past, we had dns running on all of our domain controllers.  once we went to 2003, we started removing it from the nodes where it wasn’t needed.  we turned it off on the ones where it wasn’t required.  unfortunately, it leaves the remnant namespace in wmi.

on a system where this occurs, the following query will return an empty response:

select * from microsoftdns_server

 

with a response like this:

consequentially, this is the query that’s called in the dns discovery script.  and of course, on a working system, it returns the FQDN of the dns server in question.  fortunately for me, i can override the discovery fairly safely without concern that i’ll miss anything else.

examining the failure line (478, 9) puts us inside the DoDiscovery function.  since objServer is empty, it’s going to fail.  i think an “if isnull” would correct the problem here.

Function DoDiscovery(ByVal TargetComputer, ByVal oDiscoveryData)
    ...
    
' If IsNull  <--- maybe here would help... 
    For Each objServer In colServers
        Set objInstance = oDiscoveryData.CreateClassInstance("{83556DC0-78A0-1B5E-8947-509A5115EAB4}")
        Call objInstance.AddProperty("{E4F02B95-59EC-CA14-1A36-107F6ADB84D0}", objServer.EventLogLevel)
        Call objInstance.AddProperty("{B95C9A9B-1C3D-A19A-F6D1-7CAF6A98CE67}", TargetComputer)
    ...

---

marcusoh.blogspot.com