ERROR 1450 Insufficient system resources exist to complete

[guest]

I tried to backup about 55 directories that contain about 300,000 files each.
The files average about 15-30 bytes each. Each directory is about 10 MB or
less, but the properties list them at over 1 GB each, on disk (I only have a
40 MB hard drive so I guess they don't really take that much space). I was
backing them up to an 80 GB drive with over 60 GB free space.

Xcopy and Robocopy gave me an "Insufficient system resources exist to
complete the request" error after copying about four directories. Robocopy
tried again every 30 seconds and was able to copy a few dozen more files at a
time before the same error would occurred.

The closest solution I found was
http://support.microsoft.com/kb/304101/en-us but it doesn't mention XP. It
covers NT 4.0 though. Would it apply to XP? In my registry I was able to find
the registry subkey that's mentioned in the NT instructions, so I'm hopeful
it will work, but I figured I should ask first.

[guest]

I would say yes. Use the Windows 2000/Server 2003 solution. To
alleviate the problem you might want to copy the files in several
smaller operations instead of all at once. 16.5 million files is a lot
of file entries to deal with, even if the files are small.

[guest]

Ok, I did. Then I found the same registry edit suggested for XP in solution
2 at
http://www.msfn.org/board/index.php?...dpost&p=429020
but it's listed with other registry tweeks and says "these need to be made as
a set" so I'm thinking about making every change in solution 2 before I
reboot and try my download again.

[guest]

The Microsoft article that you referred to earlier (kb304101) says as much:

"You may have to change two registry settings. You must always change
the first setting. Depending on the configuration of your system, you
may also have to change the second setting."

Although the error message appears to be the same, the problem that the
poster is having on the msfn board is a bit different than yours, he is
having difficulties saving to network drives, from what I can see the
workstations conk out saving to the server, similar but not the same
problem as you are experiencing. Be careful changing some of these
values, you may end up with a whole new set of problems. Try the
solution proposed by Microsoft and see what happens. Take it easy,
don't go changing Memory Management values unless you are absolutely
certain of the consequences! Backup (export) the registry key(s) before
you do these changes and do the change one at a time and then test the
changes. I don't see what the lanmanserver values would have to do with
your problems, I wouldn't change these.

[guest]

Quoted from Microsoft resolution:
Windows Server 2003 and Windows 2000Important This section, method, or task cont...Windows Server 2003 and Windows 2000
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows


You may have to change two registry settings. You must always change the first setting. Depending on the configuration of your system, you may also have to change the second setting.
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.

Important
◦Use 60 as your initial value. If your backup does not succeed, use 40 as your value. If that does not work, you must change the behavior of your backup program to reduce the demand of paged pool. If the value works, you may want to increase the value by approximately 25 percent until the backup does not work. If the backup is unsuccessful, use the second registry setting that is described in this article.
◦Make sure that the value for this registry setting is not more than 60.
◦If you are using the /3GB switch, use 40 as your initial setting. Note that this value is a percentage value.
8.Quit Registry Editor.
9.Restart your computer.
Because you must test these settings during the most stressful backups, you may have to wait a month for a whole backup cycle to complete if you are not sure which backup consumes the most resources. Because of this situation, Microsoft recommends that you test low values first. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
312362 (http://support.microsoft.com/kb/312362/ ) Server is unable to allocate memory from the system paged pool
Registry setting 2
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 PagedPoolSize as the entry name, and then press ENTER.
5.Right-click PagedPoolSize, and then click Modify.
6.Click Hexadecimal.
7.In the Value data box, type a value of FFFFFFFF, and then click OK.

Important
◦Setting PagedPoolSize to 0xFFFFFFFF (-1) allocates the maximum paged pool instead of other resources to the computer. This is typically required on a domain controller or a terminal server. By default, most Windows 2000 systems seem to be limited to a paged pool maximum size of 160 MB. You can verify this by downloading the kernel debuggers from the public Web site and opening a kernel dump in the debugger that you want to use. The command to use is !vm. This shows a paged pool maximum of 163840 KB, for example. Adding this value reduces the Page Table Entries (PTEs) that are available on a system and extends the paged pool maximum to 343 MB in Windows 2000. The paged pool maximum size can be extended to a larger value in Windows Server 2003.

Note The default and maximum paged pool values for Windows Server 2003 are much larger than in Windows 2000. Typically, the Windows Server 2003 values are at least 50 percent higher than the values found in Windows 2000. These larger values makes it more unlikely that you will experience the issue where paged pool values contribute to the problem that is described in this article. However, it is still possible that this issue may occur.
◦This value restricts the system PTEs that are available. PTEs are another unrelated system resource that your system uses. This setting may cause your operating system to stop unexpectedly and to display a stop 0x3F error on a blue screen when it starts. You can recover from this by using the Last Known Good restart option on the system restart menu or recovery console. Use Performance Monitor to view the Free System Page Table Entries counter. You can add the PagePoolSize setting if the observed free values are over 40,000.
◦If you are running /3GB and /PAE together, do not set this setting without extensive testing and before you establish exactly how many system PTES you must have in your environment. You will probably see values in the range of 10,000-20,000 free. Use the articles to configure paged pool memory but never drop below 10,000 free system PTEs. Do not set this to any other value if you are using the /3GB switch. The only supported values are 0, 0A000000, and FFFFFFFF.
8.Quit Registry Editor.
9.Restart your computer.
For more information about how to avoid and resolve this problem, click the following article numbers to view the articles in the Microsoft Knowledge Base:
256004 (http://support.microsoft.com/kb/256004/ ) How to troubleshoot "STOP 0x0000003F" and "STOP 0x000000D8" error messages in Windows Server 2003, Windows XP, and Windows 2000
Back to the top
Windows NT 4.0
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows


Note You must be using Windows NT 4.0 Service Pack 6a.
Resolve the first problem
1.Start Registry Editor (Regedt32.exe).
2.Locate and then click the following registry subkey :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory_Management
3.On the Edit menu, click Add Value, and then add the following registry value:
Value name: UnusedFileCache
Data type: REG_DWORD
Radix: Decimal
Value data: 15
Note This number represents the percent of pool that can be consumed by unused segments. A value of 0 indicates that the system will use the default behavior that is similar to Windows NT 4.0 Service Pack 3. A value of 5 through 40 indicates that the system will trim the unused file cache based on pool usage. 5 is most aggressive (that is, it increases the size of the cache the least) and 40 is least aggressive (that is, it lets the cache grow the largest before it trims the cache.)

Important
◦Use 15 as your initial value. If your backup does not succeed, use 5 as your value. If this does not work, you must either change the behavior of your backup program to reduce the demand of paged pool, or you must upgrade to Windows 2000, where more than double the paged pool is available (for more information, see the "Windows 2000" section). If this value works, you may want to increase it by approximately 20 percent until the backup is unsuccessful. If the backup is unsuccessful, use the second registry setting that is described in this article.
◦If you are using the/3GB switch, use 5 as your initial setting.
4.Quit Registry Editor.
5.Restart your computer.
Because you must test these settings during the most stressful backups, you may have to wait a month for a whole backup cycle to complete if you are not sure which backup consumes the most resources. Because of this, Microsoft recommends that you test low values first. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
171458 (http://support.microsoft.com/kb/171458/ ) Windows NT may fail on request to open large files
Resolve the second problem
One possible resolution is to restrict the backup so that it backs up one file at a time. This may or may not work depending on the sizes of the files to be backed up. (It is expected to work on files that are smaller than 180 gigabytes [GB].) You can also try this resolution if you are backing up several large files, but each file is smaller than 180 GB. You must follow the steps to resolve the first problem also. For files larger than 180 GB, no workaround exists. Therefore, you must upgrade the system to Windows 2000. If you try to back up the system remotely as a workaround, you will experience the same problem.
1.Start Registry Editor (Regedt32.exe).
2.Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory_Management3.On the Edit menu, click Add Value, and then add the following registry value:
Value name: DisablePagedPoolHint
Data type: REG_DWORD
Radix: Decimal
Value data: 1
4.Quit Registry Editor.
5.Restart your computer.