File copy fails with the error “Insufficient System Resources”

Suraj — Thu, 19 Feb 2009 11:10:00 GMT

Ø Apply KB 312362 http://support.microsoft.com/kb/312362

Ø Configure the below keys to maximize server resources. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanserver\Parameters subkey, configure the following entries:
• Name: MaxWorkItems Data Type: REG_DWORD Value data: 8196 (decimal)
• Name: MaxMpxCt Data Type: REG_DWORD Value data: 2048 (decimal)
• Name: MaxRawWorkItems Data Type: REG_DWORD Value data: 512 (decimal)
• Name: MaxFreeConnections Data Type: REG_DWORD Value data: 100 (decimal)
• Name: MinFreeConnections Data Type: REG_DWORD Value data: 32 (decimal)

In the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanworkstation\Parameters subkey, configure the following entry:
• Name: MaxCmds Data Type: REG_DWORD Value data: 2048 (decimal)

By default, your registry does not have a Configuration Manager subkey. To create the key, locate and then right-click the following subkey: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager Point to New , and then click Key . Type Configuration Manager , and then press ENTER. In the new HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Configuration Manager subkey, configure the following entry:
• Name: RegistryLazyFlushInterval Data Type: REG_DWORD Value data: 60 (decimal)

=============================
Reason for adding or modifying above keys
==============================
<http://support.microsoft.com/?id=312362>
By default, the Memory Manager tries to trim allocated paged pool memory when the system reaches 80 percent of the total paged pool. Depending on the system configuration, a possible maximum paged pool memory on a computer can be 343MB and 80 percent of this number is 274MB

By tuning the Memory Manager to start the trimming process earlier (for example, when it reaches 60 percent), it would be possible to keep up with the paged pool demand during sudden peak usage, and avoid running out of paged pool memory.

This problem can occur because the functions used by all of the copy utilities use buffered input/output (I/O) to transfer data from the source file to the destination file. Whenever buffered I/O is performed on a file, there is a paged pool memory overhead requirement that is proportional to the size of the file. Because paged pool memory is a limited resource, there is an upper limit on the size of file that can be copied.

Since all of the paged pool that is required to buffer an entire file is allocated when the first read or write procedure is performed on the file, the file copy operation fails immediately, instead of half way through the operation.

Regarding PAE

The CopyFileEx and CopyFile functions are used by all of the standard file-copy utilities. Because these functions use buffered I/O, the maximum size of a file that you can copy depends on the amount of paged-pool memory that is available at the start of the copy procedure and whether the Physical Address Extensions (PAE) kernel which allows access to memory above 4 gigabytes [GB] is in use. With the standard kernel, 1 kilobyte (KB) of paged pool is required for each megabyte (MB) of file size that is opened for buffered I/O. Because there are two files involved in a copy procedure, 2 KB of paged pool are required for each MB in the source file.

When the PAE kernel is used, the overhead is doubled and 4 KB of paged pool is required for each MB in the source file.

Useful information to provide to Microsoft Support in case of issues with Server Performance

Roop — Thu, 06 Dec 2007 10:27:00 GMT

In case you have got issues with your Server Performance like intermittently becomming unresponsive,generating event id's like 2020,2019,2021 or you are suspecting a problem with resource depletion;then these are the set of logs an engineer from Microsoft would require to help you diagonise the problem.

MPS Reports:

http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd915706/MPSRPT_SETUPPerf.EXE

If you have any questions regarding the usage or operations of the MPS Reporting Tool please review the link below:
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd915706/MPSRPT_SetupPerf_Readme.txt

Perfmon:

Go to the PC (without any issues). Start, Run and type "perfmon" (without quotation marks) and press OK.

- Expand Performance Logs and Alerts. Highlight Counter Logs and right click in the right pane to bring up a menu. From this menu, select "New Log Settings". Give this log a name.

- Press Add counters. Type in the the server name that we want to monitor ( Example: in the format: \\Servundefined

- Add "All counters" and "All instances" each of the following objects:

             Memory
             Network Interface
             Objects
             Paging File
             Physical Disk
             Process
             Processor
             Redirector
             Server
             Server Work Queues
             System
             Thread
         - Set the Interval for every N minutes.

N = 5 minutes – Issue happens once a day

= 10 minutes- Issue happens once a week

= 15 minutes –Issue happens one in 15 days

= 30 minutes –Issue happens once in 30 days

- Click on the Log Files tab and set Log file type to Binary Circular File and a Limit of 500,000 KB. Please make sure where the Log is currently save have enough disk space to accommodate.

- Go to the schedule tab, set the schedule for "Stop Log- Manually" and "Start Log- Manually.

Here is an article for reference: 248345 How to Create a Log Using System Monitor in Windows 2000 <<<<http://support.microsoft.com/?id=248345>>>>

Note : Logs needs to be taken till the issue occurs next time.

Poolmon

http://support.microsoft.com/kb/177415

Note:Logging needs to be done till the issue occurs next time.

PERFGURU : 2020

File copy fails with the error “Insufficient System Resources”

Useful information to provide to Microsoft Support in case of issues with Server Performance