Re: XCOPY Insufficient system resources problem.
- From: Ryan <Ryan@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 20 Jun 2008 12:35:03 -0700
Did you ever find a solution to your problem? I'm havnig the same problem now
and don't have a clue what to do next. The best lead I've gotten is this:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;304101
This doesn't seem to fix my problem. I'm thinking about further reducing the
PageUsageMaximum to see if it helps on my system. Let me know if you find a
solution.
"Chris Wilhelm" wrote:
After some poking around, I found this article, which isn't really related...
but is, since it's a copying of files problem we have here, not specifically
xcopy, but copy or even copying w/ windows explorer. They all error with the
same message.
The article is this:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;304101
and suggests this:
Registry setting 1
1. Click Start, click Run, type regedit in the Open box, and then click OK.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type PoolUsageMaximum as the entry name, and then press ENTER.
5. Right-click PoolUsageMaximum, and then click Modify.
6. Click Decimal.
7. In the Value data box, type 60, and then click OK.
8. Quit Registry Editor.
9. Restart your computer.
Which indeed has rectified the issue.
"Pegasus (MVP)" wrote:
Seeing that you're talking about principles: Microsoft have decided
that xcopy.exe is superseded by robocopy.exe and that xcopy
should no longer be used, presumably in view of the long-standing
"System resources" problem.
There is another reason why robocopy is preferable (other than
it richer set of switches): It can deal with path+file names in excess
of 255 characters. Xcopy can't.
"Chris Wilhelm" <ChrisWilhelm@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:15E24C35-3539-4FF6-B105-4505622DD211@xxxxxxxxxxxxxxxx
Oh I wouldn't. I just want the problem fixed, or some discussion on how
to
fix it. It's not that I can't use robocopy, it's that I shouldn't have
to.
You know.. the principle.
"Pegasus (MVP)" wrote:
"Chris Wilhelm" <Chris Wilhelm@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:0753E4DA-D0B0-45A1-BCAB-8618DDFEE832@xxxxxxxxxxxxxxxx
I also am having this problem when trying to copy files using the
Windows
Explorer. Both systems (target and source) are Windows Server 2003 R2
SP2.
If I try and "push" files at the target, I get this error message:
"Cannot copy <filename>: Insufficient system resources exist to
complete
the
requested service."
If I try and "pull" the files from the source, I get this error
message:
"Cannot copy <filename>: Not enough server storage space is available
to
process this command."
I've searched the knowledgebase for both error messages and found
solutions
to either ancient NT products, some 2000 products, but nothing for
Server
2003.
I'm fairly certain this limitation must still be in effect or have some
bearing on my problem:
http://support.microsoft.com/kb/833167/en-us
Or less likely, something related to:
http://support.microsoft.com/kb/259837/en-us
Other details that might be pertinent:
There is enough disk space on the destination server.
I'm not using VSS in any way, but the service is enabled and runs as it
sees
fit.
Antivirus is disabled on both sides, or enabled, but the messages are
identical.
I can move the files in other ways, such as, backing them up to a
different
media, and restoring that media to the destination.
Why would you use such a tortuous solution if robocopy.exe
does it in one fell swoop?
- Prev by Date: Re: policies
- Next by Date: Re: Ntbackup
- Previous by thread: Re: XCOPY Insufficient system resources problem.
- Index(es):
Relevant Pages
|
