System Center 2012 – Virtual Machine Manager (VMM) Error Codes [19999-20999]

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
19999	Virtual Machine Manager (%Name;:%Id;) has encountered an error and needed to exit the process. Windows generated an error report with the following parameters: %Value;.	BLANK
20000	Stopped working	BLANK
20200	Creation of the VMM resource group (%GroupName;) failed.	Ensure that the group name is valid, and cluster resource or group with the same name does not exist, and the group name is not used in the network.
20201	The clustered VMM service resources and the group (%GroupName;) could not be deleted.	Ensure that the group name is valid and have permission to delete the resources and groups.
20202	Moving the clustered VMM service (%GroupName;) to the current node failed.	Ensure that the cluster is functioning correctly and that the cluster node is not paused or in a failed state.
20203	Stopping the clustered VMM service (%GroupName;) failed.	Ensure that the VMM service is installed on the current node and is functioning properly and all the resources for the group can be brought offline.
20204	Setting owners of the group (%GroupName;) failed.	Ensure that the cluster is functioning correctly and that you have sufficient rights to update the cluster.
20205	Unable to get the cluster network configuration for the cluster.	Ensure that the user has permission
20206	Starting the clustered VMM service (%GroupName;) failed.	Ensure that the user has permission, the VMM service is installed properly, and cluster resources can be brought online.
20207	Unable to change the preferred owners for the VMM service group (%GroupName;).	Ensure that the cluster is functioning correctly and that you have sufficient rights to update the cluster.
20208	Unable to validate the cluster for existence of clustered VMM service.	Ensure that the user has permission and the cluster is functioning properly.
20209	Failover cluster remote management modules not found.	Ensure that the system has Remote Server Administration Tools for the failover clustering feature installed.
20210	Failover cluster remote management module load failed.	Ensure the system has Remote Server Administration Tools for the failover clustering feature installed properly.
20211	The failover cluster requires at least one static IP address to configure a service.	Please specify the IP address and try the operation again
20212	Failover cluster resources for the service could not be created.	Verify on the cluster if another service resource exists, and that the service components are installed properly.
20213	Unable to detect cluster configuration of the node.	Ensure that the user has permission.
20214	Unable to add the Windows feature RSAT-Clustering.	Run the PowerShell command window and try to add this feature.
20215	Unable to create the Run As account.	Try operation again. If this issue continues, please contact your system administrator with this error ID.
20216	This computer is not a Windows Server 2008 R2 cluster.	Install HAVMM in a Windows Server 2008 R2 cluster.
20217	The VMM management server name is missing.	Enter a valid VMM management server name.
20218	VMM high availability cannot be installed with a cluster in one domain and the VM M management server in another domain (%DomainName;).	The VMM management server domain should be the same as the cluster domain.
20219	The VMM service account is specified as Local System.	Enter a valid domain account for the VMM service account.
20220	SQL Server is installed on the local computer.	Use a remote instance of SQL Server for setting up Virtual Machine Manager.
20221	The Distributed Key Management (DKM) container is not valid.	Enter a valid DKM container.
20222	This cluster already has an instance of the VMM management server.	Use another cluster, or join the existing instance of the VMM management server (%ServiceName;) in the cluster.
20223	VMM cluster resources do not exist but the VMM database reports that VMM cluster nodes are already created.	Uninstall the VMM management servers which are using the database, and then try installing the highly available VMM management server again.
20224	VMM cluster resources exist but the VMM database reports that no cluster nodes for VMM have been created.	Delete the cluster resource group for the VMM management server, and then try installing the highly available VMM management server again.
20225	The VMM management server name (%ServerName;) in the database is different from the user-specified VMM management server name (%Name;).	Use the same name as in the VMM database.
20226	The VMM management server name (%ServerName;) is not valid. VMM cannot be installed because a resource or group exists in the cluster with the specified name.	Enter the valid name of a VMM management server.
20227	VMM cannot be installed because the cluster requires a static IP address for the VMM and no static IP address as specified.	Enter a static IP address.
20228	VMM cannot be installed because the cluster does not require a static IP address for VMM and a static IP address was specified.	Remove the static IP address.
20229	This is not the first time VMM was installed. A VMM database already exists.	Use the existing VMM database.
20230	Installing %PathName; failed with Windows Installer error %MSIErrorCode;.	See %SetupLogFile; for more information. After resolving the problem, retry setup.
20231	The specified path %DirectoryPath; contains invalid characters.	Type a valid path name.
20232	The specified Active Directory group (%ADGroup;) is not valid.	Enter a valid Active Directory group.
20233	A service connection point (SCP) could not be registered in Active Directory Domain Services (AD DS) for the VMM management server.	Run "%Command;" in a command window and then check AD DS. If an SCP is not registered, VMM consoles on other computers will not be able to connect to this VMM management server and deploying a Hyper-V host to a bare-metal computer will not work.
20234	The SQL Server edition cannot be detected.\nConnection string: %SqlInstance;	See the Setup event log (%SetupLogFile;) for more information. After resolving the problem, retry Setup.
20235	The database (%DatabaseName;) is running on an unsupported version of the SQL Server instance.	In order for the upgrade to continue you have to upgrade your database to a supported version of SQL Server. Another option is to back up your database, install a fresh copy of VMM and provide your backed-up database as an existing database during Setup.
20236	The installation location contains an older version of Virtual Machine Manager.
20237	Virtual Machine Manager Setup cannot stop Virtual Machine Manager 2008 R2 SP1 services.	Stop the System Center Virtual Machine Manager service and the VMM Agent service, and then restart Setup.
20238	Virtual Machine Manager Setup cannot create a backup of the existing database.	Verify that you have necessary rights to back up the VMM 2008 R2 SP1 database, and then restart Setup.
20239	The Service Principal Name (SPN) could not be registered in Active Directory Domain Services (AD DS) for the VMM management server.	1) Use setspn.exe to create SPN for vmmserver using following command "%Command;".
20240	The VMM management server cannot be removed because the specified user account does not have sufficient rights to remove the VMM database.	Ensure that the credentials provided are from an account with sufficient rights to remove the VMM database, and then try the operation again.
20241	Setup could not add the Windows Server failover clustering feature.	If Server Manager is running, close Server Manager and restart Setup , or manually add the failover clustering server feature and try the operation again.
20242	The Windows Cluster Service service is not running.	Ensure that the Cluster Service service is installed and running, an d then try again.
20243	VMM Setup cannot operate on the specified database.	Ensure that all active VMM consoles are closed while VMM Setup installs a VMM management server.
20244	The container %ContainerName; in Active Directory specified for distributed key management could not be accessed. Ensure that the container name was entered correctly and that the user installing VMM has the required permissions to the container.	Specify the distinguished name for the container and verify that you have GenericRead|CreateChild|WriteProperty rights on the container.
20245	The container %ContainerName; in Active Directory specified for distributed key management is not valid. Ensure that the container name was entered correctly.	Specify the distinguished name for the container and verify that you have GenericRead|CreateChild|WriteProperty rights on the container.
20246	An existing installation of the VMM Administrator Console has been detected. You cannot upgrade the VMM Administrator Console to System Center 2012 Virtual Machine Manager on the 32-bit (x86) version of Windows 7.	Uninstall the existing VMM Administrator Console and then install th e VMM console for System Center 2012 Virtual Machine Manager.
20247	VMM cannot locate the license agreements in the %FilePath; folder.	Ensure that this folder exists and contains the license agreements in order to continue upgrading. You can copy the license agreements from the product media.
20400	%FailedSubtaskCount; parallel subtasks failed during execution.	BLANK
20401	The Windows Remote Management (WinRM) client configuration on the VMM server is incorrect and a connection with %ServerName; can't be established.	For more information use the command "winrm helpmsg hresult" and con figure the winrm client accordingly on the VMM server.
20402	The SQL server is not able to find the user account	Ensure that the account you are trying to connect as is a valid domain account or a computer account. For more information, see "How to troubleshoot error 15401" in the Microsoft Knowledge Base at http://support.microsoft.com/kb/324321.
20403	It is not supported to upgrade to evaluation license.
20404	VMM cannot find a required object.	Ensure the object is valid, and then try the operation again.
20500	The Virtual Machine Manager Guest Agent was not uninstalled from the computer %ComputerName;.	Uninstall the Microsoft System Center Virtual Machine Manager Guest Agent by using the Programs and Features item in Control Panel on the computer %ComputerName;.
20501	Virtual Machine Manager failed to shutdown the computer %ComputerName;.	Shutdown the computer %ComputerName; manually.
20502	Virtual Machine Manager failed to restart the computer %ComputerName;.	Restart the computer %ComputerName; manually.
20503	The computer %ComputerName; cannot be reached. A network ping resulted in the status %Status;.	Verify that there is network connectivity between the VMM management server and the computer %ComputerName;. If a firewall is enabled on the computer, ensure that the following firewall exceptions have been added: a) Port exceptions for HTTP/HTTPS; b) A program exception for %ProgramName;. If the issue persists, contact your network administrator.
20504	The %ServiceName; service is not running on the computer %ComputerName;. The %ServiceName; service status is %Status;.	Ensure that the %ServiceName; service is running on the computer %ComputerName;.
20505	The %ServiceName; service cannot be located on the computer %ComputerName;.	Ensure that the %ServiceName; service is installed and running on the computer %ComputerName;.
20506	Virtual Machine Manager cannot complete the Windows Remote Management (WinRM) request on the computer %ComputerName;.	Ensure that the Windows Remote Management (WinRM) service and the Virtual Machine Manager Agent service are installed and running. If a firewall is enabled on the computer, ensure that the following firewall exceptions have been added: a) Port exceptions for HTTP/HTTPS; b) A program exception for %Program Name;.
20507	The VMM management server cannot locate Windows Remote Management (WinRM) listeners on the computer %ComputerName;. The diagnostic command '%Command;' failed with the exit code %ExitCode;.	Ensure that WinRM listeners are configured, and that the firewall is not blocking HTTP/HTTPS traffic. If the error persists, reinstall or upgrade the Virtual Machine Manager agent on the computer %ComputerName;.
20508	The VMM management server cannot check Windows Remote Management (WinRM) configuration settings on the computer %ComputerName;. The diagnostic command '%Command;' failed with the exit code %ExitCode;.	Ensure that WinRM is configured correctly, and that firewall is not blocking HTTP/HTTPS traffic. If the error persists, reinstall or upgrade the Virtual Machine Manager agent on the computer %ComputerName;.
20509	Virtual Machine Manager agent communication is blocked. The version of the VMM agent (%CurrentVersion;) on the computer %ComputerName; is unsupported.	Update the VMM agent, and then try the operation again.
20510	An upgrade is available for Virtual Machine Manager agent version %CurrentVersion; on the computer %ComputerName;.	Update the VMM agent, and then try the operation again.
20511	The version of virtualization software (%CurrentVersion;) is unsupported on the computer %ComputerName;.	Update the virtualization software to a supported version, and then try the operation again.
20512	The version of virtualization software (%CurrentVersion;) is upgradable on %ComputerName;.	Update the virtualization software, and then try the operation again.
20513	The VMM management server cannot retrieve performance data for the computer %ComputerName;. This issue may occur if the performance counter provider in the Virtual Machine Manager agent is corrupted.	Restart the System Center Virtual Machine Manager Agent service on the computer %ComputerName;. This automatically restarts the performance provider. If the error persists, reinstall the VMM agent on the computer %ComputerName;.
20514	The VMM management server cannot retrieve performance data on the computer %ComputerName;. This issue may occur if the performance counters were not registered correctly during installation of the VMM agent.	Re-register the performance counters from an elevated command prompt on the computer %ComputerName; by running the following commands: \n1) unlodctr.exe /m:"(Virtual Machine Manager installation directory)\bin\scperfprovider.man"\n2) lodctr.exe /m:"(Virtual Machine Manager installation directory)\bin\scpe rfprovider.man" \n3) Restart the System Center Virtual Machine Manager Agent (SCVMMAgent) service. \nIf the problem persists, reinstall the VMM agent on the computer %ComputerName;.
20515	The Virtual Machine Manager agent cannot be upgraded remotely from the computer % ComputerName; without specifying administrative credentials for the computer.	Specify administrative credentials, and then try the operation again .
20516	The VMware ESX host %ComputerName; is not in a connected state.	Ensure that the host configuration is correct and that the host is in a connected state on the VMware vCenter Server.
20517	The VMware ESX host %ComputerName; is not turned on.	Ensure that the host is turned on.
20518	Virtual Machine Manager could not query Active Directory Domain Services. The fully qualified domain name (%DomainName;) may not be entered correctly.	Verify that the fully qualified domain name (%DomainName;) and the credentials, if provided, are correct and then try the operation again.
20519	The specified Active Directory search filter is empty.	Specify a valid search filter to discover computers by following the LDAP query filter syntax (http://msdn.microsoft.com/en-us/library/ms675768(v=VS.85).aspx), and then try the operation again.
20520	The specified Active Directory search filter is not valid.	Specify a valid search filter by following the LDAP query filter syntax (http://msdn.microsoft.com/en-us/library/ms675768(v=VS.85).aspx), and then try the operation again.
20521	Virtual Machine Manager cannot add a host that is running a 32-bit Windows Server operating system. Therefore, the selected computer %ComputerName; cannot be added as a host.	Select a computer that is running a supported 64-bit Windows Server operating system, and then try the operation again.
20522	Virtual Machine Manager cannot upgrade the agent on a host that is running a 32- bit Windows Server operating system.	The selected computer %ComputerName; cannot be a host because VMM no longer supports 32-bit hosts. Remove the computer %ComputerName; from VMM management. Select a computer that is running a supported 64-bit Windows Server operating system, and then try the operation again.
20523	The version of the Windows operating system on the computer %ComputerName; is not supported for a host.	Upgrade the operating system to Windows Server 2008 SP2 or a later supported version, and then try the operation again.
20524	Virtual Machine Manager has added the Secure Sockets Layer (SSL) certificate with thumbprint %CertificateHash; obtained from the computer %ComputerName; to the Trusted People store of the VMM management server.
20525	There is already a Secure Sockets Layer (SSL) certificate that is associated with TCP port %TCPPort; on the computer %ServerName;.	Ensure that no application listens for HTTPS traffic on TCP port %TCPPort;.
20526	The operation cannot be performed on the computer %ComputerName; because one or more virtual machines on the host are in running state.	Ensure that no virtual machines on the host %ComputerName; are in a running state, and then try the operation again.
20527	Either a RunAs account or user credentials are required for this operation.	Provide either a RunAs account or user credentials, and then try the operation again.
20528	The operation cannot be performed on the computer %ComputerName; because the Hype r-V role is not enabled. VMM automatically installs Hyper-V, but requires a server restart to enable the role.	Restart the server, ensure that the Hyper-V role is enabled, and the n try the operation again.
20529	The computer %ComputerName; is not managed by a VMM management server.	Add the computer %ComputerName; as a managed host, and then try the operation again.
20530	Virtual Machine Manager failed to create the Windows Remote Management (WinRM) listener because there is already an existing listener on the computer %ComputerName;.	Ensure that no other application listens for HTTP/HTTPS traffic on the computer %ComputerName;.
20531	The Windows Remote Management (WinRM) client cannot process the request. The port specified in the connection string is not valid. Valid values are between 1 and 65535.	Change the value for the port, and then try the request again.
20532	The operation cannot be performed on the computer %ComputerName; because the VMM management server and the host are on the same computer.	You must perform the operation manually.
20533	The virtualization platform parameter (%VirtualizationPlatform;) is either missing or unsupported for the current operation.	Retry the operation with the correct virtualization platform.
20534	The operating system on the computer %ComputerName; is no longer supported by Virtual Machine Manager. If this computer is already added as a server role to VMM, remove all server roles that are associated with this computer from VMM.	Ensure the operating system is supported, and try the operation again.
20535	The VMM management server cannot contact the Virtual Machine Manager agent on the computer %ComputerName; after the computer was restarted.	Ensure that the VMM agent is running on the computer %ComputerName;.
20536	The host has %BinaryDiskSpaceAvailable; megabytes (MB) of disk space available. However, %BinaryDiskSpaceRequired; MB of space is required for the disk space reserve.	Reduce the requested disk space reserve by using the Set-SCVMHost cmdlet.
20537	The host has %MemorySize; megabytes (MB) of memory available. However, %MemoryMin Required; MB of memory is required for the memory reserve.	Reduce the requested memory reserve by using the Set-SCVMHost cmdlet .
20538	Virtual Machine Manager failed to remove the Secure Sockets Layer (SSL) certificate with thumbprint %CertificateHash; obtained from %ComputerName; from the Trusted People store of the VMM management server. You can manually remove the certificate by using the Certificates snap-in.
20539	A new RunAsAccount '%Name;' will be created using the credentials passed to this task. Other users in this role '%UserRoleName;' and users in parent user roles of this role can access to this RAA.
20540	Failed to save state for one or more of the virtual machines.	Resolve individual save state job errors and/or manually put the virtual machines in save state and then try the operation again.
20541	The host could not be added because Virtual Machine Manager could not determine a default host group to place it in.	Please specify a host group that you have access to, and try the operation again.
20542	Failed to import certificate because The Common Name %Name; does not match the host name %ComputerName;.	Retry the operation with full administrator credentials or provide a certificate with a matching Common Name.
20543	The certificate store already contains a certificate for host %ComputerName;.	Verify the correctness of the certificate. A full administrator can overwrite the existing certificate or remove it if not in use by VMM.
20700	Could not retrieve console parameters for virtual machine %VMName;.	Ensure that the virtual machine exists and that the host %VMHostName; can be contacted, and then try the operation again.
20701	Could not retrieve console parameters for virtual machine %VMName; because it doe s not reside on a host.	Deploy the VM to a host and then try the operation again.
20900	Virtual Machine Manager cannot add %ComputerName; as a virtualization manager because VMware vCenter Server version %SoftwareVersion; is not supported.	Use vCenter Server 4.0 Update 1 or later.
20901	The VMware ESX host %ComputerName; cannot be found on VMware vCenter Server %ServerName;.	Specify a valid ESX host name and then try the operation again.
20902	The VMware ESX host %ComputerName; cannot be added because the host is not in a connected state.	Ensure that the host configuration is correct and that the host is in a connected state on the VMware vCenter server.
20903	The VMware datastore %Name; cannot be found on VMware vCenter Server %ServerName;.	Specify a valid datastore name and then try the operation again.
20904	A VMware portgroup with VLAN ID %VlanId; cannot be found on virtual network %VirtualNetworkName;.	Use a portgroup that exists on given virtual network.
20905	A VMware portgroup named %Name; cannot be found.	Use a portgroup that exists on given virtual network.
20906	Virtual Machine Manager cannot add %ComputerName; as a Virtual Machine Host because VMware ESX Server version %SoftwareVersion; is not supported.	Use ESX Server 3.5 or later.
20907	Virtual Machine Manager cannot add %ComputerName; as a virtualization manager because %ComputerName; is not running vCenter API.	Use a server which is running vCenter API.
20908	Removing unassigned VLANs from a VMware ESX Server is not supported.	This operation is not supported.
20909	Could not retrieve a certificate from the %ServerName; server because of the error: %VMAsyncTaskErrorMessage;	Specify a valid server name and port.
20910	A referenced VMDK (%Name;) is missing from the VMware template.	Please re-import the VMware template.