Quota violation error in Windows operating system queries (4307714)

The Monitored Host performance is low as the Agent queries WMI for metrics

The Agent logs shows
Quota violation [ SWbemServicesEx ] error: YYYY-MM-DD HH:MM:SS.SSS ECHO db_sql_server 5.5.2.2="" db_sql_server="" dbss-myinstance.mydomain.com="">ERROR [Agent DBSS-myinstance.mydomain.com OSDBMODEL thread-2]com.quest.qsi.dbwc.sqlserver.agent.submitters.InstanceParser
- An unexpected error occurred which may cause undesired behavior. You may want to contact Quest Software customer support if you see this error again: A critical error happened while executing a WMI query for collection SQL server host.
The reason for the error is : Error [-2,147,217,300] : Quota violation  [  SWbemServicesEx   ]
[Ljava.lang.StackTraceElement;@1a99ab1
java.lang.Exception: Stack Trace

Queries against the WMI are successful, by using WBEMTEST

Why is the Monitored Host performance is affected when the Agent queries the WMI?

The Agent queries the Monitored Host WMI for metrics. In some cases, performance will be affected as a result of this operation. The main focus on this behavior, is that this is Windows behavior, rather than the Agent behavior as the Agent uses WMI for queries only and doesn't perform any modification over WMI. In order to investigate why quering the WMI causes performance on the Monitored Host*, the WMI itself asd a component and a service should be checked. Other than this, the Agent queries can be ran against the WMI in order to show what query causes the perfomance issue, but again this is not certain as the WMI itself might be the obstacle here.

Windows Management Instrumentation Tester (WBEMTest) is used for WMI testings. WBEMTest.exe is included on every computer that has WMI installed.

What does the WMI Quota Violation mean?

RESOLUTION 1

Make sure that the recent Microsoft hot fix has been applied

Microsoft approved that this is a bug for Windows Server 2003: KB 828653

Restart the WMI service

Login to the Monitored Host, open start | run | services.msc and restart Windows Management Instrumentation service.
Check if the WMI queries are not affecting performance.

Enable the WMI log file

Login to the Monitored Instance and enable the WMI log. Analyzing the WMI log file can shed light on the query that causes the Quota violation error.

1. Highlight My Computer and then right click | Properties | Manage | Service and Applications | WMI Control.
2. Highlight WMI Control and Properties
3. Click the Logging tab
4. Check the Verbose (Includes extra information for Microsoft troubleshooting)Click OK
5. Restart WMI service and reproduce
6. Send to Support the WMI logs

Check the WMI cache temporary policy, by using Windows Management Instrumentation Tester (WBEMTEST)

• Run c:\Windows\System32\wbem\wbemtest.exe
• Connect to "root" instead of "root\default"
• Click on the Connect... button to acomplish this step
• Click Enum Instances and use ArbitratorConfiguration as the classname
• Click OK
• Double click the ArbitratorConfiguration
• Scroll down to PollingMemoryTotal property and highlight it
• Double Click the PollingMemoryTotal property
• The default value is 10000000 (0x989680)
• Modify the value to 20000000
• This will set the WMI temporary cache limit up to 20MB
• Click Save Property
• Click Save Object
• Reboot the machine

To raise the memory quota of WMI Provider service, perform the following steps:

• Open the Start menu and run wbemtest.exe.
• Click Connect.
• In the Namespace field, type root.
• Click Connect.
• Click Enum Instances.
• In the Class Info window, enter the following superclass name: __ProviderHostQuotaConfiguration. Click OK.  Note: the superclass name must start with a double underscore.
• In the Query Result window, double-click the __ProviderHostQuotaConfiguration=@ record.
• In the Object Editor window, double-click the MemoryPerHost parameter.
• In the Value field, type 1073741824 (1024 MB).
• Click Save Property.
• Click Save Object.
• Close Wbemtest.
• Restart the computer.