Message: "Insufficient System Resources Exist"

Hi I'm Cara, a Carbonite expert. I can walk you through this process!

Yes please, show me how!

Summary:

You receive an error message stating Insufficient system resources exist to complete the requested service.

The actual error message can vary. The most frequent errors are listed below:

• Disk Full
• Cannot Create Archives
• Cannot Create Archive
• VSS Snapshot Deleted
• VSS Snapshot Failed

The error Insufficient system resources exist to complete the requested service is logged in the LogFile.txt or ZIBLogFile.txt.

Note: The default location of the LogFile.txt and ZIBLogFile.txt is C:\Program Files\Carbonite\Carbonite Server Backup\Debug\ for 32-bit operating systems and C:\Program Files\Carbonite\Carbonite Server Backup(x64)\Debug\ for 64-bit operating systems.

Events are logged in your Application or System events that reference paged pool memory. Common event numbers include:

• 2020 from source VolSnap
• Event 5 from source VSS

This article applies to:

Cause:

If you are running a computer with Windows Server 2003 or Windows XP, and you encounter this message, it indicates the system has likely run out of paged pool memory to use for backups. This is a known issue with VSS-based backups on the Server 2003 operating system. Windows XP computers can also experience this issue on rare occasions. Microsoft has released multiple updates to address this issue over the years. However, it still occurs on some computers.

Solution:

To help resolve this problem, first make sure that all available Windows Updates have been applied to your computer. If Windows is up to date, you must increase the paged pool memory alloted to the system. The following instructions are taken directly from this Microsoft Knowledgebase Article:

1. Start Registry Editor (Regedt32.exe).
2. Locate and then click the following key in the registry: 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: PoolUsageMaximum
   Data type: REG_DWORD
   Radix: Decimal
   Value data: 60
   
   Note: Setting the value at 60 informs the Memory Manager to start the trimming process at 60 percent of PagedPoolMax rather than the default setting of 80 percent. If a threshold of 60 percent is not enough to handle spikes in activity, reduce this setting to 50 percent or 40 percent.
   
   Value name: PagedPoolSize
   Data type: REG_DWORD
   Radix: Hex
   Value data: 0xFFFFFFFF
   
   Note: Setting PagedPoolSize to 0xFFFFFFFF allocates the maximum paged pool in lieu of other resources to the computer. If you cannot enter the "x" character, enter just FFFFFFFF.
   
   The 0xFFFFFFFF PagedPoolSize setting is not recommended for use on 32-bit Windows Server 2003-based computers that have 64GB of RAM. This will potentially bring the Free System PTE entry down and can cause continuous reboot of the computer. For this configuration, carefully choose a value based on the requirements and available resources.
4. Quit Registry Editor.
5. Restart the server for the changes to take effect.