Operational Defect Database
BugZero found this defect 3583 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb1909
Job Fails to Start Due to Timeout Caused by Desktop Heap Allocation Failure
Last update date:
4/13/2023
Affected products:
Veeam Backup & Replication
Veeam Agent for Microsoft Windows
Affected releases:
ALL
Fixed releases:
No fixed releases provided.
Description:
Challenge
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:
Cause
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.
Solution
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.
More Information
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.
