System Center 2012 – Virtual Machine Manager (VMM) Error Codes [10000-10999]

  • Article

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

10200

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

Uninstall WAIK from this computer, go to http://www.microsoft.com/do wnloads/details.aspx?familyid=696DD665-9F76-4177-A811-39C26D3B3B34 to download the Windows Automated Installation Kit a nd install it, and then run Setup again.

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.

10204

Either the domain account or the password you entered are not valid.

Please enter a valid domain name, user name, and user password and then try the operation again.

10205

The domain account %UserName; is not a member of the local Administrators group.

Either add the domain account to Administrators group, or use another domain account that is in the local Administrators group.

10206

VMM requires either Operations Manager 2007 SP1 or Operations Manager 2007 R2.

Install a supported version of Operations Manager, and then run Setup again.

10207

Setup was not able to retrieve the service account from the specified Virtual Machine Manager management server.

Specify a different VMM management server and then try the operation again.

10208

Setup encountered an error while importing management packs.

Uninstall all management packs related to System Center Virtual Machine Manager and then run Setup again. Setup will import the required management packs.

10209

Setup could not install Virtual Machine Manager management server because the computer name has more than 15 characters.

Change the computer name to be less than or equal to 15 characters and then run Setup again.

10210

The parameter /prep is valid only for installing the Virtual Machine Manager management server.

For help with setup and information about parameter usage, run the command setup.exe /?.

10211

Another user or process is currently using the Server Manager console.

Close the Server Manager console and then run Setup again.

10212

File %CopyFileFromCD; was not found on the Virtual Machine Manager CD.

Uninstall the VMM management server, verify that file %CopyFileFromCD; is on the CD, and then run Setup again. If the problem persists, contact Microsoft Help and Support.

10213

Setup could not install Windows Automated Installation Kit (WAIK) related assemblies in the Global Assembly Cache.

Cancel Virtual Machine Manager Setup and then run Setup again.

10214

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 management 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 2 007 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 management server information from Active Directory Domain Services (AD DS).

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

10217

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

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

10218

Setup could not import the System Center Virtual Machine Manager Management Pack into Operations Manager server because one or more required management packs are missing. The VMM Management Packs cannot be deployed unless the following component management packs are present in Operations Manager 2007:\nWindows Server Internet Information Services 2003, \nWindows Server 2008 Internet Information Services 7, \nWindows Server Internet Information Services Library, \nSQL Server Core Library.

To provide the missing component management packs, ensure that the following management packs have been imported into Operations Manager server:\n Microsoft Windows Server 2000/2003 Inter net Information Services Management Pack for OpsMgr 2007 (version 6.0.6278.0 or later)\n Microsoft SQL Server 2000/2005 Management Pack\n You can download the management packs from the System Center Operations Manager 2007 Catalog at http ://go.microsoft.com/fwlink/?LinkId=86411

10219

The Virtual Machine Manager database could not be upgraded.

Ensure that the SQL Server administrator credentials are valid, Virtual Machine Manager Database is a valid V2 RTM database and then try upgrading the Virtual Machine Manager management server again.

10220

The Virtual Machine Manager 2008 Server upgrade failed.

Ensure the setup media is not removed during upgrade and then try up grading the Virtual Machine Manager management 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 2 007 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 domain account specified for the service account could not be verified.

Ensure that the domain name, user name, and password are correct, an d then try the operation again.\n\nEnsure that a domain controller for the Active Directory domain is available.\n\nEnsure that the domain account is a member of the Administrators group on the local computer.

10400

Before Virtual Machine Manager can perform the current operation, the virtualization server must be restarted.

Restart %ComputerName; and then try the current operation again.

10401

 (Internal error.)

10402

Host configuration failed on %ComputerName; because the specified memory reserve exceeds the total memory.

Specify a memory reserve that is less than the total amount of memory.

10403

%ComputerName; is not listed in Active Directory Domain Services.

Verify that the computer name and the domain name are correct, and then try the operation again.

10404

%ComputerName; already serves the specified Virtual Machine Manager role.

Enter different computer name and then try the operation again.

10405

%ComputerName; does not have the specified virtualization software installed or enabled.

Install the correct virtualization software on %ComputerName;, or enter a different computer name and then try the operation again.

10406

Virtual Machine Manager cannot contact %ComputerName; because the credentials for %ComputerName; are missing.

Provide credentials for %ComputerName; and then try the operation again.

Command Line Interface: Run Associate-VMHost on %ComputerName;, providing root credentials, and then try the operation again.

10407

Virtual Machine Manager could not query Active Directory Domain Services.

Verify that the domain name and the credentials, if provided, are correct 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 d comcnfg.exe to modify permissions as needed and then try the operation again.

10410

Virtual Machine Manager cannot add an ESX host to host group "All Hosts."

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;. If you are not sure whether the host has hardware-assisted virtualization support, or whether it is enabled in the BIOS, downl oad 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 hardwa re-assisted virtualization support is not enabled in the BIOS, enable it. Then, enable the Hyper-V role and try to add the host to VMM management server again.

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 opera ting system was updated recently, Active Directory Domain Services updates might still be pending. Wait until Active Di rectory 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 H yper-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 an d 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 wheth er the host has hardware-assisted virtualization support or whether it is enabled in the BIOS, download the Virtualizat ion Detect (DetectVp.EXE) tool and run it on the host to confirm that it meets the requirements. To download the tool a s 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 up date, 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 console.

10417

Virtualization manager %ComputerName; is not associated with this Virtual Machine Manager management 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 h ttp://go.microsoft.com/fwlink/?LinkId=120488 and then apply update 948515 from http://go.microsoft.com/fwlink/?LinkId=1 20407.

10419

The -SshPublicKey and -SshPublicKeyFile parameters are mutually exclusive.

Resolve the conflict, and then try the operation again.

10420

VMM cannot establish a trust relationship for the SSH secure channel for %ServerName; server.

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

If the Hyper-V role is not enabled on any of the selected servers, Virtual Machine Manager will enable the role on those servers as part of the Add Host process, which will result in a restart of the servers. If any of these servers have a pending restart, they will also be restarted. \n\nDo you want to continue?

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 management 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?

10424

If you continue, Virtual Machine Manager will no longer manage the following VMware ESX host: %ComputerName;.\n\nThe host will not be deleted from VMware vCenter Server.\n\nDo you want to continue?

10425

Virtual Machine Manager has detected that %ComputerName; is either a Windows Serv er 2008 (or later) 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 or there is a pending restart on a cluster node, the node will be restarted as part of enabling the role.\n\nDo you want to continue?

10427

AvailableForPlacement property for a VMware ESX Server host cannot be changed directly within Virtual Machine Manager.

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 Availab leForPlacement property in VMM to false, and taking an ESX Server host out of maintenance mode sets the AvailableForPla cement property in VMM to true.

10428

Virtual Machine Manager agents on a highly available library server cannot be updated directly.

To update the VMM agents on the nodes of a highly available (HA) library server, in the Fabric Resources view, expand Servers. Then select each of the HA library server node agents and cl ick the Update Agent action. To find out the nodes of an HA 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 management server is installed on %ComputerName;. The VMM agent on the VMM management server cannot be upgraded independently.

Remove %ComputerName; from the Managed Computers view of the VMM con sole, uninstall the VMM management server from %ComputerName;, and then add %ComputerName; back as a host or library s rver.

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 virtualization host is not a clustered host.

Either add the host to a Windows Server 2008 R2 cluster, and then tr y 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 20 08 R2 cluster.

Either add the host to a Windows Server 2008 R2 cluster, and then tr y 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 o peration again.

10436

Virtual Machine Manager does not support updating or re-associating 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 the host (%ComputerName;) from VMM in the VMs and Hosts workspace of the VMM 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 tr y 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 management server was unable to impersonate the supplied credentials.

Ensure that the credentials are valid. In addition, the SCVMMService 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 management 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 require d 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 management 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 SCVMMService must run as the local system account or a domain account with sufficient privileges to be able to impersonate other users.

10600

The operating system specified for the template or guest operating system profile is not compatible with the answer file.

Specify unattend.xml format answer file for a Windows 2008 or Vista template, or a GuestOSProfile. Otherwise specify sysprep.inf format answer file.

10601

The specified unattended installation xml file is not valid.

Specify a valid unattend .xml file.

10602

Virtual Server does not support 64-bit virtual machines.

Place the virtual machine on a Windows Hyper-V or ESX host.

10603

Specified memory size %MemorySize; is not supported by the host %VMHostName; virtualization software.

Select a host that supports the specified memory limits or change th e memory specification. Valid memory size ranges from %MemorySizeMinLimit; to %MemorySizeMaxLimit;.

10604

Specified memory size %MemorySize; is not supported.

Specify a valid memory size and then try the operation again. Valid memory size ranges from %MemorySizeMinLimit; to %MemorySizeMaxLimit;.

10605

The specified VLAN configuration is not valid.

Ensure that the virtual network adapter is connected to a virtual ne twork, that a valid VLAN ID is specified, and then try the operation again.

10606

The -VirtualHardDisk and -PassThroughDisk parameters are mutually exclusive. You can specify only one of these parameters.

Specify either -VirtualHardDisk or -PassThroughDisk and then try the operation again.

10607

The VHDDrive operation requires either -VirtualHardDisk or -PassThroughDisk parameters.

Specify the -VirtualHardDisk or -PassThroughDisk parameter.

Command Line Interface: Specify either -VirtualHardDisk or -PassThroughDisk and then try the operation again.

10608

Cannot create a highly available virtual machine because Virtual Machine Manager could not locate or access %FolderPath;.

Ensure that the path exists and that the path is for a cluster disk in available storage, and then try the operation again.

10609

Cannot create a highly available virtual machine because host %HostNames; is not in a host cluster.

Specify a host that is in a host cluster and ensure that the cluster service is running on that host, and then try the operation again.

10610

Cannot change the Highly Available property for a virtual machine that is deploye d on a host.

You can change the HighlyAvailable property only when the virtual ma chine is stored in the library.

10611

Virtual Machine Manager does not support creation of highly available virtual mac hines for the virtualization software on host %VMHostName;.

To create a highly available virtual machine, select a clustered Hyper-V host.

10612

Cluster resource with name Virtual Machine %FriendlyName; already exists on clust er %VMHostName;.

Specify a different name for the virtual machine and then try the operation again.

10613

Cluster resource group with name Virtual Machine %FriendlyName; already exists on cluster %VMHostName;

Specify a different name for the virtual machine and then try the operation again.

10614

Cluster resource with name Virtual Machine Configuration %FriendlyName; already exists on cluster %VMHostName;

Specify a different name for the virtual machine and then try the operation again.

10615

Unable to move virtual hard disk. You can only move virtual hard disks that are c onnected to a virtual machine on a Virtual Server or Hyper-V host.

Ensure that the virtual hard disk is connected to a virtual machine on a Virtual Server or Hyper-V host and then try the operation again.

10616

Unable to move virtual hard disk. Only use the Move-VirtualHardDisk with Bus, Lun and BusType parameters for a New-VM or Move-VM JobGroup.

Check the parameters and then try the operation again.

10617

Specified location has a pass-through disk attached.

Ensure that the virtual disk drive attached at specified bus and LUN has a virtual hard disk attached, and then try the operation again.

10618

The virtual hard disk or its parent is attached to more than one Virtual Machine and cannot be moved.

Ensure that the specified virtual hard disk is associated with one virtual machine and then try the operation again.

10619

The user name provided is not a valid local administrator user name for this operating system.

Provide a valid user name other than the built-in Administrator account name and then try the operation again.

10620

The specified host disk is not attached to virtual machine on a host.

Ensure that the specified host disk is attached to a virtual machine and then try the operation again.

10621

The convert virtual disk drive operation timed out after waiting for %VHDActionTimeoutInHours; hours.

Try the operation again.

10622

The specified virtual disk drive is not connected to a host disk.

Ensure that the specified virtual disk drive has host disk attached and then try the operation again.

10623

The virtualization software for the virtual hard disk %FileName; is not compatible with the virtualization software on the host %VMHostName;.

Remove the specified virtual hard disk from the virtual machine or s pecify a different host, and then try the operation again.

10624

The virtualization software on the host %VMHostName; does not support integration services.

Specify a host with Hyper-V virtualization software and then try the operation again.

10625

The virtualization software on host %VMHostName; does not support setting the boo t order in the BIOS.

Migrate the virtual machine to a host that is running Windows Hyper- V and then try the operation again.

10626

Boot device type %BootDevice; is not valid.

Specify a valid parameter and try the operation again.

10627

The specified boot order is not complete. Not all valid boot devices are specified.

Include all valid boot devices in the boot order and then try the op ration again.

10628

The specified memory size for the virtual machine is not valid because of virtualization software restrictions on the host %VMHostName;. Virtual Machine Manager will set the virtual machine's memory t o %MemorySize; MB.

10629

The virtualization software on host %VMHostName; does not support a processor count of %Count;. Supported processor counts: %ValidProcessorCount;.

Specify a host with different virtualization software or change the processor count, and then try the operation again.

10630

The processor count of %Count; is not supported. The supported processor counts are %ValidProcessorCount;

Change the processor count and then try the operation again.

10631

The virtualization software for virtual machine %VMName; does not support shared SCSI bus configurations.

Specify a virtual machine with different virtualization software and then try the operation again.

10632

The virtualization software on the selected host does not support virtual hard disks on an IDE bus.

Specify a host that is running Windows Hyper-V or Virtual Server or change the bus type, and then try the operation again.

10633

The virtualization software on the specified host does not support user impersonation using the "Run As" parameter.

Do not specify "run-as" credentials and then try the operation again.

10634

Unable to store virtual machine %VMName; on library server %ServerName;. The virtual machine contains SAN-attached disks and cannot be stored on a highly available library server.

Select "Transfer over the network," and then try the operation again.

10635

Virtual machine customization is not supported for the %OSName; operating system.

Specify an operating system for which customization is supported and then try the operation again.

10636

The virtualization software on host %VMHostName; does not support customization of the %OSName; operating system.

Specify a host with different virtualization software and then try the operation again.

10637

The virtualization software on host %VMHostName; does not support the %OSName; operating system.

Specify a host with different virtualization software and then try the operation again.

10638

The virtualization software on host %VMHostName; does not support setting NumLock .

Specify a host that is running Windows Hyper-V and then try the operation again.

10639

The virtualization software on host %VMHostName; does not support changing the BI OS configuration.

Specify a host that is running Windows Hyper-V and then try the operation again.

10640

Hyper-V does not support the specified COM port setting.

Specify a named pipe for the COM port. Hype-V does not support mapping a virtual COM port to a physical COM port or a text file.

10641

The virtualization software on the host %VMHostName; does not support the creation of dynamic virtual hard disk.

Specify a Fixed Virtual Hard Disk disk type and then try the operation again.

10644

Virtual Machine Manager cannot access the WAIK (Windows Automated Installation Ki t) Image Manager DLLs.

Install WAIK and ensure that the Image Manager DLLs are installed in the GAC (Global Assembly Cache).

10645

Virtual machine %VMName; could not be cloned because it has checkpoints. That functionality is not supported for Hyper-V virtual machines.

Delete all checkpoints for the virtual machine and then try the operation again.

10646

The source and target location for virtual hard disk %FileName; are the same.

Ensure that the source and target locations are different and then try the operation again.

10647

The virtual network adapter for the virtual machine (%VMName;) is connected to a virtual network switch (%VirtualNetworkName;) that is not valid.

Ensure that the virtual network switch exists or disconnect the virtual network adapter, and then try the operation again.

10648

Windows Hyper-V does not support attaching a virtual floppy drive to a physical d rive.

To configure a virtual floppy drive, migrate the virtual machine to a host with different virtualization software and then try the operation again.

10649

Unable to migrate or clone the virtual machine %VMName; because the processor is not compatible with the host. To be migrated or cloned, the virtual machine must be stopped and should not contain any saved state or live checkpoints.

To select the most suitable host for virtual machine %VMName;, use the Migrate or Clone Virtual Machine Wizard. The wizard rates all available hosts based on their suitability for this virtual machine.

10650

Unable to migrate or clone the virtual machine %VMName; because the version of vi rtualization software on the host does not match the version of virtual machine's virtualization software on source (%S ourceHostVSVersion;). To be migrated or cloned, the virtual machine must be stopped and should not contain any saved st ate.

To select the most suitable host for virtual machine %VMName;, use either the Migrate Virtual Machine Wizard or the Clone Virtual Machine Wizard. The wizard rates all available hosts base d on their suitability for this virtual machine.

10651

Cannot create the template because source virtual machine %VMName; has checkpoint s. \n\nThis feature is not supported for virtual machines that are deployed on hosts running Windows Hyper-V.

Delete all checkpoints for the source virtual machine and then try the operation again.

10652

Cannot create template because source virtual machine %VMName; has pass-through disks.

Convert pass-through disks to virtual hard disks and then try the op eration again.

10653

The virtualization software on the host does not support the Limit Processor Functionality setting.

Migrate the virtual machine to a Windows Hyper-V host and then try the operation again.

10654

Could not reset local Administrator password on %VMName; to empty string before starting Sysprep.

Change the local security policy on the virtual machine to allow an empty string as a password and then try the operation again.

10655

Hardware changes while cloning a Hyper-V virtual machine, VMware virtual machine, or stored virtual machine are not supported and were ignored.

Make any hardware changes to the virtual machine after the cloning operation is complete.

10656

Unable to delete cluster resource group %FriendlyName; on host %VMHostName;.

Use Failover Cluster Management to delete the cluster resource group .

10657

Unable to move the virtual hard disk because a valid Bus, LUN, and Bus Type are n ot specified.

Specify a valid Bus, LUN, and BusType, and then try the operation ag ain.

10658

The %CmdletName; cmdlet requires an -OperatingSystem or -GuestOSProfile parameter .

Repeat the %CmdletName; cmdlet and specify a guest operating system, either directly (with the -OperatingSystem parameter) or by specifying a guest operating system profile (-GuestOSProfi le parameter).

10659

Cannot run Sysprep on virtual machine %VMName; because the template does not have a virtual hard disk attached that has been generalized.

Specify a template that has been generalized and then try the operation again.

10660

Cannot install virtualization guest services on virtual machine %VMName; because its virtual hard disks are generalized.

Install the virtualization guest services after the virtual machine has been customized.

10661

The virtualization software on the selected host does not support conversion of a pass-through disk to a virtual hard disk.

Migrate the virtual machine to a host that supports the conversion of pass-through disks and then try the operation again.

10662

Virtual machine %VMName; could not be cloned because the virtual machine has chec kpoints. This functionality is not supported for VMware virtual machines.

Delete all checkpoints for the virtual machine and then try the operation again.

10663

The specified pass-through disk and virtual machine are not on the same host.

Ensure that the pass-through disk and virtual machine are on the same host, and then try the operation again.

10664

BLANK.

BLANK.

10665

Cannot attach a pass-through disk to a virtual machine or template that is stored in the library.

To add a pass-through disk (host disk) to a virtual machine, deploy the virtual machine to a host that supports pass-through disks.

10666

Hardware changes while creating a template from a virtual machine are not supported and were ignored.

Make any hardware changes to the template after you create the template.

10667

The virtual machine being created from a template must contain at least one virtual hard disk, which must be generalized.

Specify at least one virtual hard disk that is generalized and then try the operation again.

10668

Cannot clone the virtual machine because the source virtual machine %VMName; has pass-through disks.

Convert the pass-through disks to virtual hard disks and then try the operation again.

10669

Pass-through disk %FileName; cannot be attached to the same virtual machine more than once.

BLANK

10670

The virtualization software on host %VMHostName; does not support the expanding o f a differencing virtual hard disk.

To expand the hard disk, migrate the virtual machine to a host that is running different virtualization software.

10671

The hard disk file (%FileName;) is not compatible with the SCSI adapter on the virtual machine (%VMName;).

Either specify a compatible hard disk file or convert the hard disk file (%FileName;) by using the VMware vCenter Server.

10672

You cannot remove virtual hard disk %FileName; with the Remove-VirtualHardDisk cmdlet because this virtual hard disk is associated with a virtual machine on host.

Use the Remove-VirtualDiskDrive cmdlet to remove virtual hard disk % FileName;.

10673

Unable to share the SCSI adapter. A shared SCSI adapter can only have one virtual hard disk attached to location 0.

Ensure that the SCSI adapter has one virtual hard disk attached to l ocation 0 and then try the operation again.

10674

Integration services cannot be enabled on a virtual machine that is stored in the library.

Deploy the virtual machine to a Hyper-V host and then try the operat ion again.

10675

Virtual machine customization is not supported for the %OSName; operating system. Please use the -NoCustomization parameter to create a template with the specified operating system.

Specify an operating system for which customization is supported, or use the -NoCustomization parameter, and try the operation again.

10676

Unable to create virtual hard disk %FileName; on library server %ServerName;. VMM cannot create a virtual hard disk on a library server that is not also a virtual machine host.

Select a library server that is also a virtual machine host, or use an existing virtual hard disk, and try the operation again.

10677

The Hyper-V exported file %FileName; is not valid.

Specify a valid Hyper-V .exp file.

10678

VMM cannot enable VLAN settings because the Virtual Network Adapter associated with virtual machine %VMName; is not connected to a virtual network.

10679

The virtual machine %VMName; resource group %FileName; could not be deleted from host %VMHostName;.

Manually delete resource group %FileName; from the host.

10680

The disk (%FileName;) cannot be attached as a pass-through to the virtual machine (%VMName;) because one or more volumes on the disk already are used by the same virtual machine.

Please specify a disk resource that is not used by this virtual machine or by any other virtual machine, and then try the operation again.

10681

Virtual Machine Manager cannot add virtual hard disk %FileName; because its forma t is not compatible with other disks on virtual machine %VMName;.

BLANK

10682

Virtual Machine Manager cannot add virtual hard disk %FileName; because its forma t is not compatible with other disks on template %VMName;.

BLANK

10683

Unable to contact the cluster service on the host computer (%ComputerName;).

Ensure that the cluster service is properly installed and running.

10684

The virtualization software on host %VMHostName; does not allow a virtual machine name to exceed %MaxLength; characters.

Specify a shorter virtual machine name and then try the operation again.

10685

You cannot perform set or remove operations on objects associated with a virtual machine checkpoint.

BLANK

10686

Virtual Machine Manager cannot clone virtual machine %VMName; on the Virtual Server host to a Hyper-V host because the virtual machine is in a saved state.

Delete the saved state, and then try the operation again.

10687

To create a template from a virtual machine, the virtual machine must have at least one virtual hard disk attached.

Ensure that the virtual machine has at least one virtual hard disk a ttached, and then try the operation again.

10688

The virtual hard disk (%FileName;) is a VMware (.vmdk) file. VMM does not support placing it on an IDE bus.

Either select a virtual hard disk of different type or select a SCSI adapter, and then try the operation again.

10689

Virtual Machine Manager does not support adding pass-through disks to virtual machines with checkpoints.

Ensure that virtual machine %VMName; does not contain checkpoints an d then try the operation again.

10690

Hyper-V does not support boot and system volumes on a disk attached to SCSI adapter. The disk at the location (%BusType;, %Bus;, %Lun;) must be moved to an IDE bus for the machine to boot up.

Modify the bus assignments so that boot and system volume disks are located on an IDE bus.

10691

Hyper-V does not support boot and system volumes on a disk attached to SCSI adapter. All disks containing boot and system volumes must be moved to an IDE bus for the machine to boot up.

Modify the bus assignments so that boot and system volume disks are located on an IDE bus.

10692

VMM cannot enable or disable the MAC addresses spoofing or VM network optimization settings because the Virtual Network Adapter associated with virtual machine %VMName; is not connected to a virtual network.

Connect the virtual network adapter to a virtual network, and then try the operation again.

10693

Unable to migrate or clone the virtual machine (%VMName;) because the processor i s not compatible with the virtualization host (%VMHostName;). To be migrated or cloned, processor features must be limi ted in the virtual machine hardware configuration. In addition, the virtual machine should not contain any saved state or checkpoints.

To select the most suitable host for virtual machine %VMName;, use either the Migrate Virtual Machine Wizard or the Clone Virtual Machine Wizard. The wizard rates all available hosts base d on their suitability for this virtual machine.

10694

Unable to migrate or clone the virtual machine (%VMName;) because the version (%T argetHostVSVersion;) of the virtualization software on the host (%VMHostName;) does not match the version of virtual ma chine's virtualization software on the source host (%SourceHostVSVersion;). To be migrated or cloned, the virtual machine must be stopped and should not be in a saved state.

To select the most suitable host for virtual machine %VMName;, use either the Migrate Virtual Machine Wizard or the Clone Virtual Machine Wizard. The wizard rates all available hosts base d on their suitability for this virtual machine.

10695

The virtual machine network optimization setting is supported only for virtual network adapters.

Choose a virtual network adapter, and try the operation again.

10696

The host network adapter does not support the specified virtual network adapter configuration.

Select a host network adapter that supports this configuration.

10697

VMM could not initiate live migration of the virtual machine (%VMName;) to the virtual machine host (%VMHostName;) using this cluster configuration.

Check the cluster configuration and then try the operation again.

10698

The virtual machine (%VMName;) could not be live migrated to the virtual machine host (%VMHostName;) using this cluster configuration.

Check the cluster configuration and then try the operation again.

10699

Virtual machine %VMName; cannot be deployed or migrated to host %VMHostName; because the host is in maintenance mode.

Retry the operation after the host is out of maintenance mode.

10700

This operation cannot be performed because host %VMHostName; is in maintenance mo de.

Wait until the host is out of maintenance mode, and then try the operation again.

10701

The virtualization software on the selected host does not support adding or removing a virtual disk drive on IDE adapter while the virtual machine is running.

Ensure that the virtual machine is in stopped state or select a SCSI adapter and try the operation again.

10702

This operation cannot be performed because the host (%VMHostName;) is not in maintenance mode.

Place the host in maintenance mode, and then try the operation again.

10703

The specified file name %FileName; is not valid.

Check the file name for characters that are not valid, and then try the operation again.

10704

The virtualization software on the host does not support the Limit Processor For Migration setting.

Shut down the virtual machine and then migrate it to a Windows Hyper -V R2 host, and then try the operation again.

10705

The virtualization software on the host (%VMHostName;) does not support the Limit Processor for Migration setting. After migration, the processor features for the virtual machine (%VMName;) will not b e limited for migration.

Clear the Limit Processor for Migration setting from the virtual machine hardware configuration, and then try the operation again.

10706

Processor compatibility information for the virtual machine (%VMName;) is not available. The virtual machine may not start or operate correctly on the virtualization host (%VMHostName;).

Export and import the virtual machine using VMM, and then retry the operation.

10707

The virtual machine (%VMName;) is not compatible with the virtualization host (%V MHostName;). The virtual machine may not start or operate correctly on the host. This may be due to inconsistent processor compatibility information.

Store the virtual machine in the library, and then try the operation again.

10708

The virtual machine (%VMName;) and the virtualization host (%VMHostName;) use processors from different manufacturers. A running or saved virtual machine cannot be migrated to a server that has a proc essor from a different manufacturer.

Shut down the virtual machine or select a host destination that has a processor from the same manufacturer and then try the operation again.

10709

The virtual machine (%VMName;) is using processor-specific features not supported on the virtualization host (%VMHostName;). To allow for migration of this virtual machine to a server with a different processor, modify the virtual machine settings to limit the processor features used by the virtual machine.

Limit the processor features for the virtual machine on the processor tab of the hardware configuration page, and then try the operation again.

10710

Cannot perform a storage migration on the virtual machine because the source virtual machine %VMName; has pass-through disks.

Convert the pass-through disks to virtual hard disks and then try th e operation again.

10711

The virtual machine (%VMName;) could not be moved using live migration to the vir tualization host (%VMHostName;) because another live migration is in progress.

Wait until the conflicting live migration is complete, and then try the operation again.

10712

Moving the virtual machine (%VMName;) to the virtualization host (%VMHostName;) using live migration could not be completed because the operation timed out.\nTime-out interval (in seconds): %LMTimeout InSecs;

Check the cluster configuration and then try the operation again.

10713

The virtual machine (%VMName;) was not moved using live migration to the virtuali zation host (%VMHostName;) because the operation was cancelled.

Retry the operation.

10714

VMM cannot determine the processor family for server %VMHostName;. Virtual machin e %VMName; may not start or operate correctly on server %VMHostName;.

To select the most suitable host for virtual machine %VMName;, use the Migrate or Clone Virtual Machine Wizard. The wizard rates all available hosts based on their suitability for this vi rtual machine.

10715

VMM cannot determine the processor family for virtual machine %VMName; or one of its snapshots. The virtual machine may not start or operate correctly on server %VMHostName;.

To select the most suitable host for virtual machine %VMName;, use the Migrate or Clone Virtual Machine Wizard. The wizard rates all available hosts based on their suitability for this virtual machine.

10716

Local files have not been specified for some virtual disk drives attached to the new Virtual Machine.

When the local virtual disk option is specified, VMM requires that a local file be specified for each virtual disk drive that is attached to the virtual machine.

10717

The specified local virtual hard disk file %FileName; is already attached to another virtual machine.

Ensure that the specified file is not attached to another virtual machine, and then try the operation again.

10718

VMM does not support attachment of a local virtual hard disk file to virtual machine in library.

Ensure that the virtual machine is on a host, and then try the operation again.

10719

VMM does not support the specification of an UNC path with the -UseLocalVirtualHa rdDiskFile parameter.

Specify a local file path for the virtual hard disk file, and then try the operation again.

10720

Path to local file must be specified for the virtual disk drive

Specify the local file path using -Path parameter and retry the operation.

10721

VMM does not support the attachment of a local virtual hard disk in a clone virtual machine operation.

None

10722

VMM does not support the attachment of a local virtual hard disk with the specified parameters.

None

10723

You cannot undo the migration job of virtual machine %VMName; at this stage.

To complete the migration of the virtual machine to its original des tination, retry the migration job.

10724

The specified maximum memory value is less than the specified startup memory value.

Either ensure that the maximum memory value is greater than the startup memory value, or do not use dynamic memory allocation.

10725

To specify the maximum memory value or the preferred buffer percentage, dynamic memory must be enabled.

Enable dynamic memory on the virtual machine or hardware profile, and then set these properties.

10726

To configure dynamic memory settings, including the relative memory weight, the host must be running Windows Server 2008 R2 with Service Pack 1 or later.

For a Hyper-V virtual machine, either disable dynamic memory or place the virtual machine on a host that supports dynamic memory.

10727

To change the relative memory weight or the preferred buffer percentage, the virtual machine must be off, running, or paused. The virtual machine cannot be in a saved state.

Resume or turn off the saved virtual machine to configure these properties.

10728

No passthrough disk was found for the creation of the virtual machine (%VMName;).

Please ensure that a passthrough disk resource is available, and the n try the operation again.

10729

The VMConfiguration parameter was passed for creation of the virtual machine (%VM Name;) along with some inappropriate cmdlets in the JobGroup.

For a description of the cmdlets in this type of JobGroup, see the help for the virtual machine creation cmdlets.

10730

Incomplete VMConfiguration was passed for creation of the virtual machine.

Ensure that the VMConfiguration has a VMHost or a private cloud assigned. Also ensure that a ComputerName and VMLocation have been assigned and retry the operation.

10731

VMConfiguration cannot be created for the internal template (%Name;).

Ensure that the template is not part of a service template and retry the operation.

10732

VMConfiguration (%Name;) cannot be removed since it is associated to a service co nfiguration.

Ensure that the VMConfiguration is not part of a service template and retry the operation.

10733

Creating the virtual machine (%VMName;) and rapidly provisioning it using differencing disks is allowed only from a template.

Use a template for rapidly provisioning a virtual machine using differencing disks.

10734

Static MAC address or MAC address pool is not specified for a virtual network adapter configured for static MAC address.

Specify MAC address or MAC address pool using Set-SCVirtualNetworkAd apterConfiguration, or configure virtual network adapter for dynamic MAC address.

10735

A static MAC address or MAC address pool is specified for a virtual network adapter that was configured for a dynamic MAC address.

Do not specify MAC address or MAC address pool using Set-SCVirtualNe tworkAdapterConfiguration, or configure the virtual network adapter for a static MAC address.

10736

A static IPv4 address or IPv4 IP address pool is not specified for a virtual network adapter that was configured for static IPv4 address.

Specify an IPv4 address or IPv4 address pool using Set-SCVirtualNetw orkAdapterConfiguration, or configure the virtual network adapter for a dynamic IPv4 address.

10737

A static IPv4 address or IPv4 address pool is specified for a virtual network adapter that was configured for a dynamic IPv4 address.

Do not specify an IPv4 address or IPv4 address pool using Set-SCVirt ualNetworkAdapterConfiguration, or configure the virtual network adapter for a static IPv4 address.

10738

A static IPv6 address or IPv6 address pool is not specified for a virtual network adapter that was configured for static IPv6 address.

Specify an IPv6 address or IPv6 address pool using Set-SCVirtualNetworkAdapterConfiguration, or configure the virtual network adapter for a dynamic IPv6 address.

10739

A static IPv6 address or IPv6 address pool is specified for a virtual network adapter that was configured for a dynamic IPv6 address.

Do not specify an IPv6 address or IPv6 address pool using Set-SCVirtualNetworkAdapterConfiguration, or configure the virtual network adapter for a static IPv6 address.

10740

To specify the maximum number of monitors or the maximum monitor resolution, the Microsoft RemoteFX 3D video adapter must be enabled.

Enable the RemoteFX 3D video adapter on the virtual machine or hardware profile, and then set these properties.

10741

To configure Microsoft RemoteFX 3D video adapter settings, the host must be running Windows Server 2008 R2 with Service Pack 1 or later, with RemoteFX enabled. RemoteFX is a feature of the Remote Desk top Virtualization Host role service under the Remote Desktop Services role.

For a Hyper-V virtual machine, either configure the video adapter setting on the virtual machine to use the standard video adapter or place the virtual machine on a host that supports the RemoteFX 3D video adapter.

Command Line Interface: For a Hyper-V virtual machine, either disable the RemoteFX 3D video adapter or place the virtual machine on a host that supports the RemoteFX 3D video adapter.

10742

The specified maximum monitor resolution %MonitorResolution; is either not valid or is not supported.

Specify a valid monitor resolution, and then try the operation again .

10743

To configure Microsoft RemoteFX 3D video adapter settings, the host CPU must support Second-Level Address Translation (SLAT).

For a Hyper-V virtual machine, either configure the video adapter se tting on the virtual machine to use the standard video adapter or place the virtual machine on a host with a CPU that supports SLAT.

Command Line Interface: For a Hyper-V virtual machine, either disable the RemoteFX 3D video adapter or place the virtual machine on a host with a CPU that supports SLAT.

10744

To configure Microsoft RemoteFX 3D video adapter settings, the host must have at least one RemoteFX-compatible graphics processing unit (GPU).

For a Hyper-V virtual machine, either configure the video adapter setting on the virtual machine to use the standard video adapter or place the virtual machine on a host with a RemoteFX-compatible GPU.

Command Line Interface: For a Hyper-V virtual machine, either disable the RemoteFX 3D video adapter or place the virtual machine on a host with a RemoteFX-compatible GPU.

10745

VMConfiguration has incorrect source disk (%Name;) specified.

Ensure that a resource group is attached to the template's virtual disk drive.

10746

A capability profile (%Name;) was already added to the hardware profile (%HWProfi leName;).

Remove AddCapabilityProfile parameter, then try operation again

10747

The capability profile (%Name;) is not associated with the hardware profile (%HWP rofileName;).

Remove RemoveCapabilityProfile parameter, then try operation again

10800

Unable to import %FileName; because of a syntax error in the file.

10801

Unable to import virtual hard disk %FileName; because one of its data files, %Par entFileName;, could not be imported.

10802

Unable to import %FileName; because of a syntax error in the file.

10803

Unable to refresh %FileName; because the file is in use by another process.

Wait for the next automatic library refresh, or manually refresh the library share after the process completes.

10804

Unable to import %FileName; because of a syntax error in the file.

10805

Unable to index hard disk %WsvObjectId; from the file %FileName; because the disk is a pass-through disk.

10806

Unable to import %ParentFileName; because one of its dependent files, %FileName;, is already being managed as a standalone %ObjectType; by VMM.

10807

The %ObjectType; %FileName; was not attached to %ObjectType2; %ObjectName; becaus e %FileName; is already being managed as a standalone %ObjectType; by VMM.

10808

The %ObjectType; %FileName; was not attached to %ObjectType2; %ObjectName; becaus e %FileName; could not be found.

10809

The %ObjectType; %FileName; was not attached to %ObjectType2; %ObjectName; becaus e of errors encountered while attempting to import %FileName;.

10810

Unable to import the %ObjectType; %FileName; due to errors encountered while attempting to import the file.

10811

The VMM management server was unable to impersonate the supplied credentials.

Add the library server without adding any library shares. Once that task has completed successfully add the library shares.

Command Line Interface: The VMM management server must run as the Local System account to ensure that it can impersonate other users.

10812

The %ObjectType; configuration file %FileName; was not imported because %FileName 2; could not be found.