System Center Virtual Machine Manager 2012 R2

  1. The Virtual Switch column contains the virtual switches that are configured for each physical network adapter on the host. ...
  2. The virtual switch configuration does not match the expected uplink mode setting of %UplinkMode; from the logical switch. ...
  3. The virtualization host (%VMHostName;) is in maintenance mode. Hosts in maintenance mode are not available for placement. ...
  4. The virtualization platform parameter (%VirtualizationPlatform;) is either missing or unsupported for the current operation. ...
  5. The virtualization software for the virtual hard disk %FileName; is not compatible with the virtualization software on the ...
  6. The virtualization software for the virtual hard disk %FileName; is not compatible with the virtualization software on the ...
  7. The virtualization software on host %VMHostName; does not support a processor count of %Count;. Supported processor counts: ...
  8. The virtualization software on host %VMHostName; does not support a processor count of %Count;. Supported processor range: ...
  9. The virtualization software on host %VMHostName; does not support the expanding of a virtual hard disk or the disk you want ...
  10. The virtualization software on host does not support a processor count of %Count;. Supported processor counts: %ValidProcessorCount;. ...
  11. The virtualization software on host does not support a processor count of %Count;. Supported processor range: 1 - %ValidProcessorCount;. ...
  12. The virtualization software on the host (%VMHostName;) does not support the Limit Processor for Migration setting. After ...
  13. The virtualization software on the selected host does not support adding or removing a virtual disk drive on IDE adapter ...
  14. The virtualization software on the selected host does not support conversion of a pass-through disk to a virtual hard disk. ...
  15. The VLAN ID (%VlanId;) is not valid because the VM network (%LogicalNetworkName;) does not include the VLAN ID in a network ...
  16. The VLAN ID (%VlanId;) is not valid because the VM network (%VMNetworkName;) does not include the VLAN ID in a network site ...
  17. The VLAN setting for one or more network adapters on the virtual machine (%VMName;) is not compatible with the virtualization ...
  18. The VLAN setting for one or more network adapters on the virtual machine (%VMName;) is not compatible with the virtualization ...
  19. The VM %VMName; could not be placed on host %VMHostName; in cloud %CloudName; due to the following issues: %VMErrorMessage; ...
  20. The VM host %VMHostName; is not within the scope of cloud %CloudName;. The Virtual Machine %VMName; might not be accessible ...
  21. The VMConfiguration parameter was passed for creation of the virtual machine (%VMName;) along with some inappropriate cmdlets ...
  22. The VMM database contains hosts that are running VMware ESX Server with versions that are not supported in VMM in System ...
  23. The VMM database contains one or more services in a failed state. Upgrading to VMM in System Center 2012 R2 is not recommended. ...
  24. The VMM database contains VMware vCenter Servers with versions that are not supported in VMM in System Center 2012 R2.If ...
  25. The VMM management server cannot be removed because the specified user account does not have sufficient permissions to remove ...
  26. The VMM management server cannot check Windows Remote Management (WinRM) configuration settings on the computer %ComputerName;. ...
  27. The VMM management server cannot contact the Virtual Machine Manager agent on the computer %ComputerName; after the computer ...
  28. The VMM management server cannot locate Windows Remote Management (WinRM) listeners on the computer %ComputerName;. The diagnostic ...
  29. The VMM management server cannot retrieve performance data for the computer %ComputerName;. This issue may occur if the performance ...
  30. The VMM management server cannot retrieve performance data on the computer %ComputerName;. This issue may occur if the performance ...
  31. The VMM management server name %ServerName; in the database is different from the user-specified VMM management server name ...
  32. The VMM management server name %ServerName; is not valid. VMM cannot be installed because a resource or group exists in the ...
  33. The VMM server can't be registered more than once in a Microsoft Azure Site Recovery vault but there are multiple registration ...
  34. The VMM server is either down or the powershell module on VMM server is not function. Please check if the VMM is up and its ...
  35. The VMM site certificate used for Microsoft Azure Site Recovery couldn't be found on the VMM server, and couldn't be imported ...
  36. The VMware ESX host (%VMHostName;) is in maintenance mode. It is not available for deployments or migrations of virtual machines. ...
  37. The volume %DiskName; on host %VMHostName; is already formatted as NTFS. In order to prevent data loss, the volume has not ...
  38. The volume %DriveName; is not completely uninstalled on server %VMHostName;. Restart server %VMHostName; to complete the ...
  39. The volume %VolumeDriveLetter; of source computer %ServerName; cannot be extended to the size of the resulting VHD because ...
  40. The volume %VolumeDriveLetter; of source computer %ServerName; cannot be extended to the size of the resulting VHD due to ...
  41. The volume %VolumeDriveLetter; selected for physical-to-virtual imaging is not accessible from Windows PE. This is usually ...
  42. The volume (%VolumeDriveLetter;) selected for physical-to-virtual conversion is not accessible from Windows PE. This is usually ...
  43. The Windows Installer service cannot update one or more protected Windows files. {SFP Error: 2]. List of protected files: ...
  44. The Windows Installer service cannot update the protected Windows file 2]. {Package version: 3], OS Protected version: 4], ...
  45. The Windows Installer service cannot update the system file 2 because the file is protected by Windows. You may need to update ...
  46. The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows ...
  47. The Windows PowerShell command '%Command;' failed with the exit code %ExitCode; on remote computer %ComputerName; while reading ...
  48. The Windows Remote Management (WinRM) client cannot process the request. The port specified in the connection string is not ...
  49. The Windows Remote Management (WinRM) client configuration on the VMM server is incorrect and a connection with %ServerName; ...
  50. The Windows Remote Management (WinRM) client on the VMM server cannot process the request. A computer policy does not allow ...
  51. The Windows Remote Management (WinRM) client on VMM server cannot process the request to the target computer %ServerName;. ...
  52. The Windows Remote Management (WS-Management) service cannot process the request. The object was not found on the server ...
  53. The WinRM client sent a request to the remote WS-Management service and was notified that the request size exceeded the configured ...
  54. The {0} cannot be deployed because it contains a compatibility profile that is not associated with any private cloud in the ...
  55. There are insufficient video memory resources on the host. The minimum amount of GPU memory required is %PlacementRequestValue; ...
  56. There are insufficient video memory resources on the host. The minimum amount of GPU memory required is %PlacementRequestValue; ...
  57. There are insufficient video memory resources on the host. The minimum amount of memory required is %MemorySize; MB in a ...
  58. There are multiple computer tier templates with the name {0}. Specify a unique name for the computer tier template, and then ...
  59. There are multiple virtual machines %NameList; on the LUN that virtual machine %VMName; is placed on. SAN transfer cannot ...
  60. There are no host profiles that can be used for operating system deployment. Ensure that the host profile you plan to use ...
  61. There are no volumes available for placement. For clustered hosts, all shared storage is currently in use or not available. ...
  62. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact ...
  63. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. ...
  64. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact ...
  65. There is a problem with this Windows Installer package. A script required for this install to complete could not be run. ...
  66. There is already a Secure Sockets Layer (SSL) certificate that is associated with TCP port %TCPPort; on the computer %ServerName;. ...
  67. There is already an SSL certificate associated with port BITSPORT]. Ensure that no application listens for HTTPS traffic ...
  68. There is already another Microsoft System Center Virtual Machine Manager setup running on this computer. Please wait until ...
  69. There is insufficient disk space on the volume %SystemVolumeDriveLetter; on server %VMHostName; to complete the transfer. ...
  70. There is no disk in drive 2]. Please insert one and click Retry, or click Cancel to go back to the previously selected volume. ...
  71. There is no disk in drive 2]. Please insert one and click Retry, or click Cancel to return to the browse dialog and select ...
  72. There is no gateway device selected, or no capacity remains on the selected gateway device. Select a different gateway device ...
  73. There is no subnet or VLAN connectivity for the logical network (%LogicalNetworkName;) on the host network adapter (%Name;). ...
  74. There is no suitable network location for virtual machine %VMName; on host %VMHostName;. Ensure that at least one network ...
  75. There is no suitable network location for virtual machine %VMName; on the host. Ensure that at least one network adapter ...