Job fails to start due to timeout

Challenge

If more than 100 jobs are running simultaneously, and the user attempts to start more jobs, they may fail to start with the following error message:

Error Job <JobName> cannot be started. SessionId: <UUID>, Timeout: [361 sec]

Cause

This issue is due to many session running which causes the Veeam services to be impacted by the Desktop Heap limitation. This is because the Desktop Heap size for services is much smaller than that for applications.

Solution

To resolve this issue the Desktop Heap size must be increased via a registry modification.

Because this change will affect the desktop heap of all services (also known as non-interactive window stations), do not make the new value larger than necessary.

1. Run regedit and navigate to
   HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems

2. Find string named "Windows"

3. Edit the Value data to change the third "SharedSection" value only.
   Do not modify any other values.

4. Press OK
5. Reboot the machine

More Information

More information can be found at http://support.microsoft.com/kb/947246