I'm in the process of moving all my stuff over from my old Athlon 3200 XP box running XP Pro SP3 to my new Core 2 Duo 8400 box running Vista Home Premium SP1. The two machines are networked using a router/ethernet switch.
I believe the problem may be related to the way Vista handles shares as there are no internet access problems from the Vista machine.
I'm using DOpus 9.1.1.7.3307 x86 20/01/2009 11:39:11 on the XP machine to copy to a network share on the Vista machine (a folder other than the default "Public" folder).
More than once per session, DOpus will throw up an error message along the lines of "not enough space on the server".
If I restart the "Server" service on the Vista machine, clicking on "Retry" lets the copy proceed. I suspect this might be a Vista problem rather than DOpus, but thought I'd mention it here in the hope that if someone here has come across the problem, a solution might be known.
It's unlikely to be Opus-specific. I haven't heard of the problem before so don't know what to suggest, sorry.
Difficult to search for an answer without knowing the exact error message but there are some potentially useful results if you search for "not enough space" and vista:
One of them talks about the C-drive being used as a temporary location as files are copied across, and that can run out of space even though the ultimate destination has room, but it sounds like that only applies to Windows Home Server and not a normal Vista machine...
Sounds like it can also happen if the destination machine is low on memory, too.
OK, it just happened again. The exact error message is:
Copy - Directory Opus
An error occurred moving '02 Andheriya.mp3':
Not enough server storage is available to process this command. (1130)
Retry Skip Skip All Abort
Right now there is 99.7GB free on C: and 613GB free on the volume I'm copying to. Temp directories etc are in default locations and the machine has 4GB RAM with nothing else running.
As I said before, restarting the "Server" service on the Vista machine let's the copy/move operation continue after clicking Retry.
I would hazzard a guess that something is making this service stop and although the options are set to automatically restart it, it doesn't always. I don't know enough about the innards of Vista to know why it would stop in the first place.
I tried the suggestion you made and created a new IRPStackSize Registry key. So far I've tried 5, 12 and also the documented max of 50. (Also tried undocumented 127, same result).
Whilst it seemed to make a slight improvement (more files copied before stopping), the whole operation doesn't always complete. It seems the more files there are to copy, the more of a chance there is of the operation failing. We're talking >1000 files.
This time however I noticed in the Vista Event Viewer that EventID 2017 associated with the Srv service was being generated everytime the copy failed. The description for this ID is:
"The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations."
I've seen plenty of posts in forums with the same error being discussed and the same symptoms but haven't come across any with confirmed fixes yet.
Forgot to mention, I also saw a fix that suggested disabling the new SMB2 stuff in Vista could fix this so I tried that as well. It seems to help a little - again can copy a few 1000 files over ok, but large copies still fail.
When I updated NAV on one of our XP machines, and added MySql and a few other things, and I ended up with the same issue. The solution was to adjust the IRPStackSize and also check the list of programs using the resources. I think a reboot between changes was required.
Can't quite remember the URLs but a search of Google with "Not enough server storage is available to process this command" and playing eventually gave the answers. For example
When copying stuff over, there's hardly anything running on the Vista machine. Yes I'm running Antivirus s/w (Kaspersky AV), but I'd rather not turn that off while copying as I wouldn't want anything suspect getting onto the new machine.
How does one check what other programs are using these resources?
The specific event being generated now is 2017 (nonpaged pool allocation limit busted).
I do think the problem is a Vista problem and not a DOpus one, but I rarely use Windows Explorer to do file copies (especially large numbers) as it's just not as good as DOpus at carrying on after "In use" or "Access Denied" interruptions.