The timeout error displayed in Veeam Backup & Replication can be caused by various factors. This article specifically addresses a scenario where the Windows OS experiences a 'heap allocation' failure.
Please note that the solution provided in this article is only applicable if you have identified Event ID #243 in the Windows System Event Logs (eventvwr.msc). If this event is not present, this article may not provide a relevant solution.
In Veeam Backup & Replication, 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:
By default, Veeam services are run as the LocalSystem account. As a result, all processes are started under NT AUTHORITY\SYSTEM context. If the Windows OS is running out of Desktop Heap memory, new processes can't be started.
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.
Open Registry Editor (regedit) and navigate to HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems
Within the SubSystems key will be a Value named Windows.
Double-click on the value named Windows.
Find the part labeled "ShareSection=" followed by three sets of numbers separated by commas.
The third SharedSection value is the size of the desktop heap for each desktop that is associated with a non-interactive window station. The value is in kilobytes (KB).
Modify the third value, and change it to 2048. Do not modify any other values.
Click OK to commit the changes.
Reboot the machine.
The steps provided may not always resolve the heap issue. If a third-party service causes the desktop heap memory leak, the problem may return several days\weeks after OS restart. If this occurs, we recommend contacting Microsoft support for low-level debugging assistance.
Starting with Server 2012 R2, Microsoft has changed the core logic of the heap memory management system, and publicly available tools used with previous versions to check per process head usage are incompatible. If you encounter the Veeam error listed in this KB and Event ID# 243 is found in the event viewer, we advise opening a case with Microsoft support to request assistance tracking down any service memory leaks.
To submit feedback regarding this article, please click this link: Send Article Feedback To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Your feedback has been received and will be reviewed.