Virtual Machine Manager Error Codes (10000-10499)

Virtual Machine Manager Error Codes (10000-10499)

To find a specific error message in this table, type Ctrl-F and enter the error code. If you have additional information about how to fix an error, add it to the "Additional Troubleshooting Information" column.

Code

Message

Recommended Action (in product)

Additional Troubleshooting Information

10200

Setup has detected an unsupported version of Windows Automated Installation Kit (WAIK) on this computer.

Uninstall WAIK from this computer and then run Setup again. Setup will automatically install the correct version.

10201

Share name %ShareName; contains one or more characters that are not valid or has too many characters.

A share name cannot contain any of the following characters: /\[]=?*+;,<>|: and cannot be longer than 80 characters. Enter a different library share name and then try the operation again.

10202

The portal host header %SspHeader; contains one or more characters that are not valid.

A portal host header name can contain only alphanumeric characters, and periods or dashes. Enter a different portal host header name and then try the operation again.

10203

Setup cannot add all domain users and domain groups from the local Administrators group to the VMM Administrator user role.

To use an SQL Server 2008 instance and database, the SQL Server 2008 Management Tools - Basic or Command Line Utilities must be installed on the Virtual Machine Manager server.

To install the management tools, run SQL Server 2008 Setup, and, on the Feature Selection page, select Management Tools - Basic, and then complete the wizard. Or, to download and install the command line utilities, go to http://go.microsoft.com/fwlink/?LinkId=110393.

10215

The specified SQL Server database, %DatabaseName;, is a Virtual Machine Manager 2007 database, which is not valid for this configuration.

Either specify the database name that is provided with the OEM Setup, or create a new database by typing a new database name, and then selecting the "Create a new database" check box.

10216

Setup could not retrieve the Virtual Machine Manager server information from Active Directory.

Ensure that the VMM server has a service connection point registered in the Active Directory, and then try the operation again. If you are using disjoint namespace, specify fully qualified Active Directory domain name of the VMM server.

10217

Setup could not retrieve the Virtual Machine Manager server name from the .ini file.

Ensure that the VMM server name is correctly specified in the .ini file, and then try the operation again.

Ensure the setup media is not removed during upgrade and then try upgrading the Virtual Machine Manager server again.

10221

The command %FileName; with the argument %CommandlineArgument; failed.

Run the command in a Command Prompt window, resolve any errors, and then run Virtual Machine Manager Setup again.

10222

The specified SQL Server database, %DatabaseName;, is a Virtual Machine Manager 2007 database, which cannot be upgraded directly to VMM 2008 R2. A VMM 2007 database must first be upgraded to VMM 2008 before installing VMM 2008 R2.

Either specify a new database, an empty database, or an existing VMM 2008 R2 database. If you have an existing VMM 2008 database, VMM 2008 R2 automatically detects and upgrades the database when you upgrade the VMM 2008 server.

10223

The Virtual Machine Manager 2008 R2 Server upgrade failed.

Ensure the setup media is not removed during upgrade and then try upgrading the Virtual Machine Manager server again.

Verify that the domain name and the credentials, if provided, are correct and then try the operation again.

10408

This cmdlet can be run only on a Virtual Server host.

Specify a Virtual Server host and then try the operation again.

10409

Virtual Machine Manager cannot contact %ComputerName;.

1. Verify that the correct security file is specified.\n2. Verify that DCOM access, launch, and activation permissions are enabled for the Administrators group on %ComputerName;\n3. Use dcomcnfg.exe to modify permissions as needed and then try the operation again.

Specify a host group that is not a root host group and then try the operation again.

10411

The host group does not exist on VirtualCenter server %ComputerName;.

Specify a valid host group and then try the operation again.

10412

Virtual Machine Manager cannot enable the Hyper-V role on %ComputerName; and will add it as a Virtual Server host. If the host is intended to be used as a Hyper-V host, but you are not sure whether the host has hardware-assisted virtualization support, or whether it is enabled in the BIOS, download the Virtualization Detect (DetectVp.EXE) tool and run it on the host to confirm that it meets the requirements. To download the tool as part of the Windows Logo Kit (WLK), go to http://go.microsoft.com/fwlink/?LinkId=121104. If hardware-assisted virtualization support is not enabled in the BIOS, enable it. Then, enable the Hyper-V role, remove the host from the VMM server, uninstall Virtual Server from the host, and add the host to VMM server again.

BLANK

10413

Virtual Machine Manager is unable to add the cluster %ComputerName; as a clustered host because the operating system is not supported. Clustered hosts must be running Windows Server 2008 or later.

Ensure that the cluster is running Windows Server 2008. If the operating system was updated recently, Active Directory Domain Services updates might still be pending. Wait until Active Directory Domain Services updates run, and then try adding the cluster again.

10414

Virtual Machine Manager cannot add %ComputerName; as a Hyper-V host because the Hyper-V version detected on %ComputerName; is not the released version.

1) If the host is intended to be used as a Hyper-V host, download and install the released version of Hyper-V (KB950050) from http://go.microsoft.com/fwlink/?LinkId=142900, and then download and install Hyper-V update (KB956589) from http://go.microsoft.com/fwlink/?LinkID=113199. If you are not sure whether the host has hardware-assisted virtualization support or whether it is enabled in the BIOS, download the Virtualization Detect (DetectVp.EXE) tool and run it on the host to confirm that it meets the requirements. To download the tool as part of the Windows Logo Kit (WLK), go to http://go.microsoft.com/fwlink/?LinkId=121104.\n2) If the host is intended to be used as a Virtual Server host, download and install Virtual Server 2005 R2 SP1 and the latest update on the host. To download Virtual Server 2005 R2 SP1, go to http://go.microsoft.com/fwlink/?LinkID=120488. To download the latest update, go to http://go.microsoft.com/fwlink/?LinkId=121055.

10415

Virtual Machine Manager is not able to use Hyper-V on host %ComputerName;. You must accept the Microsoft Software License Terms for Hyper-V on %ComputerName; before Virtual Machine Manager can manage the host.

Install the Hyper-V Client Management Pack on the host or on another computer running Windows Server 2008. In Administrative Tools, open Hyper-V Manager, connect to %ComputerName;, accept the license terms, and then refresh %ComputerName; in the Host view of the VMM Administrator Console.

10416

The specified key length for the Virtual Machine Remote Console (VMRC) certificate request is not valid.

Valid key lengths are 512, 1024, 2048, 4096, and 8192.

10417

Virtualization manager %ComputerName; is not associated with this Virtual Machine Manager server.

Check the virtualization manager name and then try the operation again.

10418

Virtual Machine Manager cannot add host %ComputerName; because the version of Virtual Server installed on the host is not supported.

Install Virtual Server 2005 R2 SP1 on the host %ComputerName; from http://go.microsoft.com/fwlink/?LinkId=120488 and then apply update 948515 from http://go.microsoft.com/fwlink/?LinkId=120407.

10419

The -SshPublicKey and -SshPublicKeyFile parameters are mutually exclusive.

Check the remote server name, port and SSH public key, and then try the operation again.

10421

The specified user account cannot be the same as the VMM service account.

Specify a different account and then try the operation again.

10422

One or more of the servers in the AddHost list is running the Windows Server 2008 operating system. If the Hyper-V role is not enabled on any of these servers, Virtual Machine Manager will enable the role on those servers as part of the AddHost process, which will result in a restart of the servers.\n\nDo you want to continue?

BLANK

10423

If the Hyper-V role is not enabled for selected Windows Server 2008 hosts, Virtual Machine Manager will attempt to enable it automatically. Enabling the Hyper-V role will cause the selected servers to immediately restart. Restarting the VMM Server will stop any running jobs and require the host to be added again after Hyper-V is enabled.\n\nDo you want to continue?

BLANK

10424

If you continue, Virtual Machine Manager will no longer manage the following virtual machine host, and the host will be deleted from VMware VirtualCenter: %ComputerName;.\n\nTo stop VMM from managing VMware ESX Server hosts without deleting the virtual machine hosts, remove the VMware VirtualCenter server from VMM.In Administration view, use the Remove action for the Virtualization Managers node.\n\nDo you want to continue?

BLANK

10425

Virtual Machine Manager has detected that %ComputerName; is either a Windows Server 2008 failover cluster or a node of a failover cluster. Virtual Machine Manager will add all nodes of the failover cluster. If the Hyper-V role is not enabled, all nodes will be restarted as part of enabling the role.\n\nDo you want to continue?

This property can be changed only by using the VMware VirtualCenter Server to change the host's maintenance mode setting. Putting an ESX Server host into maintenance mode sets the AvailableForPlacement property in VMM to false, and taking an ESX Server host out of maintenance mode sets the AvailableForPlacement property in VMM to true.

To update the VMM agents on the nodes of a highly available library server, in Administration view, expand Managed Computers. Then select each of the library servers and click the Update Agent action. To find out the nodes of a highly available library server, you can view the properties of the highly available library server or use the Discover-Cluster cmdlet.

10429

An older version of the Virtual Machine Manager server is installed on %ComputerName;. The VMM agent on the VMM server cannot be upgraded independently.

Remove %ComputerName; from the Managed Computers view of the VMM Administrator Console, uninstall the VMM server from %ComputerName;, and then add %ComputerName; back as a host or library server.

10431

You cannot put a host into maintenance mode if the host is not responding.

Resolve the issue on the host, and then try the operation again.

10432

You cannot migrate the virtual machines if the host is not a clustered host.

Either add the host to a Windows Server 2008 R2 cluster, and then try the operation again, or do not migrate the virtual machines.

10433

You cannot migrate the virtual machines if the host is not in a Windows Server 2008 R2 cluster.

Either add the host to a Windows Server 2008 R2 cluster, and then try the operation again, or do not migrate the virtual machines.

10434

No suitable host is available for migrating the existing highly available virtual machines.

Either improve the host ratings for the other hosts within the same cluster, and then try the operation again, or do not migrate the virtual machines.

10435

Virtual Machine Manager was not able to import the Hyper-V security settings for the selected host from %InputFileName;.

Repair the Hyper-V security settings on the host, and then try the operation again.

10436

Virtual Machine Manager does not support updating an agent on a host that is in a non-trusted domain or on a perimeter network.

If the host is in a non-trusted domain, remove %ComputerName; from VMM in Hosts view of the VMM Administrator Console. Then use the Add Hosts Wizard to add the host and automatically install a new agent.\n\nIf the host is on a perimeter network, after you remove the host from VMM, you must manually uninstall the VMM agent from the host computer, install a new agent locally on the host, and then add the host to VMM.

10437

Virtual Machine Manager failed to add %ComputerName; as a host.

Ensure that the Virtual Machine Manager Agent service is started on %ComputerName;, and then try the operation again.

10438

Virtual Machine Manager failed to look up service principal name %ServicePrincipalName; in Active Directory.

Check the network connectivity to the Domain Controller, and then try the operation again. If the problem persists, contact your network administrator.

10439

Virtual Machine Manager failed to add service principal name %ServicePrincipalName; in Active Directory.

Check the network connectivity to the Domain Controller, and ensure that the VMM service account has the proper permissions for adding service principal names. For more information, refer to the documentation at http://go.microsoft.com/fwlink/?LinkId=141963.

10440

The VMM server was unable to impersonate the supplied credentials.

Ensure that the credentials are valid. In addition, the VMMService must run as the local system account or a domain account with sufficient privileges to be able to impersonate other users.

10441

Virtual Machine Manager cannot enable the Hyper-V role on %ComputerName;.

If the host is intended to be used as a Hyper-V host, but you are not sure whether the host has hardware-assisted virtualization support, or whether it is enabled in the BIOS, download the Virtualization Detect (DetectVp.EXE) tool and run it on the host to confirm that it meets the requirements. To download the tool as part of the Windows Logo Kit (WLK), go to http://go.microsoft.com/fwlink/?LinkId=121104. If hardware-assisted virtualization support is not enabled in the BIOS, enable it. Then, enable the Hyper-V role, and add the host to VMM server again.

10442

Virtual Machine Manager has detected that a software update is needed on host %ComputerName;.

1) Run Windows Update on the host to ensure that the latest Hyper-V or Virtual Server updates are installed.\n2) Ensure that the required Hyper-V update (KB956589) is installed on the Hyper-V host. You can download this update from http://go.microsoft.com/fwlink/?LinkID=113199.\n3) Ensure that the required Background Intelligent Transfer Service (BITS) update (KB956774) is installed on the Hyper-V host. You can download this update from http://go.microsoft.com/fwlink/?LinkId=142906.

10443

Virtual Machine Manager has detected that %ComputerName; is a node of a failover cluster. You cannot add a cluster node as a standalone host.

Use Add-VMHostCluster to add the entire cluster instead.

10444

The VMM server was unable to impersonate the supplied credentials.

To add a host in a disjointed domain namespace, ensure that the credentials are valid and of a domain account. In addition, the VMMService must run as the local system account or a domain account with sufficient privileges to be able to impersonate other users.