Symptoms: Sometimes, you get this error in SMS Provider log, in CM2012.
This is generally due to load on the server and WMI, during temporary processing of queries.
Resolution: This error can be fixed by increasing the quota values in __ProviderHostQuotaConfiguration WMI class.
Check out: http://blogs.technet.com/b/askperf/archive/2008/09/16/memory-and-handle-quotas-in-the-wmi-provider-service.aspx
Changing values of Memory perhost and Memory allhosts is enough.
Method is described here: http://babaus.azurewebsites.net/2015/08/14/wmi-fine-tuning-for-config-mgr/
Another way is to run this script:
This is generally due to load on the server and WMI, during temporary processing of queries.
Resolution: This error can be fixed by increasing the quota values in __ProviderHostQuotaConfiguration WMI class.
Check out: http://blogs.technet.com/b/askperf/archive/2008/09/16/memory-and-handle-quotas-in-the-wmi-provider-service.aspx
Changing values of Memory perhost and Memory allhosts is enough.
Method is described here: http://babaus.azurewebsites.net/2015/08/14/wmi-fine-tuning-for-config-mgr/
Another way is to run this script:
$WMIProviderConfig = Get-WmiObject @WMIHT $WMIProviderConfig.MemoryPerHost = 1024MB try { $WMIProviderConfig.Put() | Out-Null Write-Verbose -Message "Successfully changed the WMI provider settings" -Verbose } catch { Write-Warning "Failed to modify the WMI provider because $($_.Exception.Message)" }