Hyper-V exports fail with The operation with VHD virtual disk failed. While the base error is generic, if you find the additional errors listed below, this KB will resolve this specific issue.
Starting with the Core UI | Events you will see the failed job with the Stack Trace listed below. To confirm the issue, look for the additional error in AppRecovery logs and WMI events in Application Events. NOTE: You may not see all the WMI errors.
Stack Trace Example:
The operation with VHD virtual disk failed
Replay.Common.Contracts.Virtualization.HyperVException: The operation with VHD virtual disk failed ---> System.AggregateException: One or more errors occurred. ---> System.InvalidOperationException: Error message: 'SERVERFOUR' failed to add device 'Virtual Hard Disk'. (Virtual machine ID A16B8D83-8F0D-4D8A-BBDA-518178EF172F)
CategoryInfo: NotSpecified: (Microsoft.HyperV.PowerShell.VMTask:VMTask) [Add-VMHardDiskDrive], VirtualizationOperationFailedException
AppRecovery Log Example:
ERROR 2016-06-08T08:05:23  - Replay.Common.Implementation.Virtualization.HyperV.Version2.HyperVWmi2VirtualMachine (Export Volume Images VM Location)
Failed to attach VHD 'E:\Hyper-V\SERVERNAME\disk0.vhdx' to Ide controller 0/1. This may indicate Microsoft issue https://support.microsoft.com/en-us/kb/2779204. Use the script to update group policy to avoid this issue.
WMI Errors and Warnings in Application Events:
This issue occurs because the NT Virtual Machine\Virtual Machines special identity does not have the Log on as a Service right on the Hyper-V host computer. Usually, the Virtual Machine Management Service (VMMS) replaces this user permission at every Group Policy refresh to ensure it is always present. However, you may notice that Group Policy refresh does not function correctly in certain situations.
For more information please see Starting or Live Migrating Hyper-V virtual machines may fail with error 0x80070569 on Windows Server 2012-based computers.
© 2020 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 使用条款 隐私