Not enough server storage is available to process this command?

[googlemad]

I have my little Windows 2003 R2 SP2 x32 file server here at home which has been running like a dream for the past 2 years.

 

Last night I tried accessing the several shares I've got and am getting the message 'Not enough server storage is available to process this command'

 

I followed the instructions at:

Err Msg: Not Enough Server Storage Is Available to Process This Command with no joy (Although, they apply to NT 4)

 

Any ideas? The only change I can think to the server configuration recently is I installed some Acronis backup software to trial out.

 

P.S. I have stacks of disk space and memory free

[FN-GM]

Have you tried a reboot?

[googlemad]

Yep, then I uninstalled the Acronis software and all is fine!

 

Grr

[Michael]

You don't have Quotas enabled do you?

[leco]

Yep, then I uninstalled the Acronis software and all is fine!

 

Grr

 

Was Acronis trying to "do something" for which it didn't have permission perhaps? Interesting though about Acronis as I am researching some of their software at the moment. Which one were you trialing, please?

[Alp1]

Was it the local install or the agent install? I am using the True Image product, and so far so good. Does it only do this on that server, and have you tried on another server? Best bet for testing purposes would be to setup a virtual server for the purposes of testing.

[mrtechsystems]

Sounds like to me that the partition for recovery manager what set a little to high lol

[Alp1]

Try the following:

 

1. Start Regedit or Regedt32

2. Locate and then click the following registry subkey: HKLM|SYSTEM|CurrentControlSet|Services|LanmanServer|Parameters

3. Click Edit, point to New, and then select DWORD Value.

4. Type IRPStackSize and press ENTER. Note: IRPStackSize is case sensitive

5. Click Edit, and then Modify

6. *Set the Value Data to 15 then click OK.

 

Note: The default value of the IRPStackSize parameter is 15. The range is from 11 (0xb hexadecimal) through 50 (0x32 hexadecimal).

If the problem persists after you complete this procedure, increase the value of IRPStackSize even more.

7. Quit Regedit or Regedt32 and then restart the server.