System Center Virtual Machine Manager 2012

  1. Cannot store virtual machine %VMName; in cloud %CloudName; because user given path %PathName; is not a subfolder of cloud's ...
  2. Cannot support a Virtual Machine from the selected template because the VMware vCenter Server that manages the selected template ...
  3. Cannot use the extension port profile (%Name;) since this has been marked for deletion by the external Virtual Switch Extension ...
  4. Capability Profile "%Name;" release "%Release;" cannot be found. Capability Profile reference will be removed from object ...
  5. Capability Profile "%Name;" release "%Release;" cannot be found. Capability Profile reference will be removed from object ...
  6. Capacity/Free space cannot be calculated for %SharePath;. Failed to retrieve information with Win32 error code %StorageErrorCode;. ...
  7. Change bus type and try operation again. If this issue continues, please contact your system administrator with this error ...
  8. Change minimum bandwidth settings on either the logical switch or virtual network adapter native port profile and retry the ...
  9. Change the classification or virtual hard disk equivalence group for this virtual disk drive to a supported configuration ...
  10. Change the client configuration on VMM server by running: winrm set winrm/config/client/auth @{CredSSP="true"} from elevated ...
  11. Change the guest OS to one that is compatible with the Application Profile or add the guest OS to the Application Profile's ...
  12. Change the local security policy on the virtual machine to allow an empty string as a password and then try the operation ...
  13. Change the processor count and try operation again. If this issue continues, please contact your system administrator with ...
  14. Change the target host group or load balancer for the virtual machine configuration to ensure that the load balancer can ...
  15. Changes are applied to the virtual machines within the service based on the update method that you selected for each tier. ...
  16. Changes to Deployment Order, DefaultInstanceCount, InstanceMaximumCount and InstanceMinimumCount settings in the service ...
  17. Changes to the deployment order in the application host template (%Name;) during servicing are not supported and will be ...
  18. Changes to the virtual disk drives in the service tier template (%Name;) during servicing are not supported and will be ignored. ...
  19. Changes to virtual network adapters in the service tier template (%Name;) are not supported during servicing and will be ...
  20. Changing properties of storage provider %ComputerName; failed since changing the parameters -NetworkDeviceName and -TCPPort ...
  21. Changing the Chart's Axes property is not supported; changes to the collection should be made with its .Add/.Remove methods ...
  22. Changing the Chart's Series property is not supported; changes to the collection should be made with its .Add/.Remove methods ...
  23. Changing the logical switch will result in clearing the switch members and deleting any child virtual network adapters. Do ...
  24. Changing the TreeMap's Interpolators Property is not supported; changes to the collection should be made with its .Add/.Remove ...
  25. Check connectivity from the Virtual Machine Manager management server to the host. If there is no connectivity, try connecting ...
  26. Check Device Manager/System Devices to make sure that Microsoft Virtual Server Storage Bus is installed and functional. If ...
  27. Check Device Manager/System Devices to make sure that Microsoft Virtual Server Storage Bus is installed and functional. If ...
  28. Check Device Manager/System Devices to make sure that Microsoft Virtual Server Storage Bus is installed and functional. If ...
  29. Check if the BITS service is running on virtual machine and restart the BITS service before retrying the operation again. ...
  30. Check that the RunAs account does not have any consumers (if the consumer is not in your scope, you might not see that), ...
  31. Check that the RunAs profile does not have any consumers (if the consumer is not in your scope, you might not see that), ...
  32. Check that WinRM is installed and running on server %ServerName;. For more information use the command "winrm helpmsg hresult". ...
  33. Check that WS-Management service is installed and running on server %ServerName;. For more information use the command "winrm ...
  34. Check the event log of server %VMHostName; for more information. Verify that all open file handles on any of the disks of ...
  35. Check the network connectivity to the Domain Controller, and ensure that the VMM service account has the proper permissions ...
  36. Check the network connectivity to the Domain Controller, and then run Setup again. If the problem persists, contact your ...
  37. Check the network connectivity to the Domain Controller, and then try the operation again. If the problem persists, contact ...
  38. Check the physical machine console and the Windows customization log on the physical machine for any errors. If there are ...
  39. Check the recent records from the VolSnap source in the Application Event Log to determine the issue, and then try the operation ...
  40. Check the virtual switch name and then try the operation again. For a host that is running Virtual Server, a virtual switch ...
  41. Check the virtual switch name and then try the operation again. For a host that is running Virtual Server, a virtual switch ...
  42. Check the Windows Event Log on the %ServerName; server to determine the cause of the error and make corrections. Then try ...
  43. Check your Fibre Channel zoning policy to ensure that the server %VMHostName; can recognize the LUN virtual machine %VMName; ...
  44. Check your iSCSI configuration and verify that iSCSI subsystem %FriendlyName; is visible to virtual machine host %VMHostName;, ...
  45. Check your iSCSI configuration to Ensure that the server %VMHostName; can connect to the iSCSI target Virtual machine %VMName; ...
  46. Checkpoint actions can be performed only for virtual machines that are on a host. Virtual machine %VMName; is in the library. ...
  47. Checkpoint actions on virtual machine %VMName; are unsupported because one or more hard disks are shared with other virtual ...
  48. Checkpoint creation on virtual machine %VMName; is unsupported because the virtual machine contains virtual hard disk %FileName;, ...
  49. Choose this option if you plan to reinstall VMM and want to resume managing virtual machines in the same host environment. ...
  50. Choose this option to specify the Windows, SMI-S or SMP based storage provider that can be used to manage the storage devices. ...
  51. Clear the Limit Processor for Migration setting from the virtual machine hardware configuration, and then try the operation ...
  52. Click Change to begin the installation. Click Back to review or change any of your installation settings. Click Cancel to ...
  53. Click Install to begin the installation. Click Back to review or change any of your installation settings. Click Cancel to ...
  54. Click Remove to remove ProductName from your computer. Click Back to review or change any of your installation settings. ...
  55. Click Repair to repair the installation of ProductName]. Click Back to review or change any of your installation settings. ...
  56. Click Start, click in the Search programs and files box, type services.msc, and then press Enter. Right-click the service ...
  57. Click Update to update ProductName from your computer. Click Back to review or change any of your installation settings. ...
  58. Close and then reopen the VMM console, and then try the operation again. If the problem persists, contact your network administrator. ...
  59. Cluster validation reported some warnings. Refer %FileName; in %windir%\Cluster\Reports of any node for further information ...
  60. Cluster validation reported that the nodes do not meet clustering requirements. Refer %FileName; in %windir%\Cluster\Reports ...
  61. Clustered host %VMHostName; is not available for placement. For the host to be available for placement, the Cluster Service ...
  62. Communication between this host and VMM server is trusted. This is set by a property of the VMware VirtualCenter server that ...
  63. Compliance state for software update %Name; as part of the baseline %BaselineName; for %TargetName; is currently unknown. ...
  64. Component Services (COM+ 1.0) are not installed on this computer. This installation requires Component Services in order ...
  65. ComputerName; is a VMM management server. A VMM management server cannot be associated with another VMM management server. ...
  66. ComputerName; is already associated with a different VMM management server. A computer can only be associated with one VMM ...
  67. Configuration issues related to the load balancer with template name %LoadBalancerName; prevent deployment of virtual machine ...
  68. Configuration issues related to the virtual hard drive configuration with ID %Id; of virtual machine %VMName; prevent deployment. ...
  69. Configuration issues related to the virtual machine %VMName; prevent deployment and must be resolved before deployment can ...
  70. Configure application deployments in the virtual machine. Deployment and servicing may be customized with scripts. You can ...
  71. Configure hardware for the virtual machine. You can import settings from a hardware profile or save a new profile based on ...
  72. Configure identity, network settings, and scripts for the new virtual machine. You can import settings from a guest OS profile ...
  73. Configure SQL Server installations in the virtual machine. You can import settings from a SQL Server profile or save a new ...
  74. Configure the host virtual network adapter to use a VM Network whose isolation type is not Windows Network Virtualization. ...
  75. Configure the security settings of host %VMHostName; to enable full management functionality and then try the operation again. ...