none
Win 7 Pro x64 Error 0x8007046a: Not enough server storage is available to process this command.

    Question

  • I installed Win 7 Pro x64 on a reasonably decent  machine (Nvidia nForce 680i SLI, core 2 duo, 4 gig ram). It was a clean install on a freshly formatted partition. While copying a large bunch of files from another machine on the LAN, I get "Error 0x8007046a: Not enough server storage is available to process this command." It does give me the option to retry and continue, but the error inevitably pops up again later during the copy. Googling the error, I found a reference to it, suggesting I go to the registry and increase the IRPStackSize (but this article was not specific to Win 7). I tried increasing it as high as 32 hex. This reduces the frequency of the error, but does not eliminate it completely. Also, I now see a new error sometimes that says, "Too many files are currently in use. Quit one or more programs and then try again." That's odd, because I don't have anything else running. I haven't seen these errors when copying files to different partitions on the machine, so I assume it's something to do with network.
    Monday, December 28, 2009 6:34 PM

All replies

  • The error, 0x8007046a, means "Not enough server storage is available to process this command".

    Whenever I've seen that (outside of the software updates download context), it has been either a rights issue, or a lack of available memory.


    Here's an article that may also relate to your case http://technet.microsoft.com/en-us/library/cc776049(WS.10,loband).aspx,  also check the search results of the forum http://social.technet.microsoft.com/Search/en-US/?Query=0x8007046a and see if any of those articles help.



    MCSE, MCSA, MCDST [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
    Tuesday, December 29, 2009 1:23 AM
  • Thanks for your reply cdobbs. After more testing, I'm beginning to suspect the issue may be hardware, possibly a flaky Ethernet controller. Thanks again,
    Ken.C

    Tuesday, December 29, 2009 7:30 AM
  • You're welcome Ken, let us know the result if you change out the NIC.
    MCSE, MCSA, MCDST [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
    Tuesday, December 29, 2009 8:07 AM

  • Well, it looks like it's not hardware. I ran Memtest for a few hours  to verify the ram is good. I changed the NIC. The problem persists.

    I installed Win 7 pro 32 bit version, and get the same errors. I monitored Task Manager to check memory usage, threads and handles. Memory use hovered around 550meg during the copy. No thread or handle leaks were observed. As a sanity check, I installed good old reliable XP and the problem goes away. 

    So to summarize, it's not hardware. I don't suspect the NIC drivers are at fault ( I downloaded the latest Win 7 x64 driver set  from the manufacturer) The IRPStackSize registry tweaks don't work. I'm not running IIS. It's just a simple folder copy of about 50 gigs from an XP machine on my LAN.  The problem is reproducible on Windows 7, both 64 and 32 bit versions, but not on XP. Any ideas anyone?
    Thanks,
    Ken.C

    Wednesday, December 30, 2009 10:05 PM
  • Ken.C,

    Have you tried swapping out the switch you have the two computers on?  You could also hardset your IP addresses and use a cross-over cable if you do not  have another switch.  I haven't had that specific error, however I know when I was using an old linksys hub it caused odd errors similar to that as it didn't handle data collisions well.  Windows 7 may be more fickle about handling errors in the data stream.

    Otherwise, how big is the largest file you are copying?

    You mentioned it was a fresh install, however did you install any Anti-Virus software already?  Some Real-Time scans can definitely cough up when scanning large files.

    Amaranthe
    Wednesday, December 30, 2009 10:26 PM

  • Thanks Amaranthe,

    I disabled the virus scanner while I'm trying to solve this issue. The files are jpgs averaging 4-5 meg. (All the pictures I've taken with my Canon 40D)
    I swapped the switch, and now more often that not I get the other error, "Too many files are currently in use. Quit one or more programs and then try again."

    It has no problem with big files. I can copy 25 gig of 3-4gig  .iso files with errors. It chokes on smaller files.

    I also noticed if I go over to the the source machine, it's slowing way way down during the copy. Many of its tasks become unresponsive until the copying ends. Strange, it doesn't make sense that the source machine would go cripple when feeding the Win 7 machine. I mean it's simply streaming packets down an an Ethernet port and should have no idea what OS the other machine is running, right?
     
    Also, the problem is reproducible when The Win 7 machine copys from any machine on the LAN.

    This is perplexing. I really wanted to like Windows 7...
    Thanks again,
    KenC
    Thursday, December 31, 2009 3:39 AM
  • Hi KenC,

     

    You can restart the machine in Safe Mode with Networking and copy large files in this mode for a test. To do this, we can eliminate whether the issue is caused by third party programs or not.

     

    If the error still persists, please capture the error message and upload it for research.

     

    Thanks,

    Novak

     

     

    Thursday, December 31, 2009 6:48 AM

  • Thanks for the suggestion Novak,

    The problem persists even in Safe Mode. Typical of this issue, it copied about 2000 of 15,000 photos, then halted on a 712 KB file. A "Copy File" dialog pops up with the following text: "An unexpected error is keeping you from copying the file. If you continue to receive this error, you can use the error code to search for help with this problem.

    "Error 0x8007046a: Not enough server storage is available to process this command."

    So does this suggest it's a Windows 7 problem, not 3rd party drivers?

    Thanks,
    Ken.C

    Sunday, January 3, 2010 4:45 AM
  • Hi,

    Does the error persist when copying a smaller file? Also, does the error occur when copying the same file to different partition on the local machine?

    Meanwhile, please also verify the Volume Shadow Copy service and make sure the status is started.

    Thanks,
    Novak
    Monday, January 4, 2010 8:47 AM

  • Hi Novak,

    The errors do not seem to be associated with any particular file - they occur randomly during a folder copy/paste from another machine on my LAN.
    I have not seen the error copying huge files (like a folder full of 3-4 gig iso files), but it happens regularly on groups of small to medium files.
    I have not seen the error when copying a single file.
    I have not seen the error copying a folder full of medium size files between different partitions on the Win7 machine. It occurs ONLY between the Win7 machine and other machines on the LAN, which is why I posted the issue on the Network section of the forum.

    The Windows 7 machine will not allow me to start the VSS (Volume Shadow Copy) service -- "access denied" Heck, I'm the admin, so what's up with that?

    Thanks you for your reply.
    Ken.C

    Tuesday, January 5, 2010 1:01 AM
  • Since the service cannot be started, I suggest you try following steps and verify it again.

     

    1. Temporarily turn off firewall and antivirus, and then verify the service again. If the error persists, I suggest you perform a Clean Boot to check the result.

     

    2. Use the System File Checker tool to scan the system files.

     

    If the issue persists, you may need perform an In-Place upgrade for a test. If needed, I will provide the detail steps later.

     

    Thanks,

    Novak

     

    Tuesday, January 5, 2010 5:21 AM


  • Thanks Novak,

    I turned off the firewall and antivirus. Cold Reboot.  VSS does not start. SFC reports no bad files. Copy problem remains. A couple of times the error that popped up was."Too Many files open. Try closing some programs and try again". (This makes no sense, since no other programs or processes are running other than whatever the system has running)  As stated in the beginning of the thread, I have seen this error before, especially when I tweaked the  IRPStackSize in the registry (The only article I found regarding 0x8007046a suggested increasing the registry value) It did not solve the problem and the registry has been restored to default. Besides, since this is a system copy/paste, it's up to the OS to manage the files, file handles, memory and whatever overhead goes along with copy/paste.

    BTW, this is the second clean install of Win7 Pro x64. After the first install, being unable to solve the problem, I reformatted the c: partition and did a clean install of Win 7 Pro X86. Still had the same errors with the 32 bit version. After another reformat and clean install of Win XP (32 bit), the problem does not occur.  But my desire is to run Win 7 Pro x64, so once again I reformatted the drive, and did a clan install of Win 7 x64. The error, of course, returned.

    I'm open to trying the "In-Place upgrade" if you think it may shed some light on what's going on.

    Thanks,
    KenC



    Tuesday, January 5, 2010 7:44 AM
  • Hi Ken,
    I am having the very same issue. I am using Windows 7 Ultimate x64. I get the "Too Many files open. Try closing some programs and try again" message when copying a large group of small onto my linux based file server (samba share). Like you, copy seems to choke only with smaller files, even a few kB. On the contrary, I can copy multi-GB files no problem.

    thanks,
    Luca
    Tuesday, January 5, 2010 11:28 PM
  • Ken I noticed you never did say what AV and firewalls may/may not be installed. Seems Kaspersky and a few others can be culprits and some 3rd party firewalls have to be totally uninstalled (not disabled) to cure this (some are not compatible). So I thought I'd throw that out there.
    MCSE, MCSA, MCDST [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
    Tuesday, January 5, 2010 11:43 PM
  • Hi CDOBBS,

    The firewall is the default MS one that automatically installs. I use Avast virus protection, but I disabled it when I began troubleshooting the issue. Since then, I've done a few reformats and reinstalls of Windows without installing any virus protection while we investigate the problems.

    Greetings Luca,
    Well at least I'm not alone reporting this issue.  I CAN copy groups of large multi-gig files. Like you it happens only with groups of smaller files. I wonder if it's some sort of timing bottleneck as it's trying to open and close a whole bunch of files in rapid sequence...

    Thanks,
    KenC

     
    Wednesday, January 6, 2010 1:03 AM
  • many folks have found that Nvidia is not ready for win 7, your MB has a new type memory controller which is designed to take advanage of the bigger
    cashes in the new intel chips only it is not working to well.
    it's very picky.

    Memory errors are happening for many folks with this new memory controller.
    Wednesday, January 6, 2010 2:02 AM
  • many folks have found that Nvidia is not ready for win 7, your MB has a new type memory controller which is designed to take advanage of the bigger
    cashes in the new intel chips only it is not working to well.
    it's very picky.

    Memory errors are happening for many folks with this new memory controller.
    I have completely different hardware though (here some info on my system):

    OS Name    Microsoft Windows 7 Ultimate  6.1.7600
    System Manufacturer    Supermicro, model X8SIE
    Processor    Intel(R) Xeon(R) CPU           X3450  @ 2.67GHz
    Installed Physical Memory (RAM)    16.0 GB (ECC Registered)

    I first reported this issue onto to the unRAID forum (my file server OS), and immediately found another person having the very same issue. So now it's at least three of us. :-)

    Ken, is the machine you are transferring to/from also unix based (like in my case)?

    Luca


    Wednesday, January 6, 2010 2:24 AM
  • I get this same error quite frequently. I have a file share on a Windows 7 x64 Ultimate machine. When I get the "not enough server storage available" message on my XP client, I go to the Windows 7 machine and restart the Server service. This only fixes it temporarily. The problem comes back a short while later.

    It seems to happen exclusively when doing peer-to-peer networking with a mixed environment (Windows 7 and other clients). When the error is occurring, I can go to my Windows 7 laptop client and it has no problems accessing the file share; only the XP client experiences the error.

    I know that in Windows 7 there is both the "homegroup" sharing mechanism and the usual file share. XP clients only get access to the usual file share. Windows 7 clients get access to both. But when the error occurs, my Windows 7 laptop can still access the file share by either means (generic share or via homegroup).

    My take on this is that, bottom line, Windows 7 does not play nicely with other OSs for peer-to-peer networking. I've read other forum posts that show this started in Vista, and was simply not fixed in Windows 7. I hope this gets fixed, because most homeowners are not going to buy a Windows Server, and some of our older machines can't run Windows 7.
    • Proposed as answer by Ecossé Geek Thursday, October 5, 2017 2:44 PM
    Wednesday, January 6, 2010 5:54 AM
  • Hi,

     

    To troubleshoot the issue, please try to do an In-Place Upgrade to repair the system.

     

    1. Start the computer by using the current Operating System.

    2. Insert the Windows 7 DVD in the computer's DVD drive.

    3. Use one of the following procedures, as appropriate:

     

    If Windows automatically detects the DVD, the Install now screen appears. Click Install now.

    If Windows does not automatically detect the DVD, follow these steps:

     

    a. Click the Start Button, type Drive:\setup.exe in the start search box and then click OK.

     

    Note: Drive is the drive letter of the computer's DVD drive.

     

    b. Click Install now.

     

    4. When you reach the "Which type of installation do you want?" screen, click Upgrade to upgrade the current operating system to Windows 7.

     

    Thanks,

    Novak

    Wednesday, January 6, 2010 9:25 AM
  • There is no networking issue with older OS, the issue you are seeing are hardware / software related, there are more people without networking issue than people with them.

    I now have over 100 win 7 workstations on networks connecting to servers from 2000 to 2008, to linux boxes, to NAS boxes.

    We have no issues what so ever that are not solve by replacing old nonsupported gear (routers / switches / network cards)

    My architect customers move VAST amounts if data day it and day out.


    with a x64 OS things that work under 32 bit can be flaky (this is a drivers isse in most cases)

    if you have Nvidia chipset MB I would start there, as Nvidia has not gotten the kinks worked out (search here or google to see that)

    I ban those off the wall systems from my networks, No AMD / no Nvidia / no VIA allowed.

    (well one AMD laptop is allowed but as soon as it is dead..NO MORE)
    Wednesday, January 6, 2010 2:10 PM
  • There is no networking issue with older OS, the issue you are seeing are hardware / software related, there are more people without networking issue than people with them.

    I now have over 100 win 7 workstations on networks connecting to servers from 2000 to 2008, to linux boxes, to NAS boxes.

    We have no issues what so ever that are not solve by replacing old nonsupported gear (routers / switches / network cards)

    My architect customers move VAST amounts if data day it and day out.

    with a x64 OS things that work under 32 bit can be flaky (this is a drivers isse in most cases)

    if you have Nvidia chipset MB I would start there, as Nvidia has not gotten the kinks worked out (search here or google to see that)

    I may not have been clear about my findings here. I am not talking about an environment where actual Windows Server OSs are providing file shares, regardless of version. I'm talking about strictly peer-to-peer networking, with no actual server OSs or domains involved. The file share is being served from the Windows 7 machine, not a real Windows Server OS. And also there is no domain server to assist with authenticating users, either.

    I can't prove or say conclusively that it's due to non-Windows 7 clients, but it does seem to be supported by actual observation and by other reports on the web.

    In my small peer-to-peer network (one desktop with a file share serving one other desktop and two laptops), only the client with Windows 7 on it has no issues connecting to the file share. When the problem occurs, the two XP clients can't connect and the Windows 7 laptop has no trouble at all.

    I don't believe it's the switch/router, because all machines are going through the same switch (including the Win7 client that has no problems).

    The XP clients both have different network cards (one is a laptop the other is a desktop). Yes, the desktop has an NVIDIA chipset, but the laptop does not.

    Again, in my observation the problem only affects clients that are not running Windows 7. This is consistent with the original poster (Ken C.), who in his 3rd post revealed that his client is an XP machine too. A Linux user in this thread also reported the problem. I've never seen the problem reported by someone connecting FROM a Windows 7 machine TO another Windows 7 machine. I've Googled several posts and forums on the net, and there is a definite trend that it's seen when Windows 7 (or Vista) is serving files peer-to-peer and the clients are not running Windows 7.

    Wednesday, January 6, 2010 6:41 PM

  • My Windows 7 machine does have an Nvidia MB. However, if it was truly a "hardware" (memory controller) problem, wouldn't it also manifest itself on XP? XP works perfectly on this hardware. Win 7 x64 and Win 7 x86 both have the problem.

    Hi Luca
    The problem happens when the Win 7 machine attempts to copy a folder from an XP peer on my LAN and write to it's local hard drive.
    While I don't claim to be a network expert, I would think the OS on the remote machine should be irrelevant, because they are communicating via TCP/IP. Does anyone with more knowledge than I care to comment on this?
     
    Hi Novak,
    If I understand correctly, you want me to "upgrade" Windows 7 to Windows 7?

    Thanks to all!
    Ken.C

    Thursday, January 7, 2010 12:58 AM

  • My Windows 7 machine does have an Nvidia MB. However, if it was truly a "hardware" (memory controller) problem, wouldn't it also manifest itself on XP? XP works perfectly on this hardware. Win 7 x64 and Win 7 x86 both have the problem.

    Hi Luca
    The problem happens when the Win 7 machine attempts to copy a folder from an XP peer on my LAN and write to it's local hard drive.
    While I don't claim to be a network expert, I would think the OS on the remote machine should be irrelevant, because they are communicating via TCP/IP. Does anyone with more knowledge than I care to comment on this?
     
    Hi Novak,
    If I understand correctly, you want me to "upgrade" Windows 7 to Windows 7?

    Thanks to all!
    Ken.C

    Ken, I was wondering because someone on the unraid forum suggested that this may be caused by a Samba bug:
    https://bugs.launchpad.net/samba/+bug/462172
    Incidentally, the samba fix which was recommended did not work for me.

    One thing that may be of help in troubleshooting this. In my experience, it seems as though an actual transfer to/from the windows 7 client is not even necessary for the error to occur!  Even just transferring data within the unix server (for instance, moving files from one share to a different share on the same server, windows 7 still gives me the "too many files" error. I hope I explained this clearly enough. :-)

    Novak, I am also curious what the in-place upgrade you suggest is supposed to accomplish.

    Luca
    Thursday, January 7, 2010 4:27 AM
  • Luca,

    I was able to copy the folder to the machine's d: partition was when I installed XP on the c: partition as a sanity check. Later I put Win 7 back on the c: partition and did a a couple tests copying the folder between d: and e:. I did not encounter any errors so I went back to troubleshooting the network copy issue which, for me,  is consistently reproducible.

    I took a look at the samba bug (Thanks for the link). Looks a lot like my problem, but one of the tests I did was to monitor Task Manager for memory, thread, and handle usage during the copy. A good chunk of memory was allocated, but nowhere near maxed out, and I didn't see any spike occur in threads or handles. It doesn't appear to be a resource shortage, even though the error messages suggest it is... I'm still baffled.

    Thanks,
    Ken.C

     
    Thursday, January 7, 2010 7:33 AM
  • Ken,
    I never encountered this error while copying files locally on my windows 7 machine either. What I was trying to say was: if I connect from the win 7 box to 2 different shares on my unix server, and copy or move a bunch of small files from one share to the other, I am sure I am going to see this error popping up.

    So it seems that at least one network connection has to be involved, win 7 box to samba share(s) in my case. I guess my point was that no heavy network traffic needs to be happening for the error to occur. Which is consistent with the fact that I (and I believe you) can move tens of gigabytes in large files without any errors. Probably you got what I meant the first time, but English not being my first language, I always try to make sure I made myself clear. :-)

    Friday, January 8, 2010 12:26 AM
  • Hi Luca.

    Your English is excellent, my friend.

    Yeah, it seems to be Win 7 network related. What you're describing is consistent because it routes the copy through the Win 7 machine's NIC and back to the other UNIX share.

    Perhaps this weekend, I will install Win 7 on a different machine. It's a little under powered for Win7, but it will give us another test point. It's an Intel MB and I'd like to see if a different chipset works or not.

    Ken.C




    Friday, January 8, 2010 1:59 AM
  • I didn't know the problem also occurs when Win7 is on the client-side of a peer-to-peer file share connection. What does seem to be consistent is that one of the two machines is not a Windows 7 machine (or Vista for that matter).

    So far I guess I'm still sticking with my statement that perhaps Windows 7 doesn't play nicely with other OSs on a peer-to-peer network. (And for this purpose I would guess that Vista and Windows 7 do play nicely with each other, being effectively the same OS in this regard).
    Friday, January 8, 2010 8:38 PM

  • The latest test results:
    I installed Win 7 Pro 32-bit on an older machine  [P4-3.2ghz, 1-gig ram, 160 gig IDE drive, Intel MB/chipset].  Doing the same test, copying a 50 gig folder full of files from an XP peer I get the same error, 0x8007046a: Not enough server storage is available to process this command."

    Ok, this eliminates the NVidia chipset as being the culprit,  and lends some credence to Jay's comment that Win7/Vista does not "play nice" with other OS's. Next, I'd like to test two Win7 machines, peer to peer to confirm this, but since I can't get freaking test folder onto either Win7 machine, I'll have to install XP again on one of them [sigh].

    Thanks to everyone for their comments.
    Ken.C


    Monday, January 11, 2010 4:51 AM
  • Was anyone able to find the answer to this error.  I'm getting it on a Windows 2008 x64 server.  Another line of thought is could the OS be trying to cache the file image somewhere (particularly the c: drive) during the copy?
    Thursday, January 21, 2010 9:10 PM
  • Ken, one helpful person on the unraid forum recommended trying teracopy (http://www.codesector.com/teracopy.php), a utility alternative to the built-in windows copy. Interestingly enough, this seems to have fixed the "too many files" problem. I don't know why this is, but I'll take it. :-) You may want to give it a shot.
    Sunday, January 24, 2010 6:19 AM
  • I have experienced this error several times now when copying files from XP/Samba to a Vista/7 share.  What appears to be happening is that Vista/7 use the SMB2 protocol for networking and XP uses SMB1 and aparently there are some bugs going from one to the other.  So by disabling the SMB2 protocol on the Vista/7 machine you revert it to using SMB1 and it seems to fix the problem.  To make sure you have this issue, check your eventlogs for the event id 2017, complaning that "The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations" when in fact there is plenty of nonpaged pool memory available. 

    To fix the problem, you need to add a key to your registry to diable SMB2: Open regedit, go to HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/LanmanServer/Parameters, now create a DWORD key with the name SMB2 and set the value to 0.  Restart your computer and the problem should stop.  To remove the fix and re-enable SMB2, just delete the key from the registry and reboot. 

    Good luck!

    -Tim
    Tuesday, January 26, 2010 6:03 PM
  • According to a Wikipedia article, SMB2 only gets used when the connection is between Vista/7 machines, and the server reverts to SMB1 when communicating with other machines. If that is accurate, then it would seem that disabling SMB2 is of no benefit to this problem.

    That doesn't explain why you apparently saw the problem solved. I haven't tried that, so can't really say.
    Tuesday, January 26, 2010 10:19 PM

  • I didn't see event ID 2017 in any of the event logs ( in fact it's curious that no errors or warnings are ever logged in association with this error. However, I tested Shadardrin's suggestion anyway, setting the registry to disable SMB2, but it does not correct the problem.

    Next, I tried Luca's suggestion and installed Teracopy. This utility effectively replaces Explorer's copy/paste functionality. Lo and behold, the folder copies over perfectly.

    My conclusion at this time is that it's Microsoft's bug. [Sigh]  Changing the NIC, cables & switch had no effect, and it's only reproducible on Windows 7 (Don't know about Vista. Like many, I abandoned Vista after a couple days of it refusing to install the software I wanted to run.)

    I'm not going to burn any more time on this unless the Teracopy workaround fails. I'll check back on this thread periodically to see if anyone finds a concrete solution ( I still consider this question "unanswered")

    Thanks to everyone for their input and suggestions, especially Luca and to Code Sector for coming up with a utility that can do what Win 7 can't -- copy/paste a folder!

    Ken.C  
    Monday, February 1, 2010 5:16 AM
  • Next, I tried Luca's suggestion and installed Teracopy. This utility effectively replaces Explorer's copy/paste functionality. Lo and behold, the folder copies over perfectly.


    Ken, glad it worked out for you. It does look like a win 7 bug. In-place upgrade indeed... :-)
    Thursday, February 4, 2010 5:47 AM
  • I may have found the answer
     
    Apparently you need to tell Windows that you want to use the machine as a file server and that it should allocate resources accordingly.  Set the following registry key to ‘1′:

    HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache

    and set the following registry key to ‘3′:

    HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size

    After making these changes and restarting, I haven’t seen this issue arise again

     
    • Proposed as answer by Anthony Lake Wednesday, April 28, 2010 8:57 PM
    Thursday, February 4, 2010 2:19 PM
  • I may have found the answer
     
    Apparently you need to tell Windows that you want to use the machine as a file server and that it should allocate resources accordingly.  Set the following registry key to ‘1′:

    HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache

    and set the following registry key to ‘3′:

    HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size

    After making these changes and restarting, I haven’t seen this issue arise again

     
    This actually worked... I could not reproduce the "too many files" error after applying those registry changes and rebooting.
    Thanks krbaugh.
    Tuesday, February 9, 2010 5:41 AM
  • Glad to hear it it sure fixed my problems!!
    Tuesday, February 9, 2010 2:55 PM
  • This is the only solution I have found that works, across both Vista and Win7. Thank you krbaugh, dissolved hours of frustration, searching and incorrect advice in 2 minutes + reboot.
    Wednesday, April 28, 2010 10:14 AM
  • Hi All,

    Have been facing this error since very long time. I encounter this error after sometime of booting my machine. Everything stops. I work as a developer. So, Asp.net compilation also stops. Same error "Not enough storage is available to process this command". I am using Microsoft security essentials as my anti virus and default firewall . It is Win 7 32 bit machine. I have tried both the fixes "Lanmanserver IRPStackSize" and the one mentioned here. Initially after the install i was not facing this issue. Bt after some days this error started showing up. Please help.

     

    Regards

    Mohit Thakral

    Wednesday, July 7, 2010 12:12 PM
  • Hi all

    I'm facing the same problem running Win7 Pro, 64bit version. Recently i've reinstaled my machine with a fresh new Win 7 (previously using Win XP 32bit).

    When i'm playing DOTA, while in the game after like 15-20 mins the game crashes and i get the same error mesage  "Not enough server storage is available to process this command."

    This happened twice in consecutive games.As you can see i'm not having this problem while copying files or simillar situations (like i've read about sharing files between Win 7 & Win XP) but while playing Warcraft Dota.

    Any ideea how to solve this issue ?

    Thx

    Wednesday, July 21, 2010 12:40 PM
  • I had this problem which cannot copy large size files and getting the error 0x8007046a. but I solved the problem in this way.

    The windows page size in source server was low. The source server had 32GB RAM but the page file was only 2GB. I increased the page file and set it to System Manage Size in source server and it solved my problem.

    Please test this in your case and let me now if your problem goes away too!


    Hossein Tavakkoli
    Wednesday, November 3, 2010 6:10 AM
  • Running 32bit win7 ultimate on a computer here with NAS drives. Same server storage error when copying over the network using winxp just copying a few MBs of files. I found several posts related to this from old NT and Vista/Win7 all failed for me. I move TBs of files around locally without issue. So if we set the mtu to a size that fits down the pipe without fragmentation it works. You can use ping with various packet sizes with defragment disabled to see what fits. Not sure why this shiny new OS can't fragment packets properly but its bound to be more secure than win98, right?

     

    ping -f -l 1500 192.168.1.1

    Fails with fragmentation message

     

    ping -f -l 1472 192.168.1.1

    No problem

     

    Set mtu lower than what needs to be fragmented using netsh and files copy over network again.

    netsh interface ipv4 set subinterface "Local Area Connection" mtu=nnnn store=persistent

    Until a real fix comes out.

    you can also set it in the other os to correct this if necessary.

     

     



    • Proposed as answer by fishdogman Monday, October 10, 2011 3:10 PM
    • Edited by fishdogman Monday, October 10, 2011 3:19 PM
    Monday, October 10, 2011 2:33 PM
  • How is it more efficient and how does that help the problem when win7 64bit has the same problem?

     

    My phone can copy files over a network without issue.

    Monday, October 10, 2011 3:24 PM
  • Ever since I edited the two registry entries as krbaugh suggested on 2/4/2010 I have not had a single case of this issue. I think he's totally right, the mass-consumer editions of Windows are not optimized for use as a file server. Windows 7 had big improvements, but only when sharing with itself.

    Making it easy or obvious how to change that might undercut their marketing of Windows Home Server (which is already dying off). As I mentioned, Windows 7 actually does work well if you're ONLY sharing files with other Windows 7 users, which probably lines up with their strategy of dropping support for their older OSs.

    Monday, October 10, 2011 3:53 PM
  • In some cases and i have simple problem i simple changed the file type you said you was moving photos well i would just put the photos in a rar file or a zip file or my favorite a 7z file and they get compressed and then transferred the files also when moving files ur page filing needs to get set HIGH!!! and also when transferring data from one pc to another pc depending on ur network it will be slow you are REALLY!!! better off taking the HDD out of the PC and putting it in the new PC and transfer ALL THE DATA  with in the local machine it self EVEN IF its a laptop HDD i do this all the time for customer more effectively and ALOT FASTER data transferring over the internet or even over a local network i have had files get corrupted and incomplete because something gets lost in the transfer! BETTER OFF DATA TRANSFER ON THE ONE MACHINE IT SELF!!!!!

    ADVISED FOR ANY ONE THAT DOES HIGH VOLUMES ON DATA TRANSFERRING!!!!

    Thank you,
    Sanders, Chris

    Tuesday, September 4, 2012 1:57 AM
  • I think you found the answer to the problem. May have solved a problem before a big Win 7 migration roll out. Still doing some more repetitive testing but looks good so far.
    Friday, September 21, 2012 8:40 PM
  • I used the above to solve a Large file ( 297 GB) copy failure from a Server 2003 R2 to a 2008 R2 server.

    I tried ROBOCOPY, XCOPY, and Explorer.  All had the same failure.

    Copy failed on another 295 GB file.  Copy succeeded on many other smaller ( 1 to 35 GB ) files.

    Copy failed from Server2003 R2 to another 2008 R2 Server.

    Copy failed from 2008 R2 server to the 2003 R2 Server computer.  Ah ha.  In both directions the copy fails....

    Copy worked from 2008 R2 server to another 2008 R2 server. 

    All three computers were on the same VLAN and the same switch.

    I tried increasing the Virtual Memory Total Pageing File size on the 2008 R2 servers.  Copy still failed.

    I tried increasing the Virtual Memory Total Pageing File size on the 2003 R2 server to 5.6 GB.  Copy succeeded on the 295GB file.  Copy failed on the 297GB file.

    I tried increasing the Virtual Memory Total Pageing File size on the 2003 R2 server to 20 GB.  Copy succeeded on the 297GB file.

    Good luck on solving your 0x08007046A problem!

    Wednesday, May 1, 2013 3:47 PM
  • I ran into this issue yesterday that initially was giving me an error when I was trying to install a new deployment of AutoCAD 2014 from the install files on a 2003 R2 server to a 2008 R2 server.  What I was getting in that instance was an error saying "the copy functions cannot be used".  Eventually I tried copying the install files to the 2008 server and got a similar error. This attempt to copy seemed to crap out when it got to a file that was about 140MB in size.  Later in the day I tried to copy a 160MB file from my win 7 64 bit workstation to the 2003 R2 server and got the 0s08007046a error.  As reported by Terry Crain I too was able to resolve this error by changing the page file settings on the 2003 R2 server from settings that had been specified (and were too low for the amount of RAM in the server) to allowing the system to manage the page file.
    Thursday, May 29, 2014 12:19 PM