When your server is under a heavy load, the Server may repeatedly give the following symptoms that indicate that the server is out of paged pool memory.
Symptoms:
- RDP: Unable to connect (click connect and nothing happens)
- UltraBac: Skipped Error: (1450 – Insufficient system resources exist to complete the requested service.)
- Explorer: Not enough server storage is available to process the command
- Outlook: Cannot expand “networked” PST files
Cause:
- More files are open than the memory cache manager can handle. As a result, the cache manager has exhausted the available paged pool memory.
- The backup program has tried to back up a file whose size is larger than the backup API can access on that version of the operating system. This has the same result (that is, the paged pool is exhausted).
Fix:
- Set Memory Manager to start the trimming process at 60 percent of PagedPoolMax rather than the default setting of 80 percent. This should be enough to handle spikes in activity. If not, reduce this setting to 50 percent or 40 percent.
- Start Registry Editor (Regedt32.exe).
- Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management
- Add, Value: PoolUsageMaximum
Data type: REG_DWORD
Radix: Decimal
Value data: 60 - Reboot.