This problem is killing me: Not enough server storage is available to process...etc

[sram]

We have this ~15 computers workgroup network and everything was okay until one day we started seeing this problem. When the shared drive letter is clicked, we get this message:

Not enough server storage is available to process this command

After some googling, I found that a value needs to be increased in the Registry. It was addressed in one of M$ articles. I followed it exactly, and things are fine for some days and then it is back.

This is the article:

http://support.microsoft.com/kb/106167

I set it to the maximum value already the first time so there is no higher value I can set this stack size to.

Could this be an infection? Virus or malware? could it be a hardware problem?

What do you think?

 

[JBark]

AV software will do this, I know a few older versions caused this problem. Also, that max value of 12 isn't true, the real max is 50. I've gotten bit by that before. 12 was the max with NT.

Also, take a look at this article, it can cause the same sorts of error messages:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;304101

The PagedPoolSize key is the important one.

 

[nessus]

You reallyneed to find whatever driver or process is misbehaving. If increasing the allocation only got you a few extra days, something is leaking.

I'd take "poolmon -b " captures right after startup, and then every couple of days. Look for things making new allocations, but not releasing.

 

[sram]

AV software will do this, I know a few older versions caused this problem. Also, that max value of 12 isn't true, the real max is 50. I've gotten bit by that before. 12 was the max with NT.

Also, take a look at this article, it can cause the same sorts of error messages:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;304101

The PagedPoolSize key is the important one.

I found out about 50 being the true maximum minutes before reading your post. I set it to 50 and everything is well now. Hopefully it won't happen again.

Thanks.

 

[sram]

You reallyneed to find whatever driver or process is misbehaving. If increasing the allocation only got you a few extra days, something is leaking.

I'd take "poolmon -b " captures right after startup, and then every couple of days. Look for things making new allocations, but not releasing.

I'll be grateful if you can elaborate. I don't want this to happen again.

Thanks.