System Center Virtual Machine Manager 2012 R2

  1. The virtual machine (%VMName;) cannot be placed on the Hyper-V host because it has checkpoints that are in a format that ...
  2. The virtual machine (%VMName;) could not be live migrated to the virtual machine host (%VMHostName;) using this cluster configuration. ...
  3. The virtual machine (%VMName;) could not be moved using live migration to host because another live migration is in progress. ...
  4. The virtual machine (%VMName;) could not be moved using live migration to the virtualization host (%VMHostName;) because ...
  5. The virtual machine (%VMName;) has running or saved snapshots while virtualization host (%VMHostName;) has a different incompatible ...
  6. The virtual machine (%VMName;) is not compatible with the virtualization host (%VMHostName;). The virtual machine may not ...
  7. The virtual machine (%VMName;) is not compatible with the virtualization host. The virtual machine may not start or operate ...
  8. The virtual machine (%VMName;) is using processor-specific features not supported on the virtualization host (%VMHostName;). ...
  9. The virtual machine (%VMName;) is using processor-specific features not supported on the virtualization host. To allow for ...
  10. The virtual machine (%VMName;) on the host (%VMHostName;) could not be stored because it has multiple virtual hard disks ...
  11. The virtual machine (%VMName;) violates the maximum memory limit for the virtualization host (%VMHostName;). Maximum memory: ...
  12. The virtual machine (%VMName;) was not moved using live migration to the virtualization host (%VMHostName;) because the operation ...
  13. The virtual machine (%VMName;) was not moved using live migration to the virtualization host because the operation was cancelled. ...
  14. The virtual machine being created from a template must contain at least one virtual hard disk, which must be generalized. ...
  15. The virtual machine configuration %VMName; specifies a host group that does not have access to load balancer %LoadBalancerName; ...
  16. The virtual machine configuration %VMName; specifies a pass-through disk as its source and must use a target disk deployment ...
  17. The virtual machine configuration belongs to a tier that requires a load balancer connected to a single shared host group. ...
  18. The virtual machine configuration could not be added to %ComputerName; because the configuration file %FileName; could not ...
  19. The virtual machine configuration does not have a name. A virtual machine name must be specified in order to determine an ...
  20. The virtual machine configuration targets host group %HostGroupName; and does not have access to required load balancer %LoadBalancerName;. ...
  21. The virtual machine connection certificate with thumbprint %CertObjectID; could not be registered in the server certificate ...
  22. The virtual machine connection certificate with thumbprint %CertObjectID; could not be uninstalled from the server certificate ...
  23. The virtual machine couldn't be deployed with Azure Site Recovery enabled because it must be deployed in a cloud and no clouds ...
  24. The virtual machine couldn't be deployed with Azure Site Recovery enabled because it must be deployed in a cloud and no clouds ...
  25. The virtual machine has a network adapter that requires static addresses of both IPv4 and IPv6 address families. When both ...
  26. The virtual machine host %ComputerName; cannot be removed because one or more virtual machines are active on the virtual ...
  27. The virtual machine host group (%Name;) cannot be removed because it is referenced by one or more virtual switch extension ...
  28. The virtual machine host group or private cloud %Name; cannot be removed because it is referenced by one or more services, ...
  29. The virtual machine is in a cloud that's been detected by Microsoft Azure Site Recovery. This cloud will appear in the Azure ...
  30. The virtual machine is in a cloud that's not protected by the Microsoft Azure Site Recovery. Enable protection settings for ...
  31. The virtual machine is located in a cloud that hasn't been detected by Microsoft Azure Site Recovery. Enable detection in ...
  32. The Virtual Machine Manager Administrator Console is currently running one or more cmdlets. If you close the console, these ...
  33. The Virtual Machine Manager agent cannot be upgraded remotely from the computer %ComputerName; without specifying administrative ...
  34. The Virtual Machine Manager database was not created. Delete %DatabaseName;.mdf and %DatabaseName;_log.ldf if they exist ...
  35. The Virtual Machine Manager management server lost connectivity to host %VMHostName; after applying the network settings. ...
  36. The Virtual Machine Manager management server lost connectivity to host after applying the network settings. This might be ...
  37. The Virtual Machine Manager P2V Agent was not removed from the computer %ComputerName; because -Credential parameter has ...
  38. The Virtual Machine Manager service does not have required credentials to access the Operations Manager SDK service on %OperationsManagerServer;. ...
  39. The Virtual Machine Manager service on the %ServerName; server stopped while this job was running. This may have been caused ...
  40. The Virtual Machine Manager service on the %ServerName; server stopped while this system job was running. This may have been ...
  41. The Virtual Machine Manager service stopped while PRO tip %TaskID; was being implemented. That might have been caused by ...
  42. The Virtual Machine Manager service stopped while the VM Role provisioning job was running. This may have been caused by ...
  43. The virtual machine must be in either the Poweroff or Stored state before SCVMM can perform the specified hardware changes. ...
  44. The virtual machine name identifies the virtual machine to VMM. The name does not have to match the computer name of the ...
  45. The virtual machine or tier load balancer configuration requires an IP pool and there are no appropriate IP pools accessible ...
  46. The virtual machine paths %PathName; are not present on the host. Verify that all selected virtual machine paths exist and ...
  47. The virtual machine related to the virtual IP address member (%Name;) does not exist in VMM. VMM is unable to add a virtual ...
  48. The virtual machine requests %PlacementRequestValue; IOPS disk IO. Disk IO capacity is insufficient to host the virtual machine. ...
  49. The virtual machine requests %PlacementRequestValue; IOPS disk IO. The maximum disk IO accounting for reserves on host %VMHostName; ...
  50. The virtual machine requests %PlacementRequestValue; IOPS disk IO. The maximum disk IO on host %VMHostName; is %MaximumIOPS; ...
  51. The virtual machine requires a highly available virtual switch connection and the host network adapter is not attached to ...
  52. The virtual machine requires a logical switch connection and the host network adapter is not attached to a logical switch ...
  53. The virtual machine requires a virtual switch connection and the host network adapter is not attached to a virtual switch. ...
  54. The virtual machine requires NUMA spanning to be disabled and the host either has numa spanning enabled or does not support ...
  55. The virtual machine template has referenced a service setting %Name; in one or more of the following properties: Computer ...
  56. The virtual machine template is marked as capable of SAN cloning, but no physical virtual hard disk instances could be located ...
  57. The virtual machine will be migrated using the following options based on your placement defaults for the hosts, the default ...
  58. The Virtual Machine will not be accessible to the cloud after storing the Virtual Machine in the library or deploying it ...
  59. The virtual machine with name %VMName; requires Hyper-V Recovery Manager protection, but the cloud does not provide this ...
  60. The virtual machine workload %VMName; cannot be deployed to the hardware supporting cloud %CloudName;]. Contact the cloud ...
  61. The virtual machine workload %VMName; requires a MAC pool that supports its virtualization platform and the most appropriate ...
  62. The virtual machine workload %VMName; specifies requirements that cannot be satisfied by the hardware supporting cloud %CloudName;]. ...
  63. The virtual machine workload %VMName; specifies settings that are not allowed by any capability profile supported by the ...
  64. The virtual machine workload %VMName; specifies settings that are not allowed by any capability profile supported by the ...
  65. The virtual machine's saved state could not be accessed because the user has insufficient access rights on the %ServerName; ...
  66. The virtual machine's saved state is not compatible with this version of Virtualization Service on the %ServerName; server. ...
  67. The virtual machines cannot be shut down because Virtual Guest Services are not installed on the guest operating system (%ObjectList;) ...
  68. The virtual network adapter %Name; MAC: %MACAddress; doesn't have a CA (customer address) assigned from the VMSubnet related ...
  69. The virtual network adapter cannot be connected because the virtual switch (%VirtualNetworkName;) on the host is not in compliance ...
  70. The virtual network adapter extension port profile %Name; is already present in the list of virtual network adapter extension ...
  71. The virtual network adapter for the virtual machine (%VMName;) is connected to a virtual switch (%VirtualNetworkName;) that ...
  72. The virtual NUMA limits specified are invalid because the settings would result in an invalid number of virtual NUMA nodes. ...
  73. The virtual subnet Id (%VirtualSubnetId;) configured on the virtual network adapter is incompatible with the VMNetwork (%VMNetworkName;) ...
  74. The virtual subnet Id (%VirtualSubnetId;) configured on the virtual network adapter is incompatible with the VMSubnet (%VMSubnetName;) ...
  75. The Virtual Switch %VirtualNetworkName; associated with the virtual machine %VMName; does not exist on host %VMHostName;. ...