Could not invoke guest operation error in a job when using vSphere API for Guest OS connection

KB ID: 2712
Product: Veeam Backup & Replication
Version: 9.x
Published:
Last Modified: 2018-08-24

Challenge

When Microsoft User Profile Disks (for example, in a Windows RDS farm) are used, Veeam Application Aware Image Processing through vSphere API may fail with the following error: Could not invoke guest operation.

Cause

When processing Guest OS data through vSphere API, Veeam needs to deploy a runtime component in a temporary location. C:\Windows\Temp\ folder had been used for these purposes previously. However, starting from 10.2.0 VMware tools’ version, the Temp folder location has been changed to C:\Users\username\Temp\. 

When User Profile Disks feature is used, Windows has no User’s profile temp folder unless a User is logged in (once a User is logged out, Temp folder is deleted). Hence, Veeam has no temp folder to place its components in.

Solution

VMware is planning to address this issue in one of the next VMware tools releases. As a workaround, you may want to downgrade VMware tools version to an earlier version or set up a direct network connection to the Guest OS from a Guest Interaction Proxy

More Information

Please be aware that starting from September 2018 downloading updates will require an active contract for the corresponding product.

OK

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

Couldn't find what you were looking for?

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

Request new content

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!

Orphus system