What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

OS version could not be determined

Votes:

0

Your Vote:

Up

Down

We have some sensors (Disk Free, pagefile usage, memory, and CPU Load) that are giving the following in PRTG:

- Note: the OS version of the device could not be determined, WMI might not work reliably.

The target server is Windows Server 2008 Standard w/ SP2 32-bit.

PRTG Server is version : PRTG Network Monitor 8.4.1.2283 Operating System: Windows 7/2008 R2 (6.1.1 Build 7601 Service Pack 1), 8 CPUs

Interestingly enough, when looking at Control Panel -> System Properties on the target server, both Processor and Memory say "Not Available"

WMI was already restarted as well as the box itself - issue persists.

2008 os-version prtg server standard windows wmi

Created on Aug 25, 2011 8:17:36 PM by  dsanpedro (50) 1 1



Best Answer

Accepted Answer

Votes:

0

Your Vote:

Up

Down

Following the WMI Repair List resolved my issue. I had to:

1) Reset WMI

winmgmt /resetrepository
winmgmt /resyncperf

2) Rebuild WMI by running the below code (.bat file) as admin"

net stop winmgmt
c:
cd %systemroot%\system32\wbem
rd /S /Q repository

regsvr32 /s %systemroot%\system32\scecli.dll
regsvr32 /s %systemroot%\system32\userenv.dll

mofcomp cimwin32.mof
mofcomp cimwin32.mfl
mofcomp rsop.mof
mofcomp rsop.mfl
for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
for /f %%s in ('dir /b *.mof') do mofcomp %%s
for /f %%s in ('dir /b *.mfl') do mofcomp %%s

3) Run lodctr /r to fix the remaining monitors in error

I conclude that WMI on the target host was completely corrupt. Thanks for the assistance!

Created on Aug 29, 2011 7:56:33 PM by  dsanpedro (50) 1 1

Last change on Aug 30, 2011 2:19:30 PM by  Torsten Lindner [Paessler Support]



2 Replies

Votes:

0

Your Vote:

Up

Down

Hello,

this seems to be a major issue with the WMI on this particular target host. Please try if anything from our "WMI Repair List" does help.

best regards.

Created on Aug 29, 2011 11:02:51 AM by  Torsten Lindner [Paessler Support]



Accepted Answer

Votes:

0

Your Vote:

Up

Down

Following the WMI Repair List resolved my issue. I had to:

1) Reset WMI

winmgmt /resetrepository
winmgmt /resyncperf

2) Rebuild WMI by running the below code (.bat file) as admin"

net stop winmgmt
c:
cd %systemroot%\system32\wbem
rd /S /Q repository

regsvr32 /s %systemroot%\system32\scecli.dll
regsvr32 /s %systemroot%\system32\userenv.dll

mofcomp cimwin32.mof
mofcomp cimwin32.mfl
mofcomp rsop.mof
mofcomp rsop.mfl
for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
for /f %%s in ('dir /b *.mof') do mofcomp %%s
for /f %%s in ('dir /b *.mfl') do mofcomp %%s

3) Run lodctr /r to fix the remaining monitors in error

I conclude that WMI on the target host was completely corrupt. Thanks for the assistance!

Created on Aug 29, 2011 7:56:33 PM by  dsanpedro (50) 1 1

Last change on Aug 30, 2011 2:19:30 PM by  Torsten Lindner [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.