System Center Virtual Machine Manager 2012 R2

  1. Verify the virtual machine is in a Running status, the Virtual Guest Services is installed, and the Heartbeat and Data Exchange ...
  2. Verify the virtual switch name by refreshing the Host Properties dialogue box, go to the Hardware tab and click the Virtual ...
  3. Verify the Windows Assessment and Deployment Kit is correctly installed, and check the file Logs\dism.log under the Windows ...
  4. VHDs %Name; cannot be marked equivalent of VHD %ObjectName; (Family name: %FamilyName;, Release: %Release;) because they ...
  5. VHDs %Name; cannot be marked equivalent with family name %FamilyName; and release %Release; because they have different VHD ...
  6. View the errors in the Virtual Machine Manager Setup log file %SetupLogFile;, view the errors and make the required changes. ...
  7. VIP names must start with a letter, must contain only alphanumeric characters, hyphens (-), periods (.), or underscores (_), ...
  8. Virtual Guest Services are not available for the operating system on virtual machine %VMName; residing on host %VMHostName;. ...
  9. Virtual machine %VMName; cannot be cloned or migrated. To be cloned or migrated, a virtual machine must be stored in the ...
  10. Virtual machine %VMName; cannot be cloned. A virtual machine must be in Running, Poweroff or Stored state in order to be ...
  11. Virtual machine %VMName; cannot be deployed from host %VMHostName; because the host is in a state that has limited management ...
  12. Virtual machine %VMName; cannot be live migrated to host %VMHostName; since the XenServer Tools are not installed on the ...
  13. Virtual Machine %VMName; cannot be migrated with SAN transfer type because it contains an ISO - %FileName; that is not in ...
  14. Virtual machine %VMName; cannot be modified because Virtual Guest Services is not installed on the guest operating system ...
  15. Virtual machine %VMName; cannot be moved to host %VMHostName;. The source and destination hosts have incompatible virtualization ...
  16. Virtual machine %VMName; cannot be moved to host %VMHostName;. Virtual machine migrations between XenServer hosts are only ...
  17. Virtual machine %VMName; cannot be moved to host. The source and destination hosts have incompatible virtualization software. ...
  18. Virtual machine %VMName; cannot be moved to host. Virtual machine migrations between XenServer hosts are only supported for ...
  19. Virtual machine %VMName; cannot be placed on host %VMHostName; because the host is a node in a host cluster that is managed ...
  20. Virtual machine %VMName; cannot be placed on the host because the host is a node in a host cluster that is managed by Virtual ...
  21. Virtual machine %VMName; cannot be transferred because it is associated with two files with identical names - %SourceFile1;, ...
  22. Virtual Machine %VMName; cannot be transferred over the SAN because it contains an ISO - %FileName; that is shared with other ...
  23. Virtual Machine %VMName; cannot be transferred over the SAN because it contains virtual disks that are shared with other ...
  24. Virtual machine %VMName; cannot be transferred. To be transferred, a virtual machine must be stopped, shut down, in a saved ...
  25. Virtual machine %VMName; cannot be transferred. Volume %SystemVolumeDriveLetter; on server %VMHostName; is unavailable for ...
  26. Virtual machine %VMName; cannot be used for any checkpoint actions. For checkpoint actions, a virtual machine must be running, ...
  27. Virtual machine %VMName; could not be cloned because it has checkpoints. That functionality is not supported for Hyper-V ...
  28. Virtual machine %VMName; could not be cloned because the virtual machine has checkpoints. This functionality is not supported ...
  29. Virtual machine %VMName; could not be moved because it has checkpoints. Checkpoints are not supported for VMware virtual ...
  30. Virtual machine %VMName; could not be moved to Hyper-V host %VMHostName; because it has checkpoints. These checkpoints must ...
  31. Virtual machine %VMName; could not be moved to Hyper-V host because it has checkpoints. These checkpoints must be permanently ...
  32. Virtual machine %VMName; could not be moved to virtual machine host %VMHostName; because the target path was not specified. ...
  33. Virtual machine %VMName; creation cannot restart. To restart a virtual machine must be in the Creation Failed or Customization ...
  34. Virtual machine %VMName; has Microsoft Azure Site Recovery protection enabled. You can't move it to replication group '%TargetRGName;' ...
  35. Virtual machine %VMName; is protected by replication group %TargetRGName;. You can't move it to a location that's unprotected, ...
  36. Virtual machine %VMName; isn't associated with a replication group and couldn't be moved to a location that's protected by ...
  37. Virtual machine %VMName; on host %VMHostName; does not have any virtual hard disks. Virtual Guest Services cannot be installed ...
  38. Virtual machine %VMName; requires protected storage but the replication group %RGName; associated with the virtual machine ...
  39. Virtual Machine %VMName; resides on a LUN, which is not visible to the Virtual Disk Service (VDS) hardware provider on machine ...
  40. Virtual Machine %VMName; resides on a LUN, which is not visible to the Virtual Disk Service (VDS) hardware provider on machine. ...
  41. Virtual machine %VMName; targets host group %HostGroupName;. Host %VMHostName; is not part of this host group or its contained ...
  42. Virtual machine %VMName; targets host group %HostGroupName;. Host is not part of this host group or its contained host groups. ...
  43. Virtual machine %VMName; which has pass-through disks, cannot be transferred over the SAN because it has snapshots or it ...
  44. Virtual machine '%VMName;' is enabled for Microsoft Azure Site Recovery protection. Moving this virtual machine across replication ...
  45. Virtual machine '%VMName;' is highly available and is being enabled for Microsoft Azure Site Recovery protection. Moving ...
  46. Virtual machine customization is not supported for the %OSName; operating system. Please use the -NoCustomization parameter ...
  47. Virtual Machine Manager (%Name;:%Id;) has encountered an error. Windows generated an error report with the following parameters: ...
  48. Virtual Machine Manager (VMM) encountered an error while creating the answer file for the deployment. This indicates a problem ...
  49. Virtual Machine Manager agent communication is blocked. The version of the VMM agent (%CurrentVersion;) on the computer %ComputerName; ...
  50. Virtual Machine Manager Agent is not supported on this operating system. For more information, see 'Supported Operating Systems ...
  51. Virtual Machine Manager can automatically convert virtual machines created with other virtualization technologies to virtual ...
  52. Virtual Machine Manager cannot add %ComputerName; as a Hyper-V host because the Hyper-V version detected on %ComputerName; ...
  53. Virtual Machine Manager cannot add %ComputerName; as a virtual machine host because VMware ESX Server version %SoftwareVersion; ...
  54. Virtual Machine Manager cannot add %ComputerName; as a virtualization manager because %ComputerName; is not running vCenter ...
  55. Virtual Machine Manager cannot add %ComputerName; as a virtualization manager because VMware vCenter Server version %SoftwareVersion; ...
  56. Virtual Machine Manager cannot add a host that is running a 32-bit Windows Server operating system. Therefore, the selected ...
  57. Virtual Machine Manager cannot add host %ComputerName; because the version of Virtual Server installed on the host is not ...
  58. Virtual Machine Manager cannot add one or more objects to the scope of user role %UserRoleName; because the objects are not ...
  59. Virtual Machine Manager cannot add the library servers to the scope because the state of one or more of the library servers ...
  60. Virtual Machine Manager cannot add virtual hard disk %FileName; because its format is not compatible with other disks on ...
  61. Virtual Machine Manager cannot add virtual hard disk %FileName; because its format is not compatible with other disks on ...
  62. Virtual Machine Manager cannot clone virtual machine %VMName; on the Virtual Server host to a Hyper-V host because the virtual ...
  63. Virtual Machine Manager cannot complete the VirtualCenter action on server %ServerName; because of the following error: %DetailedErrorMessage; ...
  64. Virtual Machine Manager cannot complete the VirtualCenter action on server %ServerName; because of the following error: %DetailedErrorMessage;. ...
  65. Virtual Machine Manager cannot complete the VirtualCenter action on the server %ServerName; because of the following error: ...
  66. Virtual Machine Manager cannot detect a heartbeat from the specified virtual machine. Either the virtual machine is not running ...
  67. Virtual Machine Manager cannot discover partition %PartitionNumber; on virtual hard disk %FilePath;. File will not be injected ...
  68. Virtual Machine Manager cannot enable the Hyper-V role on %ComputerName;. If you are not sure whether the host has hardware-assisted ...
  69. Virtual Machine Manager cannot link ISO %FileName; to virtual machine %VMName; on host %VMHostName;. The file is not accessible ...
  70. Virtual Machine Manager cannot locate the boot or system volume on virtual machine %VMName;. The resulting virtual machine ...
  71. Virtual Machine Manager cannot perform hardware configuration changes on virtual machine %VMName; because it is stored in ...
  72. Virtual Machine Manager cannot process the request because an error occurred while authenticating %ServerName;. Possible ...
  73. Virtual Machine Manager cannot transfer the virtual machine %VMName; over the SAN because the virtual machine resides on ...
  74. Virtual Machine Manager cannot transfer virtual machine %VMName; over the SAN because the VMM management server %VMHostName; ...
  75. Virtual Machine Manager cannot transfer virtual machine %VMName; over the SAN because the VMM management server does not ...