System Center Virtual Machine Manager 2012

  1. Ensure that %ServerName; is online and that you can access the server remotely from your computer. Then connect to %ServerName; ...
  2. Ensure that all cluster nodes has access to storage array by zoning property for fibre channel or logging into array targets ...
  3. Ensure that all library servers you are adding to the scope are in the Responding state and then try the operation again. ...
  4. Ensure that all network adapters used by virtual machine %VMName; are legacy type and specify a logical network connection ...
  5. Ensure that all of the files and pass-through disks belonging to the virtual machine reside on highly available storage. ...
  6. Ensure that all of the virtual network adapters are either disconnected or connected to highly available virtual switches. ...
  7. Ensure that all of the virtual network adapters are either disconnected or connected to highly available virtual switches. ...
  8. Ensure that all settings that refer to the service setting are of the same type (Run As account, VM Network, or string). ...
  9. Ensure that all the nodes are online and do not have Not Responding status in Virtual Machine Manager. Then refresh the host ...
  10. Ensure that all virtual machine configurations in the tier target a common host group with appropriate load balancer connectivity ...
  11. Ensure that all virtual network adapter configurations and load balancer configurations have IP address settings correctly ...
  12. Ensure that all virtual network adapter configurations have MAC address settings correctly specified, and then try again. ...
  13. Ensure that Analysis Management Objects (AMO) is installed on the VMM management server. If you are using SQL Server 2008 ...
  14. Ensure that exactly one of the virtual disk of the template is marked as 'Contains an operating system', and then try again. ...
  15. Ensure that host %VMHostName; has access to storage array %ArrayName; by zoning property for fibre channel or logging into ...
  16. Ensure that importing multiple resources was the intent. If this occurred during Service template import, check the Imported ...
  17. Ensure that no application on computer %ServerName; listens for HTTP traffic on TCP port %TCPPort; during the P2V conversion. ...
  18. Ensure that none of the virtual machine instances in the service tier are in failed states and that the number of virtual ...
  19. Ensure that none of the virtual machines in the service tier are in failed states and that none of them are marked as templates. ...
  20. Ensure that none of the virtual machines in the service tier are marked as templates and that the number of virtual machines ...
  21. Ensure that none of the virtual machines in the service tier are marked as templates, that the number of virtual machines ...
  22. Ensure that PowerShell remoting is enabled on Virtual Machine Manager management server and that the action account that ...
  23. Ensure that SQL instance %SqlInstance; is installed properly and running. Also ensure that %DatabaseName; is accessible. ...
  24. Ensure that sufficient host resources are available on the host group or cloud that this virtual machine configuration targets ...
  25. Ensure that System Center Virtual Machine Manager 2012 SP1 Management Pack and its reports are installed on the Operations ...
  26. Ensure that the account you are trying to connect as is a valid domain account or a computer account. For more information, ...
  27. Ensure that the any effects of incomplete orchestration steps such as a stopped virtual machine, an incomplete virtual machine ...
  28. Ensure that the character @ (single @) is properly escaped by using @ (double @) in corresponding properties of virtual machine ...
  29. Ensure that the cluster is running Windows Server 2008. If the operating system was updated recently, Active Directory Domain ...
  30. Ensure that the computer %ComputerName; exists, that the specified credentials have administrative rights, and then try the ...
  31. Ensure that the computer %ServerName; exists on the network, WMI service and the agent are installed and running and that ...
  32. Ensure that the computer name is correct, and then try the operation again. If the problem persists, contact your network ...
  33. Ensure that the correct address protocol version is specified for the IP address of in the virtual network adapter configuration. ...
  34. Ensure that the correct boot loader is installed and remove all files named "$scvmm*.*" from the root directory of the boot ...
  35. Ensure that the correctness of the driver package that the Setup information file (%FileName;) is a part of, and then try ...
  36. Ensure that the credentials are valid. In addition, the SCVMMService must run as the local system account or a domain account ...
  37. Ensure that the credentials provided are from an account with sufficient rights to remove the VMM database, and then try ...
  38. Ensure that the disk location for operating system disk in the template and in the virtual machine are the same, or that ...
  39. Ensure that the domain name, user name, and password are correct, and then try the operation again. Ensure that a domain ...
  40. Ensure that the effects of skipping the SQL Server script command are mitigated by taking any required corrective action ...
  41. Ensure that the file has the ".vhd" virtual hard disk image extension and that the file is actually a virtual hard disk image. ...
  42. Ensure that the file is present and accessible. Unmount the VHD file by using vhdmount.exe if the file is mounted. Try the ...
  43. Ensure that the folder %DirectoryPath; is a valid location and that the current user has permission to access the location. ...
  44. Ensure that the group name is valid, and cluster resource or group with the same name does not exist, and the group name ...
  45. Ensure that the host is running Windows Server 2003 SP2 or later. If the operating system was updated recently, Active Directory ...
  46. Ensure that the HTTP service and/or the agent on the machine %BITSServerName; are installed and running and that a firewall ...
  47. Ensure that the Hyper-V services (vmms, nvspwmi, or vhdsv) and the Virtual Machine Manager Agent are installed and running ...
  48. Ensure that the IIS Admin Service is running and then try running VMM Self-Service Portal Setup again. If you are installing ...
  49. Ensure that the input .vmdk file is the .vmdk file that the .vmx file points to. The .vmx file points to a .vmdk file that ...
  50. Ensure that the InstanceMinimumCount is less than or equal to the DefaultInstanceCount, and that the DefaultInstanceCount ...
  51. Ensure that the load balancer template is connected to network adapters in the service tier template with a static IP address. ...
  52. Ensure that the load balancer template is connected to network adapters in the service tier template with a static MAC address. ...
  53. Ensure that the load balancer template is connected to network adapters in the service tier template with MAC spoofing enabled. ...
  54. Ensure that the LUN, which contains virtual machine %VMName;, is unmasked to virtual machine host %VMHostName;. Then try ...
  55. Ensure that the Microsoft Cryptographic Service has been installed on the VMM management server and try the operation again. ...
  56. Ensure that the Microsoft Virtualization Reports management pack is installed and the reports are present under Microsoft.Virtualization.Reports ...
  57. Ensure that the non-customizable template does not contain application profiles, SQL Server profiles, or operating system ...
  58. Ensure that the P2V agent is installed on %ComputerName; and that the P2V agent service is running, and then try the operation ...
  59. Ensure that the patch file applies to 32-bit platform of an operating system that is supported for virtualization, and then ...
  60. Ensure that the patch file exists and is accessible by the machine account on the Virtual Machine Manager management server. ...
  61. Ensure that the path %FolderPath; exists and that the folder is empty. Ensure that another volume is not mounted at this ...
  62. Ensure that the path exists and that the path is for a cluster disk in available storage, and then try the operation again. ...
  63. Ensure that the path exists and that the path is not a cluster disk or cluster shared volume, and then try the operation ...
  64. Ensure that the path exists and Virtual Machine Manager management server %ServerName; has read permissions to all the files ...
  65. Ensure that the path or part of the path that you provided is not used as a writable library share path on a private cloud, ...
  66. Ensure that the pending service template is same or cloned from the service template for the service, and then try again. ...
  67. Ensure that the private cloud in which the virtual machine is placed has an associated ReadWriteLibrarySharePath, and then ...
  68. Ensure that the provided name is a cluster name or the computer name of a node in the cluster exactly as added in VMware ...
  69. Ensure that the provided name is a cluster name or the computer name of a node in the cluster, and that the cluster is listed ...
  70. Ensure that the ReportingServiceRunAsProfile, SQLServiceRunAsProfile, SARunAsProfile, AgentServiceRunAsProfile parameters ...
  71. Ensure that the resource group only contains a single virtual machine resource, a single virtual machine configuration resource, ...
  72. Ensure that the Run As profile for SA account is specified for SQL Server Authentication mode, and try the operation again. ...
  73. Ensure that the RunAs account credentials or the VMM service account used to connect to Operations Manager server have necessary ...
  74. Ensure that the same address family is used for both PA and CA address type, or that the virtualization mode of the VM network ...
  75. Ensure that the security file is valid and the key used for encrypting the security file is correct, and then try the operation ...