Operational Defect Database
BugZero found this defect 1607 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb3077
Veeam Agent backup job fails with "Failed to call RPC function 'TestCompatible': Error code: 0x80070008. Cannot initialize COM runtime" error
Last update date:
7/10/2023
Affected products:
Veeam Agent for Microsoft Windows
Affected releases:
ALL
Fixed releases:
No fixed releases provided.
Description:
Challenge
A Veeam Agent backup job managed by the backup server fails with the following error:Processing Error: Failed to call RPC function 'TestCompatible': Error code: 0x80070008. Cannot initialize COM runtime.
Cause
When a backup job starts, Veeam Backup & Replication connects to the Veeam Agent machine to initiate the backup process. The connection is based on Windows API and uses RPC and WMI queries. If Microsoft Windows is low on desktop heap memory for services running under LocalSystem account, Microsoft Windows can reject the incoming queries. As a result, the following message will be displayed in System Event Log (eventvwr.msc) of the Veeam Agent machine: Log Name:System Source:Win32k Event ID:243 Task Category: None Level:Warning Keywords:Classic User:N/A Computer: Description: A desktop heap allocation failed. DCOM errors (Event ID 10010) can be found in System Event Log of the Veeam Agent machine too.
Solution
Article Applicability This article is relevant to a specific scenario where the Windows OS suffers from a 'heap allocation' failure. The solution provided in this article should only be performed if Event ID# 243 is found in the Windows System Event Logs (eventvwr.msc).
More Information
A previous version of this KB article documented the use of a tool to identify the process responsible for a memory leak, which may have been causing the heap memory issue. However, beginning with Server 2012 R2, Microsoft changed the core logic of the heap memory management system, rendering those publicly available tools incompatible. If you come across the Veeam error mentioned in this KB and find Event ID# 243 in the event viewer, we recommend opening a case with Microsoft support to seek assistance in locating any service memory leaks.
