These resource levels are set via the SharedSection parameter in the Windows string value in the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\SubSystems.
For example, the SharedSection parameter might look like this:
SharedSection=1024,20480,768
The first number, 1024, is the size of the system-wide heap, common to all desktops.
The second number, 20480, is the size of each interactive desktop heap. This is available when an analysis is run interactively.
The third number, 768, is the size of each non-interactive desktop heap. This is available when an analysis is run by a service, like when running as a scheduled task SQL Server services or AppAssure services.
Typically, that third number is smaller than the second, i.e. the interactive desktop heap is larger than the non-interactive desktop heap.
The solution is to modify that registry setting to increase the third number of the SharedSection parameter, i.e. increase the size of the non-interactive desktop heap.
For example, you could change this:
SharedSection=1024,20480,768
to this:
SharedSection=1024,20480,4096
You must re-boot the server for the change to take effect.
Regarding the warning at the top of this document: if you make one of these 3 heap size settings too small, the server may not have enough resources to start.
Windows Registry Disclaimer:
Quest does not provide support for problems that arise from improper modification of the
registry. The Windows registry contains information critical to your computer and applications. Make
sure you back up the registry before modifying it. For more information on the Windows Registry
Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the
Microsoft Windows registry” at Microsoft Support.