If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
What a pile
XP Pro sees two folders on my other PC (Win 7).
On home LAN via Cat5 no WiFi involved. I copied a bunch of files over and checked free disk giving me over 1TByte. I tried to copy more files and XP says: --------------------------- My Documents --------------------------- W:\ is not accessible. Not enough server storage is available to process this command. and --------------------------- My Documents --------------------------- Z:\ is not accessible. Not enough server storage is available to process this command. What the ... How do I fix this? |
Ads |
#2
|
|||
|
|||
What a pile
APCUser wrote:
XP Pro sees two folders on my other PC (Win 7). On home LAN via Cat5 no WiFi involved. I copied a bunch of files over and checked free disk giving me over 1TByte. I tried to copy more files and XP says: --------------------------- My Documents --------------------------- W:\ is not accessible. Not enough server storage is available to process this command. and --------------------------- My Documents --------------------------- Z:\ is not accessible. Not enough server storage is available to process this command. What the ... How do I fix this? You can pop the entire error message into Google. What that tells me, is there is more than one root cause possible. The error message may not be precise enough for the job (it could have used better wording, or identified an actual resource). For sure, it does *not* mean you're out of disk. That hasn't appear in anything I've looked at so far. But there are other resources you could run out of. IRPStack space, Paged Pool (memory), Non-Paged Pool (memory). ******** IRPStackSize. Not likely to be applicable, except if maybe you set this in Regedit manually to a small number. This is an ancient KB. My registry doesn't have this entry. The next article gives the WinXP default. https://support.microsoft.com/en-ca/kb/106167 They give a range of values here. Default 15 for WinXP, Range 11 to 50 https://kc.mcafee.com/corporate/inde...9932&pmv=print There could be more than one root cause. https://social.technet.microsoft.com...m=winservergen And seems far removed from the mechanism described here. https://en.wikipedia.org/wiki/I/O_request_packet I can also find references to running out of Paged Pool or Unpaged Pool (part of system memory). The expected error message should be different though, so it's not clear why your exact error message pops up because of that. Maybe the IRPStack uses one of the Pools for memory ? Perhaps that's how it works. I've had that problem (Pool exhaustion) on this system, and tend to blame it on VPC2007. Mainly because I can't figure out what else it might be :-) The "drivers" that VPC2007 installs, run all the time, even if the software is not running. I've had one case, where the floppy interleave factor was being blown - and simply by starting VPC2007, the problem corrected itself instantly. https://support.microsoft.com/en-us/kb/304101 It might be quite difficult to identify what piece of software is actually doing this. Is it an AV product ? Somehow you need the affected subsystem to "confess" :-) Paul |
#3
|
|||
|
|||
What a pile
On 01 Sep 2016, APCUser wrote in
microsoft.public.windowsxp.general: XP Pro sees two folders on my other PC (Win 7). On home LAN via Cat5 no WiFi involved. I copied a bunch of files over and checked free disk giving me over 1TByte. I tried to copy more files and XP says: --------------------------- My Documents --------------------------- W:\ is not accessible. Not enough server storage is available to process this command. and --------------------------- My Documents --------------------------- Z:\ is not accessible. Not enough server storage is available to process this command. What the ... How do I fix this? In my experience, that error message is misleading. It usually there's a problem with the server service on the server machine. First easiest thing to do is reboot the server (Win7 machine). Wouldn't hurt to reboot the XP machine, either. |
Thread Tools | |
Display Modes | |
|
|