I recently had to upgrade storage in my always on machine. I moved some files onto the bigger drive and shared out the folders. The drives are mirrored and hold my photos and my wife’s graduate homework, etc. For a while they worked fine, after a while though, I couldn’t access the shares over my network and received the following error: “Not enough server storage is available to process this command.”
A quick search, with multiple results led me to an article such as found here. I thought I remembered reading in one of the search results that in some instances could be a result of drive size. A lot more also reference Norton, which I haven’t used since the late 90s.
Either way, the quick fix, was to do the registry edit, restart the machine, and all was well.
- Click Start, click Run, type “regedit”, and then click OK.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters - Click Edit, point to New, and then click DWORD Value.
- Type “IRPStackSize”, and then press ENTER to name the value.
Note Type IRPStackSize exactly as it is displayed. This is case sensitive.
- Click Edit, and then click Modify.
- In the Data Value box, type 30 or any value max of 50, and then click OK.
- Restart the machine
This does not work unless you do a regedit after every reboot. And I changed from Symantec to AVG and am still getting the error. There must be something else involved.
Randy,
Check to make sure you don’t have something running to protect your registry… I have only had to make this edit once, and I run McAfee and SpyBot 24/7 on my machines.
Good luck!
Your fix did not work.
Sorry Bob, anyone else out there have a solution? I know this worked on my machine, but I’ve only done it on one machine, so to call it a 100% working fix is obviously incorrect.
My original post also talks about Norton being an issue… It was long enough ago I don’t remember what they said. Any chance that’s what is interfering?
This fixed worked for my Windows 2003 Standard Server. I did not have to restart afterwords though. I just restarted the Server service.
Thanks!!
Yeah, this should work as long as you have nothing preventing or un-doing changes made to your registry. Examples of those could be anti-virus or spam/ad-ware programs. Or if you have any particular security software running.
Nice fix Mike!
Pingback: Brickblog » Surprising Search Results for Brickblog
Hello,
I just wanted to let you know that this worked like a champ! I was trying to connect to an XP x64 SP2 box and this little registry trick worked. Just add the value, restart the Server Service (on the machine you are trying to connect to) and viola!
Take Care>>>Dustin
I was having this problem with my PC also. I could access the files in my laptop from my desktop, but not from my laptop to my desktop PC. I was able to ping OK, just couldn’t access my files. Tried this and it worked.
As always, when changing your registry, back it up, and MAKE SURE YOU TYPED EVERY LETTER CORRECTLY. This includes caps and lower case. BE CAREFUL when editing the registry.
Changes took without problems.
This fix works in conjunction with comment #7. After restarting the Server service, I tried accessing my shared external drive on my desktop from my laptop and it came right up! You guys are geniuses! Many, many thanks!
This worked for me, but I did it on both the computer I was trying to connect from and to. I think this only needs to be done on the computer you are trying to connect to…
I failed. I can enter the entry in the regsitry but Something erased the data value after I entered it.
Any idea?
I connected a western digital 500 gig drive on one computer of my home network and try to access it from another computer on the network.
What is the proper value of the DWORD stack that I must enter in the registry. The suggested value of 50 fails.
What is the relation between the capacity of the drive andthe registry value.
The trick was to set the registry of both machines to 50 decimal. Thanks for bringing my attention to a solution.
Thanks, Worked fine for me. Only set on the server side. I’m wondering if some people may be trying to enter 50 in HEX instead of DECIMAL. If 50 is the max, of course that wouldn’t work.
The original poster’s solution worked perfect for me.
This worked like a champ. I was trying to connect a 64bit vista business to an XP Pro SP3 box. Added the regkey (set value to 15 hex), and restarted the server service. Thanks!!
I kept upping the DWORD value till I got to 50 and no dice. But then as soon as I made the corresponding setting on the server I was *connecting* (mapping) to, it worked. Thanks to Serge, I never would’ve thought of that otherwise.
This worked liked a charm! I set it to 50 and everything works again.
I just installed a terabyte hdd and thats when the problem started.
Satish got it right —- Check the machine you are CONNECTING TO … it also may be the problem. Just because the error message displays on the machine you are attempting to map FROM, the error could be on the machine you’re mapping to — took me days of researching this to find this now simple answer!
Worked like a charm! Using an Asus Vista Premium 64bit laptop to access a compaq XP desktop with an internal Terrabyte drive. Thanks!
I was having the same issue, and kept increasing my DWORD size incrementally, however I still was unable to connect via any machine on the network. The only program I had installed since losing access was Acronis. Did a sys-restore to just prior to the install and ~viola!~
just adding this to help people think outside the box..
For me, it worked wonderfully well in connecting a win XP 64 with a win XP 32, by doing what serge had said: add IRPStackSize = 50 (dec) to BOTH computers and restarting Server on both. Thank you very much to all contributors. I had already lost a few hours with this issue, and I only found the right answer here.
Thanks, this worked great. Made the IPStackSize entry and restarted the server service and instant access with no error! I do have a question, I checked another computer that I am able to connect to and it does not have an IPStackSize entry in the registry. The two machines have identical hardware and almost the same software. Mystery of Windows? They both worked till today when the network scanner could not open the scan folder
Testing in a XP/W7/VMware environment, I’ve found that only the server needs this registry value changed. No change is required to any computer connecting to that server. Also, restarting the Server service on the server computer is sufficient to pick up the new value. MS recommends not increasing this beyond what’s required, to minimize (undefined) performance issues.
From support.microsoft.com:
If the IRPStackSize registry entry is not present, the computer uses a default value of 0×4. Depending on the configuration of the computer’s hardware, this default value may not be large enough for the Srv service to administer shared folders on some of the physical drives. When a Windows for Workgroups client tries to access these shared directories, you receive the following message: “Path not found.” If you encounter this error message, gradually increase the value of IRPStackSize in order to find the minimum value which resolves the problem. Using a value that is larger than necessary might waste system resources. Other factors can also lead to this error message. If problems persist after you have used all the valid values for IRPStackSize, restore IRPStackSize to its original value, and seek another explanation for the error.
Thank you, Thank you, Thank you!!! You saved me hours of frustration and I appreciate it. Hopefully I can contribute something to help someone else in the future.
This was a great fix. I had just completed a fresh install of XP and had never run into network sharing problems before. I don’t know why the “not enough storage space” kind of problem showed up, but this regedit fixed the problem. Thanks!
I came across this problem recently when trying to share files between two XP/SP3 machines, and when I had upgraded from Acronis TI Home to ATIH 2010, and also to AVG antivirus s/w.
The guy who fixed it reckoned the problem was in AVG, but I’ve found other sites, notably http://www.winhlp.com who are convinced the problem is in ATI 2010.
Either way, everything is OK with stack size now 18 on both machines, ATI 2010 and Avast successfully installed.
God luck!
Thanks! Your suggested edit of the Registry fixed my problem. I was attempting to share files on my Window XP Media Center (SP3) computer with a PC runnning Vista Home (SP1) and MacBookPro running Mac OSX Version 10.6.2. The Vista Home PC and the MacBook could share files but neither could see the files on the XP Media Center server. I checked the XP server and discovered there was no Registry entry for the “IRPStackSize”. On my first attempt to correct the problem I set the value of the IRPStackSize equal to 16 (decimal) and the problem was still present. Then I set the value to 50 (decimal) and the problem was resolved. All three computers are now sharing files. Thanks again for your help. Greatly appreciated.
Regards,
…Drew
It’s definitely ATIH 2010 that was the culprit in my case. I installed it on one PC and sharing failed after the first reboot.
Thanks to the OP for his post.
Jonathan
Pingback: Prevent data loss with Acronis True Image Home 2010 | TechRepublic Out Loud | TechRepublic.com
worked perfectly with val of 50 on server only and restarted the server process!!! thanks so much.
I have been reading all day about changing this on the server you are connecting FROM. After changing this setting and rebooting my office server (Windows 2003) about 15 times…reconfiguring Symantec antivus…nothing was working. I made the change to the remote computer (Windows XP SP3) and restarted the server service and it connected without issue.
Thanks for the info.
most of you mention “just restart the server service”, which one you guys talking about. there are a lot of server service.
You guys mentioned about “Retart server service” which one you guys talking about because there are a lot of server Services.
Please let me know so I don’t have to reboot the server.
Lawrence, it’s been a while since I needed to do this, but I believe everyone is referring to the service named “server.” Since this server is only dev for my use I had no problem just restarting so I can’t say for certain.
-Mike
YES worked like a champ added the “IRPStackSize” set the value to decimal 50. Went into Services and did a restart of the service named “server”!!! AWESOME it works!
Thanks,
Tom
I have my doubts about this “100% sure” fix. Rationale: no-one seems to know a) what exactly causes this issue b) what the IRPStackSize value actually does on XPSP3.
Has anyone tried restarting the workstation, or just the server service, without touching the registry? I think it’s the restart of the service that really fixes the problem and the registry editing is just waste of everyone’s time.
Jurri,
The good old restart should always be troubleshooting 101. It never worked, but feel free to give it a try. A quick google search indicates Microsoft also recommends a similar approach, though often because the value was not present. .
http://support.microsoft.com/kb/106167
Its worked for a lot of people, and others found info from Microsoft about this too. (post 25)
Pingback: Top 10 for 2011 | Brickblog