Have a longstanding home network with various laptops for family members and never a problem running network wizard, enabling sharing, saying WORKGROUP, sharing a folder, and so on. After a new hard drive on our T61, and reinstalling XP from the IBM disks, coldn't connect due to the error ""not enough server storage is available to process this command". XP3 on all machines. There may have been Norton software and I would have uninstalled it as I use ESET Nod32 with no problem. Ran the Norton uninstall program anyway but that didn't fix it. Edited the registry to a value of 21, but it then says 33. It should say IRPStackSize Reg_DWORD 0x00000015 (21) or should it be 21 (33)?

Also, my the T61 has a DWORD value for "size" but none for IRPStackSize, whereas my new T400 has IRPStacksize but no Size. Any idea of the distinction?

I rebooted both computers and this doesn't fix the problem with it saying 21 (33) and 15(21) and neither works. Oh, ok, I see, it should have a DECIMAL value of 21. You have to click decimal rather than hexidedimal when editing with regedit. Still, that didn't work.

However, FROM that computer the T61, i can reach the other computer, so not to worry.

Mike - informed user is all

Hi, this has not worked for me. First of all I have 64bit vista and not 32bit vista. When I go to the dword next to it It says that dword is for 32bit vista. Then under that it has a qword which says for 64bit vista. So I choose the qword instead of the dword but not only am I not able to type in IRPStackSize but I'm not able to do it under qword either. Now admin when you made this topic, it was 2007, which I'm sure 64bit vista was not out by then. But what advice do you give for 64bit users who is unable to download the windows installer because of low storage. What's the advice for 64bit users to get us out of this mess? Please help me admin I really need to download this windows installer 3.1. Thanks

Hamachi file sharing, free version never did work for me until I created that registry key and set it to 17.
Now it does work.

Just a note:

I added an RPStackSize of 25 to A WinXP Sp2 x64 system and it worked.

Thank you.

My laptop can now finally see my desktop files after probably more than one year of this particular problem! (My testing is somewhat ongoing, and I have not yet checked the other computers in my home network.)

My desktop system has the SP2 XP Pro OS. Partitions "C" and "D" are on the boot HD whereas partition E is on a second HD.

A value of "16" (on the desktop system) for IRPStackSize was not effective. A value of "18" had the strange effect of making the sharing possible on the "E" partition, but not on the "C" or "D" partitions! A value of "21" succeeded in making all three partitions visible. The items that are peculiar to "E" is its location on a separate hard drive (on a separate HD controller) and the fact that its drive letter was re-assigned to "E" to work into my partitioning scheme.

Thank you for this solution! I wish that I had found it a year earlier.

PS: I have had several versions of Norton AV on this system and currently have Norton AV installed. I am in the process of migrating away from this program.

Having wrestled with this problem for years and given up, I encountered it again recently whilst installing a new PC and laptop, which I need to sync with each other, so I had to try again.

Changing the IRPStackSize to 16 did the trick, and I changed it back to 15 just to check. Sure enough it didn't work.

Thanks for providing the solution to this very irritating problem. Could someone tell Microsoft?

Thanks! The registry tweak works well.

I have a home fileserver with a lot of internal drives and partitions as well as an external hard drive enclosure connected to the server via USB and a USB printer. Other computers could see the description and drive letter for the external USB drive, but got the "Not enough server storage..." error message when trying to access any of the files stored on it.

I checked the registry and the key wasn't there. So I entered it and set a decimal value of (16). I separately tried restarting the Server service, logging out of and back into windows, and rebooting, all to no avail.

I cruised the nearby keys and noticed that there were 16 shares listed. Not sure that it matters, but it made me think that a higher number would be better for the stack size.

So I tried the suggested value of decimal (25). After I made the change, all it took to get everything working again was a restart of the Server service via Administrative Tools.

Thanks again!

hi,

I finally got it fixed for my external usb drive, after seeing it for a few (2-3 days, but never before that) but it could have been resolved by either of two things

- i played around with the different values for the stacksize, but nothing helped, but i didn't reboot each time, but restarted the services, only the last time (see below) i rebooted, so it could be that a reboot was necessary and the value 25 helped.

- i completely forgot it, but a spontaneous occurring vprorecovery.ini on the external drive after a convert/format to ntfs (from fat32, even tried that) helped me to remember that i had a trial version of norton (yes norton again!) ghost which accidentally expired a few days ago. Removing and rebooting resolved it.

... but I can't be sure what did the trick, but the expiring norton around the time that the issue started is too much of a coincidence in my humble opinion.

regards,

Peter

Thanks for providing this solution . I had this when trying to map a drive on my XP Pro desktop from my Vista Notebook . In my case i could map any share on the XP box ( 10 drives up to 400G in size) except one which gave me this error . This drive was a USB ext 750G HDD . Applying the registry change with a value of 16 and restarting the server service fixed the problem .

XP box has Norton 360 and trial of Acronis True Image Home 2009 but i can't say that either "broke" the sharing as I hadn't mapped this USB drive before they were installed . I had mapped other drives before and they were all unaffected .

I thought this might be significant but I don't know how .

Thanks guys for all your helpful post. But how do I resolve this error in the event that I cannot even logon to the server. I am completely shut out of the server.

On system logon to Window Server 2003. I get this error.
System cannot log you on due to the following error Not enough storage is available to process this command.

I had a call from a user today having this exact issue. I noticed the entry was not in the registry and I thought I was in for a quick fix once I read the solution. I added the registry entry and experimented with different values and still nothing. After banging my head on the desk for about 15 mins. I figured if all else fails blame Norton. I did an uninstall of Norton Anti-Virus 2009 with the Norton Product Removal Tool.... and like magic, all of the mappings were working again with no issue.

I recommend for those who aren’t having success with the registry fix alone to try to uninstall the protection software as a troubleshooting step... worked for me. The user is now happy with AVG and everything is working as intended!

The IRPStackSize entry was completely missing. I added it with a value of 16 and restarted the Server service. BTW I also had to restart the Computer Browser service as this is stopped when the Server service is stopped. Whoppee works a treat.

I am running Acronis TrueImage V10 and have been for over a year. Dunno why this should suddenly happen now. My last install was Ad-AwareAE free.May this could be added to the culprit list.

Anyway great tip, helped me no end, thanks very much.

I'm another very happy reader of this item. I am setting up a new PC and had the network drive access problem. I have both Norton IS and Acronis TrueImage on the system, so I don't know which one is the likely culprit.

On my system (XP, SP3) setting IRPStackSize (which I had to add) to 15 didn't work, but 16 did.

Many thanks for the great tip.

I've been farting around trying to fix this problem for months. I stumbled upon your website and like others, I had already tried the setting of 15, based on something I read months ago, to no avail. I wasn't expecting much but I read through all the posts and found that 18 appears to be the minimum number that worked for everyone, so I went straight to 18 and Voila, it worked! I couldn't believe it. Thank you very much.

But my question is, why are we supposed to sneak up on the lowest number that works? Why not set it to 20 or 25 or higher, right to begin with?

btw, I don't have Norton (hate it) but I do have Acronis True Image 11 Home (love it!). I don't know if when I upgraded to version 11 (from version 9) is when my problem began, but I know for sure it was still working when I had version 9.

Thanks again!

thanks for the fix, I too had just installed that TrueImage piece of crap, and had no idea my problem was related. Gotta love google and winhlp.com

I tried 15 and 16 and nothing, so I jumped to 18 and everything's cool.

16 worked, so I didn't try any other values.

Sharing used to work on my machine, but seemed to stop after I installed Norton Internet Security 2007. Maybe some connection, maybe not. May try some experimenting on my other machines to see if installing NIS2007 changes the registry key.

Thanks a lot for posting this fix!!! Very much appreciated.

"Information is best when shared!"

I also have TrueImage home installed, and I never would have guessed that it was the cause of my network problem.

I had no IRPStackSize entry at all, adding it with a value of 16 and restarting the Server service fixed it right up.

Thanks!

Stacksize had to be increased to 18 here.
I too have trueimage.

I have 3 machines ... after increasing the stack size to 18 at first only the vista machine would talk to the XP desktop that is the troublemaker.
The laptop (also XP) would not talk to the trouble machine at first .. but I went to the toilet and when I came back I tried again and it worked that time without me doing anything.
Weird ... eh ?

I notice with lan stuff you have to do a lot of rebooting and a lot of waiting ... if at first it does not work ...just wait a few mins ....

Note to self: IRPStackSize must be a DWORD, not a STRING.....

Aaaaarrrrrrgggghhhhh

This solved my problem first time... thanks

WIN XP home, vanilla, value of 16 worked for me! THANK YOU!

suddenly started getting the "Not enough server storage" error when attempting to access shares on a WinXP box from a Vista box

for me it all went horribly wrong when windows update installed .NET 2.0 framework SP1

added the IRPStackSize with value 16, rebooted, no luck
changed value to 18, rebooted, works a charm!

thank you! thank you! i can access my 2TB share again

props to admin

After installing Acronis TrueImage home 2009 (which I like), I was not able to access my computer. I only realized this fact after reading your post. By first looking at Microsoft, they suggested to put the key larger than 4. Well this is far from enough. It used your recommended 15 and all is fine for me. Now I have to go back at Norton Internet Security and undo settings that I thought were wrong. Well!

Merci.

Signed up to cast vote and "Thank you so much for this post!!" I still need a little help though. After changing parameters I can now access all of my network files(yeah, been working 3 days on it) However, video now takes an unusually long time to load, and stutters while its playing. I have tried lots of settings (in increments of 3 up to 50) and even increased local cache to accommodate...to no avail.
My network WAS running fine w/o the irpstack mod before...and no wait when executing video etc..then a few days ago I could see the network, including folders but could not access files..until this change. I feel like I am very close, but I am at a loss right now. ANY help would be hugely appreciated. I would be more than happy to provide any additional info, if needed. Thanking you in advance,
Erich