none
WMI Counters are decreasing! RRS feed

  • Question

  • We have found a problem with some WMI raw performance data counters on Windows server 2016 build 14393 and Windows 2003 SP2. We found that some counters decrement  or Timestamp_Sys100NS not change with previous collectionso each recollection has a lower value that the previous value instead of getting bigger so this renders the calculations done after the recollection useless. For example, this happens in Win32_PerfRawData_PerfOS_Processor with the counter PercentProcessorTime, if we use WBemTest to get the values, we see that any new value of the counter is lower than the previous one, so when we try to get a formatted percentage based on the counter values we end getting an invalid negative percentage of processor time.

        Other counters affected are in Win32_PerfRawData_PerfDisk_PhysicalDisk:

        - PercentDiskTime
        - PercentDiskReadTime
        - PercentDiskWriteTime
        - AvgDiskQueueLength
        - AvgDiskReadQueueLength
        - AvgDiskWriteQueueLength

    Best regards,

    andy


    Friday, October 11, 2019 4:27 AM

All replies

  • HI
    Thank you for discovering this issue .
    1 how can I reproduce this issue on a clean install w2016 vm ?
    2 is this issue is Unique problem only happen in your environment ?

    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, October 11, 2019 9:04 AM
  • I can't reproduce this issue in my environment but several of our customers have sent us the same issue. They are using our application which collects cpu utilization by WMI class Win32_PerfRawData_PerfOS_Processor.
    Friday, October 11, 2019 9:33 AM
  • HI
    3 when the customer first find this issue ?
    4 did the problem happen after your customer install windows update patch?
    $QFE = Get-hotfix -computername $server | select-object -property Description,HotFixID,InstalledBy,InstalledOn | out-file c:\windows\temp\$server.txt
    change$server to the hostname
    5 if we run below command on problematical server ,will there be error information on problematial w2016 ?
    winmgmt.exe /verifyrepository
    Please check the symptom in a clean boot (refer to windows 10 steps) environment if it is possible. 
    when the server in clean boot mode,can you use wbemtest to query
    Win32_PerfRawData_PerfOS_Processor and get the correct count ?
    7 when the problematical server in a clean boot ,if you only run your application ,will it receive a correct count?
    clean boot steps
    https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows


    8 for other problem ,we can refer below document first.
    Troubleshooting WMI and WMI Counter Repair
    https://www.logicmonitor.com/support/monitoring/os-virtualization/troubleshooting-wmi/

    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, October 15, 2019 7:22 AM
  • HI
    Is there any progress on your question?

    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Sunday, October 20, 2019 10:12 PM
  • HI
    Is there anything to help you?

    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, October 25, 2019 2:49 PM