Job fails to start due to timeout

KB ID:
1909
Product:
Veeam Backup & Replication;Veeam Agent for Microsoft Windows
Version:
VBR - 7,8,9.x | VAW - 2.x,3.x
Published:
Last Modified:
2019-09-23

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

Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.

OK

Rate the quality of this KB article: 
3.9 out of 5 based on 21 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text:

Submit