Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

WMI not sending error when property is missing

I needed to create my own drive monitor APM (in order to encorporate TSM backup volumes in my calculations).

All is working fine except for Win 2000. The issue is the WMI property Win32_PerfFormattedData_PerfDisk_LogicalDisk does not exist on many (about 100) of them. My script traps for an error but no error is reported and the durn thing reports a size zero.

I log onto the server... see that Win32_Perf* does not exist in WMI. I would expect the query to return some non-zero Err.Number.

Anyone run into this? Here is a code snippet...

On Error Resume Next

'Get amount free megabytes from volume
strQuery = "SELECT * FROM Win32_PerfFormattedData_PerfDisk_LogicalDisk WHERE Name LIKE '" & strVolume & ":%'"
Set colItems = objWMIService.ExecQuery(strQuery,,48)
CALL ErrorCheck(Err.Number, strQuery)

if( IsNull(colItems) ) then
Err.Number = 99
CALL ErrorCheck(Err.Number, strQuery)
End If

For Each objItem in colItems
intFreeMb = objItem.FreeMegabytes
Next

Find more posts tagged with

Accepted answers

RogerWong

Hi, butler.

As you've discovered, Windows 2000 does not have formatted data classes (perfformatted...)

In a nutshell, to get disk statistics off W2K you must query for the raw data, and then apply some special Microsoft formula to convert the raw data into bytes free.

We've covered this before on thwack. Let me search for the example script and post a link.

Here you go. You should be able to modify the arithmetic in this script to get the disk space statistics you need:

This script queries the remote computer for the raw percent free WMI counter for the C: instance and then performs the necessary arithmetic to give us the % of used disk space.

Notes:

1. This script requires the following script arguments

Script Arguments: ${IP} ${USER} ${PASSWORD}

2. This script cannot monitor the status of the Orion NPM server itself, because it *only* makes remote WMI calls. You have to use the other script for that.

strComputer = wscript.arguments(0)
strUser = wscript.arguments(1)
strPassword = wscript.arguments(2)

Set objSWbemLocator = CreateObject("WbemScripting.SWbemLocator")
Set objWMIService = objSWbemLocator.ConnectServer (strComputer, "root\cimv2", strUser, strPassword)

Set colDisks = objWMIService.ExecQuery _
    ("Select * from Win32_PerfRawData_PerfDisk_LogicalDisk Where Name = 'C:'")

For Each objDisk in colDisks
    intBaseValue = objDisk.PercentFreeSpace_Base
    dblActualUsedSpace = 100 - ((100 * objDisk.PercentFreeSpace) / intBaseValue)
    WScript.Echo "Statistic:" & Int(dblActualUsedSpace)
Next

Roger

All comments

RogerWong

Hi, butler.

As you've discovered, Windows 2000 does not have formatted data classes (perfformatted...)

In a nutshell, to get disk statistics off W2K you must query for the raw data, and then apply some special Microsoft formula to convert the raw data into bytes free.

We've covered this before on thwack. Let me search for the example script and post a link.

Here you go. You should be able to modify the arithmetic in this script to get the disk space statistics you need:

This script queries the remote computer for the raw percent free WMI counter for the C: instance and then performs the necessary arithmetic to give us the % of used disk space.

Notes:

1. This script requires the following script arguments

Script Arguments: ${IP} ${USER} ${PASSWORD}

2. This script cannot monitor the status of the Orion NPM server itself, because it *only* makes remote WMI calls. You have to use the other script for that.

Roger

RogerWong

Here's the microsoft article that put me on the right track when I was wondering the same thing you were. More Windows 2000 WMI counter example scripts are in here.

http://msdn.microsoft.com/en-us/library/ms974615.aspx

gbutler

Thanks Roger... I'll give it a try.

gbutler

that was a good explanation. And I think its going to work.

My testing is showing that my failures are now due to the "logicalDisk" class not availabe... turns out Win2000 by default turns them off. This sure does give me a little flavor of what you guys must deal with in development. Yuck.

What is a bit frustrating is I was trapping the return value from all my WMI executions... I made the assumption that at minimum if the class did not exist it would report a "not found" or something. I guess a lesson learned about making assumptions... . ;-(.

thanks again.

Glenn.