System Center Virtual Machine Manager 2012

  1. VMM is unable to attach the specified logical network definition name (%Name;) to the VMNetwork because the logical network ...
  2. VMM is unable to attach the specified logical network definition name (%Name;) to the VMNetwork because the logical network ...
  3. VMM is unable to attach the specified VMSubnet (%Name;) to the VMNetwork because the VMSubnet is already in use. Contact ...
  4. VMM is unable to complete the request. The connection to the VMM agent on the virtualization server (%ServerName;) was lost. ...
  5. VMM is unable to complete the requested file transfer. The connection to the HTTP server %BITSServerName; could not be established. ...
  6. VMM is unable to connect to the VMM management server %ServerName; because the specified computer name could not be resolved. ...
  7. VMM is unable to create a snapshot set on %ComputerName;. An unexpected error occurred during the Volume Shadow Copy service ...
  8. VMM is unable to create a snapshot set on %ComputerName;. The writer %VssWriterName; is in the failed state %VssWriterStatus;. ...
  9. VMM is unable to delete the load balancer (%LoadBalancerName;) because the service (%ServiceName;) depends on the virtual ...
  10. VMM is unable to delete the logical network (%Name;) because other objects, such as network sites, virtual network adapters, ...
  11. VMM is unable to delete the logical network because dependent resources, such as logical network definitions, are still associated. ...
  12. VMM is unable to delete the logical network definition (%Name;) because other objects, such as VM Subnets or NativeUplinkPortProfiles ...
  13. VMM is unable to delete the logical network definition because dependent resources, such as VM Subnets or NativeUplinkPortProfiles ...
  14. VMM is unable to delete the logical switch because dependent resources are still associated. Contact your VMM administrator ...
  15. VMM is unable to delete the native uplink port profile because dependent resources are still associated. Contact your VMM ...
  16. VMM is unable to delete the UplinkPortProfileSet because dependent resources are still associated. Contact your VMM administrator ...
  17. VMM is unable to delete the virtual switch extension (%Name;) because dependent resources, such as LogicalSwitches use it. ...
  18. VMM is unable to delete the virtual switch extension manager (%Name;) because dependent resources, such as LogicalSwitches ...
  19. VMM is unable to delete the virtual switch extension uplink port profile (%Name;) because dependent resources, such as LogicalSwitches ...
  20. VMM is unable to delete the virtual switch extension virtual port profile (%Name;) because dependent resources, such as LogicalSwitches ...
  21. VMM is unable to delete the VirtualNetworkAdapterNativePortProfile because dependent resources are still associated. Contact ...
  22. VMM is unable to delete the VirtualNetworkAdapterPortProfileSet because dependent resources are still associated. Contact ...
  23. VMM is unable to delete the VM Network because other components, such as Library Servers are still associated to it. Contact ...
  24. VMM is unable to delete the VMNetwork %Name; because other objects, such as VMSubnets, Load balancer templates and Virtual ...
  25. VMM is unable to delete the VMNetwork because dependent resources, such as VMSubnets, Load balancer templates and Virtual ...
  26. VMM is unable to delete the VMSubnet because dependent resources, such as virtual network adapters or VM Network gateways ...
  27. VMM is unable to deploy the VM '%VMName;' from the VMM Library to the XenServer host. The VM data contained in '%FileName;' ...
  28. VMM is unable to emulate the exact configuration of the source machine %ServerName;. The virtual machine memory could not ...
  29. VMM is unable to enable network virtualization on the specified adapter because network virtualization is not supported by ...
  30. VMM is unable to establish a connection to the XenServer computer you specified in order to determine whether it is a cluster ...
  31. VMM is unable to find the capacity settings for the specified private cloud. The private cloud may have been moved or deleted. ...
  32. VMM is unable to find the specified GatewayConnection. The GatewayConnection name may be incorrect, or the GatewayConnection ...
  33. VMM is unable to find the specified load balancer virtual IP (VIP) address. The load balancer VIP address may have been deleted. ...
  34. VMM is unable to find the specified logical switch. The logical switch name may be incorrect, or it may have been deleted. ...
  35. VMM is unable to find the specified native switch port profile. The native switch port profile name may be incorrect, or ...
  36. VMM is unable to find the specified Native Uplink port profile. The Native Uplink port profile name may be incorrect, or ...
  37. VMM is unable to find the specified network site. The network site name may be incorrect, or the network site may have been ...
  38. VMM is unable to find the specified NetworkGateway. The NetworkGateway name may be incorrect, or the NetworkGateway may have ...
  39. VMM is unable to find the specified NetworkRoute. The NetworkRoute name may be incorrect, or the NetworkRoute may have been ...
  40. VMM is unable to find the specified port classifcation. The port classification name may be incorrect, or it may have been ...
  41. VMM is unable to find the specified UplinkPortProfile. The UplinkPortProfile name may be incorrect, or it may have been deleted. ...
  42. VMM is unable to find the specified VirtualNicPortProfile. The VirtualNicPortProfile name may be incorrect, or it may have ...
  43. VMM is unable to find the specified VM Network Gateway. The VM Network Gateway name may be incorrect, or the VM Network Gateway ...
  44. VMM is unable to find the specified VMNetwork. The VMNetwork name may be incorrect, or the VMNetwork may have been deleted. ...
  45. VMM is unable to find the specified VPNConnection. The VPNConnection name may be incorrect, or the VPNConnection may have ...
  46. VMM is unable to import from %FolderPath; because the exported configuration file was not found. The exported configuration ...
  47. VMM is unable to import the virtual machine %VMName;. This could be because the virtual machine has a Virtual Fibre Channel ...
  48. VMM is unable to perform a snapshot set -related operation on %ComputerName;. This is a general failure in Volume Shadow ...
  49. VMM is unable to perform operation because the subnet (%Subnet;) overlaps with another subnet (%OtherSubnet;) that is defined ...
  50. VMM is unable to read all the necessary data for the SQL Server hosting your existing VMM databases. Please verify the SQL ...
  51. VMM is unable to update the isolation mode of the logical network (%Name;) because logical network definitions or VM networks ...
  52. VMM is unable to update the logical network (%Name;) because other objects, such as network sites, virtual network adapters, ...
  53. VMM is unable to update the logical network because dependent resources, such as logical network definitions, are still associated. ...
  54. VMM is using WinRM for the request. WinRM cannot complete the operation. The client cannot connect to %ComputerName; specified ...
  55. VMM management server is already installed on this machine and includes the components you have requested. There is no need ...
  56. VMM target group %TargetGroupName; cannot be found on update server %ComputerName;. Remove the update server from VMM management ...
  57. VMM uses virtual machine placement paths as default locations to store virtual machines placed on a host. To add a new virtual ...
  58. VMM will attempt to restart the selected jobs from the last known status. This may require restarting from the beginning ...
  59. VMM will create a virtual hard disk (.vhd file) for each volume. Specify the size, the disk type, and the channel to which ...
  60. VMM Workgroup Edition can manage a maximum of five hosts. Uninstall the Virtual Machine Manager management server using the ...
  61. VMMM cannot add a script command to the application profile or application deployment that is associated with an application ...
  62. VMMM is unable to find the specified load balancer virtual IP (VIP) address template. The load balancer VIP address template ...
  63. Volume %VolumeDriveLetter; cannot be attached to IDE controller because the volume exceeds the maximum IDE disk size (%MaxLimit; ...
  64. Volume %VolumeDriveLetter; cannot be attached to SCSI controller because the volume exceeds the maximum SCSI disk size (%MaxLimit; ...
  65. We cannot autogenerate names for the selected Hyper-V hosts based on the host profile you have selected. You will need to ...
  66. When a virtual hard disk file is removed from a virtual machine, it can also be removed from the virtual machine host. Do ...
  67. When a virtual hard disk file is removed from a virtual machine, it can also be removed from the virtual machine host. Do ...
  68. When CPU usage on a host is high, virtual machines with higher priority are allocated CPU resources before virtual machines ...
  69. When doing a deployment, VMM advises that you have enough free space on the partition to contain the recommended page file ...
  70. When memory usage on a host is high, virtual machines with higher priority are allocated memory resources before virtual ...
  71. When no isolation is selected, the VM network provides virtual machines with direct access to logical network. Only one VM ...
  72. When the -UseLocalVirtualHardDisk parameter is specified, VMM requires that a local file be specified for each virtual disk ...
  73. When the local virtual disk option is specified, VMM requires that a local file be specified for each virtual disk drive ...
  74. When the value for the -PhysicalAddressType Static parameter is specified, a Media Access Control (MAC) address for the -PhysicalAddress ...
  75. When this option is selected the new VM network will be isolated from other network traffic through the use of a virtual ...