if i issue "!wmi h= select * from Win32_Product", collector debugger comes back with "Empty Value Set". Can someone elaborate on why? Win32_Product is very widely used to collect installed applications on a windows host.
This same query returns results from wbemtest.exe
Hey there, what collector version are you running? I'm not seeing the same issue .
you point out the command:
!wmi h= select * from Win32_Product
Are you putting in your h={hostname} ??
>>!wmi h=servername.domain.local select * from Win32_Product
>>>>>>>
SKUNUMBER=>
INSTALLDATE2=>
REGOWNER=>0
LOCALPACKAGE=>C:\Windows\Installer\4f5a5ca6.msi
PRODUCTID=>none
PACKAGECACHE=>C:\Windows\Installer\4f5a5ca6.msi
PACKAGECODE=>{C85B3D46-A06B-4DB8-864B-E0788CE9519D}
DESCRIPTION=>LogicMonitor Collector
HELPTELEPHONE=>1-888-41LOGIC (888-415-6442)
URLUPDATEINFO=>http://www.logicmonitor.com
INSTALLSTATE=>5
LANGUAGE=>1033
INSTALLSOURCE=>C:\Users\xxxx\AppData\Local\Temp\{3DBB1779-375F-4FE3-A29D-C935E9FDD561}\
HELPLINK=>http://www.logicmonitor.com
NAME=>LogicMonitor Collector
URLINFOABOUT=>http://www.logicmonitor.com
INSTALLDATE=>20140725
REGCOMPANY=>xxxx
VERSION=>1.10.3000
VENDOR=>LogicMonitor
WORDCOUNT=>0
ASSIGNMENTTYPE=>1
IDENTIFYINGNUMBER=>{B8BE4241-B235-4DA2-8642-CF9627F8303E}
CAPTION=>LogicMonitor Collector
PACKAGENAME=>LogicMonitor Collector.msi
INSTALLLOCATION=>C:\LogicMonitor\Agent\
TRANSFORMS=>
As Tom pointed out you need to add the hostname, but if you already doing this then the help page http://www.logicmonitor.com/support/monitoring/os-virtualization/troubleshooting-wmi/ has a section on repairing wmi counters.
"You may be experiencing unexplained errors such as "Empty result set", ox80041003, 0x80041017 from the collector debug, WBEMTEST utility, or your custom application."
There are steps to repair your counters in that help page, I have found this cures the empty results set problem in all cases I have seen.
Microsoft state that this may happen when "... certain extensible counters corrupt the registry, or if some Windows Management Instrumentation (WMI)-based programs modify the registry", but the exact nature of these issues is largely unknown and normally not worth troubleshooting extensively.
Hi Wael
Just wanted to add that win32_product should not be used for monitoring. Invoking this class will cause windows to do an integrity check on all installed MSI's, making it very slow (check the application log after you invoke this class to see). Also win32_product will only return applications installed using MSI.
Regards
