System Center 2012 – Virtual Machine Manager (VMM) Error Codes [12000-12999]

Use Ctrl-F to find a specific code.

Some codes have a recommended action using PowerShell as well as the general action.

Links to other error code pages can be found at System Center 2012 – Virtual Machine Manager (VMM) Error Codes.

 

If you have additional information about an error, please add it to the "Additional Troubleshooting Information" column.

 

Code	Message	Recommended Action (in product)	Additional Troubleshooting Information
12400	Unable to open Windows PowerShell because the path to PowerShell.exe could not be found.	Add the path to PowerShell.exe to the Path environment variable on the Advanced tab in Windows System Properties.
12401	Unable to display Windows PowerShell script because Notepad could not be found.	Add the path to Notepad.exe to the Path environment variable on the Advanced tab in Windows System Properties.
12402	Migrating %VMName; will cause saving state of the virtual machine, resulting in a temporary loss of service to all users of the machine.\n\nDo you want to continue?
12403	If you proceed, the following host clusters will no longer be managed by this Vir tual Machine Manager management server: %ObjectList;.\n\nDo you want to continue?
12404	Unable to import templates because no library path was selected.	Select a library path and then try the operation again.
12405	Virtualization manager %ServerName; will no longer be managed by this Virtual Machine Manager management server. All hosts and virtual machine data related to this virtualization manager will be removed from VMM. VMM will take no action on the virtualization manager itself.\n\nDo you want to continue?
12406	(Internal error.)
12407	You cannot open the VMM console because your user role in Virtual Machine Manager does not have access to any host groups. \n\nThis happens when an administrator is given a Delegated Administrator pro file but is not assigned any host groups to administer.	Ask your VMM administrator to assign the host groups that you will a dminister to your user role.
12408	You cannot add hosts to Virtual Machine Manager because your user role does not have access to any host groups.\n\nThis happens when an administrator is given a Delegated Administrator profile but is not assigned any host groups to administer.	Ask your VMM administrator to assign the host groups that you will a dminister to your user role.
12409	%ComputerName; cannot be reached.	Verify network connectivity between the Virtual Machine Manager mana gement server and %ComputerName;. If the issue persists, contact your network administrator.
12410	Moving the selected host, host group, or host cluster to host group %HostGroupNam e; will result in a restructuring of folders and datacenters for the following VMware VirtualCenter servers: %ObjectLis t;.\n\nDo you want to continue?
12411	This action will place virtual machine %VMName; on a highly available host. This will cause the virtual machine to become highly available for all future migrations.\n\nDo you want to continue?
12412	This action does not allow an empty password.	Enter the password.
12413	Unable to migrate virtual machine %VMName; because the host %VMHostName; is not a suitable host for the virtual machine. To select from the hosts that are best suited for the virtual machine, use the Migrate Virtual Machine Wizard.\n\nDo you want to start the Migrate Virtual Machine Wizard now?
12414	Unable to migrate virtual machine %VMName; because the selected host group, %Host GroupName;, does not contain any suitable hosts. To select from the hosts that are best suited for the virtual machine, use the Migrate Virtual Machine Wizard.\n\nDo you want to start the Migrate Virtual Machine Wizard now?
12415	Unable to migrate virtual machine %VMName; because the host cluster %HostClusterName; contains no suitable hosts. To select from the hosts that are best suited for the virtual machine, use the Migrate Virtual Machine Wizard.\n\nDo you want to start the Migrate Virtual Machine Wizard now?
12416	VMM is unable to process one of the provided parameters for the cmdlet (%CmdletNa me;):\n\n%ParameterBindingMsg;	Try the operation again. If the issue persists, contact Microsoft Help and Support.
12417	Connecting to this VMware virtual machine requires an ActiveX control that is not installed.\n\nWould you like to install the VMware ActiveX control now?
12418	Invalid port number for %InputParameterTag;.	Enter an integer from 1 through 65535 for the port.
12419	Unable to display Diagram view because the Operations Console for System Center Operations Manager 2007 cannot be opened.	Install an Operations Console for Operations Manager 2007 on the Virtual Machine Manager management server.
12420	Creating a template will destroy the source virtual machine %VMName;. The virtual hard disks of the virtual machine will be generalized to create the new template and any user data on the virtual mach ine may be lost. To prevent this, you can create a clone of %VMName; before using it to create a template.\n\nDo you want to continue?
12421	The certificate file on the VMware vCenter Server is not valid.	Ensure that the file is a valid certificate file, and then try the operation again.
12422	Cannot add VMware ESX host %VMHostName; to Virtual Machine Manager because the ho st already is associated with a VMware VirtualCenter server (%VCSName;) that is managed by VMM.	To associate the VMware ESX host with a different VMware VirtualCenter server, first remove the host from VMM, and then add the host to VMM again, this time specifying the new VirtualCenter server.
12423	The specified network address is not valid.	Specify a valid IPv6 network address.
12424	Cannot add VMware ESX host %VMHostName; to host group %HostGroupName; because the host group is not in a VMware VirtualCenter datacenter.	To add a VMware ESX host, you must add it within a VMware VirtualCenter datacenter. Select a host group that represents its VMware VirtualCenter datacenter or a child of that host group.
12425	A connection to this virtual machine through the Hyper-V host is not available because CredSSP is not enabled on this computer.	To enable CredSSP for Windows XP SP3, see the following KB article: http://go.microsoft.com/fwlink/?LinkId=123471.
12426	When you import the selected templates, the original templates are destroyed on the VMware ESX Server host.\n\nDo you want to continue?
12427	A connection to this virtual machine through the Hyper-V host is not available because CredSSP is not supported on this computer.	Connect to the virtual machine using Terminal Services instead.
12700	VMM cannot complete the host operation on the %ServerName; server because of the error: %VMAsyncTaskErrorMessage;	Resolve the host issue and then try the operation again.
12701	VMM cannot complete the VMware operation on the %ServerName; server because of the error: %VMAsyncTaskErrorMessage;	Resolve the issue in VMware and then try the operation again.
12702	Cannot bind to TCP port %TCPPort; because it is in use by another process on the %ServerName; server.	Wait until the other process is completed, and then try the operation again.
12703	VMM cannot establish a trust relationship for the SSL/TLS secure channel for %ServerName; server.	Install the certificate to the trusted people root store of the VMM management server and then try the operation again.
12704	Unable to connect to the Hyper-V service on the server %ServerName;.	Ensure that the Hyper-V services (vmms, nvspwmi, or vhdsv) and the Virtual Machine Manager Agent are installed and running on the server %ServerName;.
12705	The volume does not contain a recognized file system.	Ensure that all required file system drivers are loaded and that the volume is not corrupted.
12706	The virtualization software on the host %ServerName; does not support the convers ion operation on a virtual hard disk.	Select a host with different virtualization software and then try th e operation again.
12707	The virtualization software on host %ServerName; does not support the compacting of a fixed virtual hard disk.	To compact the hard disk, migrate the virtual machine to a host that is running different virtualization software.
12708	The specified pass-through disk does not exist on the virtualization host (%Serve rName;).	Select an offline pass-through disk and then try the operation again . If you have recently changed your disk configuration, wait approximately 30 minutes, or you can manually refresh the properties selecting the virtualization host (%ServerName;) in the Hosts pane, and then run the refresh action. Command Line Interface: Select an offline pass-through disk and then try the operation again . If you have recently changed your disk configuration, wait approximately 30 minutes or you can manually refresh the p roperties by using the Refresh-VMHost cmdlet, and then try the operation again.
12709	The operation on the computer (%ComputerName;) did not complete successfully because of the error: %DetailedErrorMessage;.	Ensure that the parameters are valid, and then try the operation aga in.
12710	VMM does not have appropriate permissions to access the Windows Remote Management resources on the server ( %ServerName;).	1) Ensure that the Windows Remote Management (WS-Management) service is running on the server (%ServerName;). 2) If the System Center Virtual Machine Manager service on your VMM management server is configured to run by using the machine account, ensure that there is not a group policy that does not allow adding machine accounts to a computer's Administrators group. If there is, you can use one of the following workaroun ds: - Disable the group policy in Active Directory Domain Services (AD DS) - Modify the group policy to allow the VMM machine account in the Administrators group - Move the machine account to its own organizational unit (OU) and block the group policy from being applied - Reinstall the VMM management server and choose the option to run the System Center Virtual Machine Manager service by using a domain account, and re-add all of your virtual machines. Command Line Interface: 1) Ensure that the Windows Remote Management (WS-Management) service is running on the server (%ServerName;). 2) If the System Center Virtual Machine Manager service on your VMM management server is configured to run by using the machine account, ensure that there is not a group policy that does not allow adding machine accounts to a computer's Administrators group. If there is, you can use one of the following workarounds: - Disable the group policy in Active Directory Domain Services (AD DS) - Modify the group policy to allow the VMM machine account in the Administrators group - Move the machine account to its own organizational unit (OU) and block the group policy from being applied - Reinstall the VMM management server and choose the option to run the Sys tem Center Virtual Machine Manager service by using a domain account, and re-add all of your virtual machines.
12711	VMM cannot complete the WMI operation on the server (%ServerName;) because of an error: %WMIExtendedErrorMessage;	Resolve the issue and then try the operation again.
12712	VMM cannot complete the virtualization operation on server %ServerName; because of error: %WSManSoapFaultSubcode;: %WSManSoapFaultReason;	Resolve the issue in VMware and then try the operation again.