WmiPrvSE memory leak. The computer 'localhost' failed to perform the requested operation because it is out of memory or disk space


The computer 'localhost' failed to perform the requested operation because it is out of memory or disk space.

I got these error.
The disk had 75 % free space.
So, the memory is the problem
I killed the WmiPrvSE. The processes had 700.000k.
After, I killed it, everything goes well and the processe started again with 6.000k.
The hyper-v manager started to work without problem.

You can solve the problem restarting the server of course. But the server was in a enviroment production.



Anonymous said...

qnez f ) bz 94

Anonymous said...

My friend and I were recently talking about how technology has become so integrated in our day to day lives. Reading this post makes me think back to that discussion we had, and just how inseparable from electronics we have all become.

I don't mean this in a bad way, of course! Societal concerns aside... I just hope that as memory becomes less expensive, the possibility of downloading our brains onto a digital medium becomes a true reality. It's a fantasy that I dream about all the time.

(Posted on Nintendo DS running [url=http://www.leetboss.com/video-games/r4i-r4-sdhc-nintendo-ds]R4i SDHC[/url] DS SurfV3)

Anonymous said...

What's Happening i'm new to this, I stumbled upon this I have found It absolutely useful and it has aided me out loads.
I am hoping to give a contribution & help different users like its aided me.
Good job.

My webpage :: free music downloads

Anonymous said...

Way cool! Some extremely valid points! I appreciate you penning this article and also the rest of the website is also very good.

Here is my web blog: diets that work

Anonymous said...

Pretty element of content. I just stumbled upon your site and in
accession capital to claim that I acquire in fact loved account your weblog
posts. Any way I'll be subscribing to your feeds or even I achievement you access constantly fast.

Feel free to visit my blog post - bok of ra - -

Anonymous said...

Took a long time to find this article but it was well worth it. Resolved the issue on my 2008r2 painlessly.

Thank you