Quota violation in wmi

Question

0.00/5 (No votes)

See more:

I have a wmi query to monitor file system changes.

Select * from __InstanceOperationEvent within 5 where TargetInstance isa 'CIM_LogicalFile'

It shows an error when run in wbemtest call quota violation.

Can any one help me with how to remove the quota violation error.

What I have tried:

I searched in Microsoft website about the error it showed me some steps to remove the error but i didn't work
Even after also it displayed quota violation

Posted 21-Jul-18 2:51am

Member 13906075

Updated 21-Jul-18 5:13am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Accepted Answer · 2018-07-21T05:14:00

Solution 1

Memory and Handle Quotas in the WMI Provider Service | Ask the Performance Team Blog[^]

Posted 21-Jul-18 5:14am

Dave Kreskowiak

Comments

Member 13906075 21-Jul-18 12:15pm

I have tried it even though it displays invalid parameter when trying to save the object

Dave Kreskowiak 21-Jul-18 14:06pm

Well, it was something to try. This is something you're going to have to research. There probably isn't going to be someone who just walks up and goes "oh yeah, just do this and you're good".

Also, monitoring an entire drive for all file changes will quickly overwhelm whatever code you write because there is so much going on.