1-800-691-1991 | 9am - 8pm ET

Job fails to start due to timeout


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]


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.


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

Veeam Agent for Microsoft Windows, Veeam Backup & Replication
VBR - 7,8,9.x | VAW - 2.x,3.x
Last Modified:
Please rate how helpful this article was to you:
5 out of 5 based on 2 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

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

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.


error icon

Oops! Something went wrong.

Please go back try again later.