Go to All Forums

WMI issues on Windows Servers

Other than my organization (we do have a Site24x7 team looking at the problem) is anyone else who's using Site24x7 to monitor their servers experiencing WMI issues on every server?  Not just physical servers, but VMs as well.  We do have HP servers in place and we're seeing errors such as: Windows Management Instrumentation has stopped WMIPRVSE.EXE because a quota reached a warning value. Quota: PrivatePageCount Value: 6275072 Maximum value: 0 WMIPRVSE PID: 10468 Providers hosted in this process: C:\Windows\SysWOW64\wbem\WmiPerfInst.dll.  We've increased the quota but it doesn't fix the issue.  This started happening as soon as it was installed.  The issues we are seeing due to this is that other applications using WMI is unable to pull data, uninstalling programs doesn't work until the Site24x7 agents are stopped.  We have disabled Windows event log and AppLogs but it doesn't fix the issue.  We also have changed the frequency of checks from 1 minute to 10 minutes, but the events continue to pop up.  The only fix is to stop the Site24x7 agent.  I'm wondering if anyone else has experienced the same and if you have, where you able to fix the issue and what steps did you take?  Also, this is happening on Windows 2012 R2, Windows 2016 and Windows 2019 servers.

Like (4) Reply
Replies (6)

Hello, on our side we had bad performance on all VM due to WMIPRVSE.EXE cpu usage. This has been corrected in the 19.7.5 version. Since then we don't have issues with wmi.

Like (0) Reply

Hi,

 
We are working on the WMI related warning events. We will post here in this thread once we get an update.
 
 
Regards,
Hisham
Like (0) Reply

Just an update on this.

First, the Site24x7 has went over and beyond on working with me in finding a fix for the issue.  They created multiple agents to try and improve the WMI calls and more.  Big kudos to the team.

With that being said, it's looking like the issue was with our WMI quota.  In the past it was configured with high values, specifically for this property: MemoryPerHost

We had it configured at 4GB.  Dropping it to 2GB (at first we dropped it to 512MB and it worked) fixed the issue.  Anything higher and the problem would immediately start happening again.   We are testing that out on multiple different servers during the next 1-2 weeks to make sure that's the fix, but so far, not ONE event has happened on any server after making that change.

Like (0) Reply

Hi,
Thanks for understanding and sharing your positive feedback. It really means a lot to us :)

Looking forward to your continued support and cooperation.

Regards,
Hisham

Like (0) Reply

I am on the 19.8.1 and we have still have performance issues due to WMI. I really don't think we should be changing our servers for the agent but did you manually change your servers or use a GPO/Script to update?

Like (0) Reply

Hey, that WMI issue was a pain, however, it is resolved for us.  It came down to 2 things actually:

 

1. The quota was wrong specifically for "MemoryPerHost".  It was off by 1 bit which resulted in problems.  Originally it was set to 4294967296, the 6 pushing it past its capacity.  We had to change it to: 4294967295

 

2. Since there were other tools that accessed the Windows Event logs within our infrastructure, we had to disable Windows Event log capturing on Site24x7.  I actually created a rule to automatically disable it and change monitoring polling to 5 minutes when new servers are added.  

With these two changes, our WMI issues went away.  

Like (0) Reply

Was this post helpful?