Quota violation while running WMI queries

KB ID:
1657
Product:
Veeam Management Pack for Microsoft System Center
Version:
5.7
Published:
Last Modified:
2013-04-23

Challenge

In the nworks Web UI, some monitored objects are grey or missing at all.  The Collector is installed on Windows 2003 Server.

Standard troubleshooting steps do not help, the SCOM agent log on the Collector server contains the following error: 

WMI Error: 0x8004106C

When you try to use the WBEMTEST utility you get the same WMI error, you get the following message:

WMI: Quota violation

User-added image

Cause

The problem can occur if WMI Provider service has reached its quota limit. It was found out that only Microsoft Windows Server 2003 machines are affected.

  • Microsoft Windows Server 2003 has the memory quota of 128 MB per host.

  • Microsoft Windows Server 2008 has the memory quota of 512 MB per host.

Solution

To raise the memory quota of WMI Provider service, perform the following steps:
  1. Open the Start menu and run wbemtest.exe.

  2. Click Connect

  3. In the Namespace field, type root.

  4. Click Connect.

  5. Click Enum Instances.

  6. In the Class Info window, enter the following superclass name: __ProviderHostQuotaConfiguration. Click OK

    Note: the superclass name must start with a double underscore.

  7. In the Query Result window, double-click the __ProviderHostQuotaConfiguration=@ record.

  8. In the Object Editor window, double-click the MemoryPerHost parameter.

  9. In the Value field, type 536870912 (512 MB).

  10. Click Save Property.

  11. Click Save Object.

  12. Close Wbemtest.

  13. Restart the computer.

More Information

If you have any questions or problems, please contact Veeam Support at http://www.veeam.com/support.

Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.

OK

Rate the quality of this KB article: 
4.5 out of 5 based on 2 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text:

Submit