Select Page

Hyper-V VMs fail with error 0x80070569 while Starting or Live Migrating

Symptom

Virtual Machines on Hyper-V fail with error 0x80070569 to Start, Stop or fail to move (Live Migration or Quick Migration).   Also new Virtual Machines fail.  The error messages may vary, but if running the command:  GPUPDATE /force fixes the situation, at least temporarily.   Creating new Virtual Machines fail as well with varying error messages.

Error Messages

This condition can appear in various screens or functions.  Some of the error messages include:

  • Starting or Live Migrating Hyper-V virtual machines may fail with error 0x80070569
  • Error 0x80070569 (‘VM_NAME’ failed to start worker process: Logon Failure: The user has not been granted the requested logon type at this computer.)
  • Logon failure: the user has not been granted the requested logon type at this computer
  • Cluster resource ‘Virtual Machine <vmname> of type ‘Virtual Machine’ in clustered role ‘<vmname>’ failed. The error code was ‘0x569’
  • Failed to bring the resource ‘Virtual Machine <vmname>’ online.  Error Code 0x80071736
  • An error occurred while opening virtual machine settings for ‘Virtual Machine <vmname>’
  • Hyper-V encountered an error trying to access an object on computer ‘localhost’ because the object was not found
  • Cluster Validation message:  An error occurred while configuring the virtual machine resource ‘Virtual Machine Configuration <vmname>
  • Cluster Validation message:  An error occurred while configuring the virtual machine role for ‘<vmname>’
  • Cluster Validation message:  The operation failed because either the specified cluster node is not the owner of the resource, or the node is not a possible owner of the resource

Cause

If the errors appear on only a single Hyper-V computer, the cause may be the Hyper-V computer has lost or has an incomplete connection to the domain – such as a credentials mismatch.   This may be remedied by removing the computer from the domain then adding the computer back.

Otherwise, the cause is likely a permissions error inherited as a GPO policy.  The NT Virtual Machine\Virtual Machines special identity does not have the Log on as a Service right on the Hyper-V host computer.

The GPO policy change will be required.  Quick instructions are below.   A more in-depth explanation are in the links below.

  • Logon as a Domain Administrator
  • Install the Group Policy Management feature from the Server Manager console
  • After installation, open the GPMC MMC snap-in and browse to the policy that manages User Rights
  • Edit the policy to include NT Virtual Machine\Virtual Machines in the entries for Log on as a Service
  • Close the policy editor and initiate a gpupdate /force on the Hyper-V host computer to refresh policy. (You may need to wait several minutes for Active Directory replication to occur).

Additional Technical References

Screen Shots

KB9-Screen-Shot-1

KB9-Screen-Shot-2

 

KB9 - Screen Shot 3

KB9-Screen-Shot-4

 

KB9 - Screen Shot 5

Was this article helpful?

1 Comment

  1. Abubakkar Sithik

    Hi

    Unable to find NT Virtual Machine\Virtual Machines id.Also i tried manually adding NT Virtual Machine\Virtual Machines Log on as a Service i cann’t find.Could you please advice how to resolved this issue.

    Thanks

    Reply

Submit a Comment

Your email address will not be published. Required fields are marked *