Not enough server storage

Tue, 2007-07-17 11:58 by admin · Forum/category:

Error messages:

  • Not enough server storage is available to process this command.
  • Not enough memory to complete transaction. Close some applications and retry.

These error messages on a computer, which we will call computer A, can indicate the IRPStackSize bug on the other machine, the server that has the share, which we will call computer B. Go to that other computer, B, open the event log, and check for event ID 2011. If this is present, it is a strong indication for this particular bug. The two computers again:

  1. The computer trying to access a share on the other computer over the network, displays the error message, "Not enough …". Let's call this one the client.
  2. The server where the share is, needs to have its IRPStackSize parameter increased. Let's call this one the server, even if it is just a desktop computer.

To repair it, you have to set or increase the IRPStackSize parameter in the registry on the server where the share is, i.e. on computer B.

There are many reports (below), indicating that a value of 15 is not enough, and only values in the range of 16 to 25 solved the problem.

The most successful values used to be 16 and 18, but recently we have more reports of 20 and more. If you want to solve the problem quickly, try 20.

It is not quite clear whether higher values incur any cost in terms of memory usage or performance, but it is conceivable that they don't. If so, then we probably should just set the value to its maximum of 50 and forget about it.

And don't forget to reboot after each change, because only that makes the new value effective. Thanks to everybody who tested and reported!

Please add a comment below to report which value you used to make it work. If you find the time to experiment, please report the lowest value that worked. Please try also to set it back to a lower value and recheck whether that indeed makes it fail. Reboot after each change.

Here is the offending registry value:

HKEY_LOCAL_MACHINE
 \SYSTEM
  \CurrentControlSet
   \Services
    \LanmanServer
     \Parameters
IRPStackSize DWORD 0x0000000f (15)

Check for the presence of the value named IRPStackSize. If it doesn't exist, create it as type DWORD and make sure you have the capitalization absolutely correct (5 upper case, 7 lower case characters), because the system strangely seems to depend on that. Make sure also that you haven't by mistake added a leading or trailing space as described in this comment below.

With base set to decimal, enter the value 16 or higher. 15 is the default, so entering 15 should have the same effect as removing that value altogether.

Reboot the computer (or restart the server service, as described in the comment below: Worked for me).

Certain software, when installed on the server, also causes this error. One frequent culprit is

  • Norton AntiVirus,

which tends to change the registry parameter. See also: How to remove Norton software. Other culprits seem to be

  • Acronis TrueImage, version 10 or 2009 or higher,
  • Seagate DiscWizard (a rebranded version of Acronis TrueImage),
  • IBM AntiVirus,
  • Microsoft's Bitdefender, and
  • Symantec EndPoint Protection (version 11+),
  • AVG 2011+.

Some reports state that only uninstalling solves the problem. If you have such a case, please report your findings here.

Check also this Microsoft Knowledge Base article. It does not mention Windows XP, but applies to XP as well.

Antivirus Software May Cause Event ID 2011 (Q177078)
http://support.microsoft.com/kb/177078/

Not enough server storage...

Mon, 2008-09-15 03:40 by peterbosman

Thanks for the effective advise. My problems, too, started after installing TrueImage.
Peter

Thanks!

Sun, 2008-09-07 00:10 by Victor

I could no longer get my Vista Machine to access the mapped drives (both internal and external) which are connected to my XP computer and got the error message about insufficient server storage.

I checked the registry of the XP machine and there was no IRPStackSize entry. 15 didn't work, but when I raised it to 18, all was back as it should be.

As I try and recreate what caused the problem to appear I think the trial version of TrueImage may be the culprit since that was recently installed and even when not actively running has some processes going in the background. Of course, that may not be the case, but I can't think of anything else that's been changed in the last day or so that might have caused it.

In any event, I'm sure grateful for the info that solved this.

Thanks.

Dick

Thanks for these reports

Sun, 2008-09-07 09:33 by admin

Thanks to everybody who reported the solution, particularly the values higher than 15 that were needed to solve the problem!

I just edited the main article above to reflect the fact that 15 is often not enough and that TrueImage appears to be implicated.

Thanks for a quick solution that works!

Wed, 2008-08-06 21:19 by felixs

Dell Dimension Optiplex and Lenovo X61s connected through LAN at work, both running WinXP Pro SP2. Dell has Sophos, Lenovo has Kaspersky antivirus. Both computers 'see' each other and I could access files on the Dell from the Lenovo but not vice versa. Neither computer had the IRPStackSize entry. I added the IRPStachSize with value 15 on the Lenovo and restarted services as indicated by a post below. Did not work. I increased value to 25, restarted services and BINGO! Now I can access files in both directions again (only Lenovo has IRPStackSize entry!).
Thanks for this quick and easy solution which I just rated a four star.

Works fine thanks

Mon, 2008-08-04 19:13 by Islandxpress

here my story:
Desktop Dell XPS, two Lenovo Thinkpads in a small WLan net. XP Prof SP3 on all.

The two laptops allow file transfer both ways between them.
The desktop can download files from the laptops, but none of the laptops can download files from the desktop.

Checked IRPStackSize parameter in desktops registry: Not included.

Repaired registry as suggested, set value to 15. Result: No good, no change.

Increased IRPStackSize to 25. Result: ok, file transfer from and to desktop is now possible. :)

Checked registry on both laptops, no IRPStackSize parameter???
Can't explain why it is necessary to have this entry on the desktop registry, but the laptops don't seem to need it.

Anyhow, most important - problem solved - thanks

Only on the server

Tue, 2008-08-05 05:48 by admin

The setting is only needed on the server, i.e. on the computer where the share or printer is. And I have not found out why some computers need a value higher than 15. If anybody knows, please chime in.

Worked for me

Sun, 2008-07-27 20:07 by etmed

Server was XP SP2 machine with Symantec AV 10.1.5.5000 and client also XP SP2. IRPStackSize was set to 15 and I was getting event 2011. Set IRPStackSize to 25 and, in lieu of rebooting, restarted the Server service (Start -> Run -> services.msc). Tried it again and voila, share access. Thanks!

Thanks for the good hint!

Sun, 2008-07-27 22:13 by admin

Good idea to restart the server service. I'll edit that into the main article.

This was the hint I was looking for!

Wed, 2008-07-09 09:55 by Carolin

I tried so hard to connect my laptop (Win 2K SP4) to my desktop pc (Win XP SP3) and always received the alert, that there was not enough server storage.

I also knew about the MS advice, but increasing the IRPStackSize value on my laptop didn`t change anything. Today I read your hint, increased the value on my desktop pc from 15 up to 18 and - voilá - I can finally access my desktop pc over the network!!!
Thank you so much!

Glad this helped

Wed, 2008-07-09 17:01 by admin

You're welcome! Good to hear that the article was helpful.

Saved me a huge headache...

Sat, 2008-05-17 03:34 by iantheevil

I just bought a 2TB external USB drive to use for storage for my company until we upgrade our systems. I had just installed it and started moving many of our (less used) shares to the new drive when I decided to test it out to make sure the oft-used shares would work properly. That's when I ran into the "Not enough server storage space available to process this command" error. I'm am so glad the first thing I did was to do a search on the error and that I ended up at this site! I am using Symantec Anti-Virus Corporate Edition and I ended up using 25 instead of 15 to get it to work. Your article saved me so much time I can't thank you enough.

Interesting

Sat, 2008-05-17 21:20 by admin

Thanks! Interesting that you confirm that you also needed 25 instead of the default 15. I wonder where that comes from.

But we do not need to know. We only need to know how to fix the nasty thing.

Thank you!

Sun, 2008-05-11 17:07 by Bocaboy

I was having trouble connecting to a shared Western Digital USB drive connected to an XP desktop. I couldn't do it from my Mac or another PC, but it wasn't until I tried from another PC that I was able to track down the error message and solve it.

As a note, I had to increase the value to 25 to make it work. You might consider adding that footnote to your excellent solution.

Also, if you're adding this DWORD value to the registry, it is case sensitive and must be enter exactly as it is shown in the post (IRPStackSize)

Thank you too

Mon, 2008-05-12 10:35 by admin

I just added your information to the main article at the top. This is very helpful.

Fantastic - no more hair pulling!!!

Sat, 2008-05-10 01:51 by mefrunter

like another user signed up just to say thank you and vote it four stars.I can stop the pulling of - the very little I have left - hair .
Appreciate it - keep up the good work.
Cheers
mefrunter

Good to hear

Sat, 2008-05-10 08:05 by admin

Thanks! The problem is still widespread, probably due to poorly (or arrogantly) programmed third-party software.

PragueBob's picture

Fantastic advice! Perfect!

Fri, 2008-01-25 19:10 by PragueBob

This was such good and helpful advice that I signed up just to give it as many stars as possible and make this comment. Thanks so much to whoever posted this.

Hans's picture

Glad it helped

Fri, 2008-01-25 19:26 by Hans

Thanks for the thanks!

The articles labelled admin are from me, I can proudly state. smile

I need two accounts around here. I know, admin sounds a bit impersonal, but I have to separate the "official" from the "personal" articles.

Not enough storage is available to process this command

Thu, 2008-11-13 08:29 by patneys

I too am getting this error "Not enough storage is available to process this command" if I try to access a shared folder/drive which is on my external disks through network.
My shares on internal disks can be accessed.
I tried increasing the IRPStackSize to various decimal values viz 15, 18, 20, 21, 25, 30, 49, 50, 100. Did restart the svr service after modifying these values but to no avail.

On attemped access to shared folders, the event viewer throws up the error: The server's configuration parameter "irpstacksize" is too small for the server to use a local device. Please increase the value of this parameter. (Event id: 2011)

OS: Windows XP SP3
------------------------
Problem Solved!!! Damn, I had pasted a 'space' at the end of the word "IRPStackSize ". solved by deleting that.

No event 2011!

Mon, 2011-11-21 10:33 by oldabelincoln

I had the same problem on XP Pro SP3 (both systems), but without event 2011 on either system.

I thought that I had inserted the registtry change, without effect, on the server (machine B) so I uninstalled Acronis Disk Director to see what would happen. I had noticed an Acronis entry in user types, so when I read of Acronis issues with True Image, I became suspicious, as Disk Director includes similar functionality.

I had to wait for a TV recording to finish before rebooting, and I decided to check the registy. The entry was gone. Acronis? Me? I don't know.

Made the entry again (25 decimal), restarted the server service, no reboot. All was well.

Sorry to be so ambiguous. I don't know if others have also not had an event 2011 entry, but I definitely did not have one.

Abe

Thanks for reporting back!

Thu, 2008-11-13 11:54 by admin

It's always good to know what worked! I'll mention this trap in the main article as well.

17 and 18 worked on two separate computers

Sat, 2009-03-14 20:52 by pyrex

There was an Asus Eee PC that got an IRPStackSize of 17 and a Desktop that got 18. Both computers function well together in the network of many.

Most frequently mentioned

Sat, 2009-03-14 22:22 by admin

I think 17 and 18 are the most frequently mentioned success numbers. Thanks for reporting back!

IRPStackSize

Mon, 2009-05-25 07:51 by admea

I did as MS suggest and increased the IRPStackSize by 3 to 18 and it worked like a charm. :)

Thx for the tip!

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.