Share via

Command-Line Interface Error Messages

  • Article

Applies To: Virtual Machine Manager 2008, Virtual Machine Manager 2008 R2 SP1

Did you know that System Center 2012 is available? System Center 2012 offers you a single, flexible platform to manage traditional datacenters, private and public clouds, and client computers and devices. Learn more about System Center 2012.

The following table contains error messages that you might encounter when using the Windows PowerShell – Virtual Machine Manager command shell.

Error Messages

Code Message Recommended Action

261

The parameter %InputParameterTag; is missing.

Select a value for the parameter.

400

The server %ComputerName; is already associated with this Virtual Machine Manager server.

Check the remote server name, and try the operation again.

401

Virtual machine host %ComputerName; is not associated with this Virtual Machine Manager server.

Check the virtual machine host name and then try the operation again.

402

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

Check the library server name, and try the operation again.

403

%ComputerName; is not a valid network computer name.

Only fully qualified domain names and NETBIOS computer names are valid. An IP address is valid only for hosts on a perimeter network, ESX hosts, and hosts joined to the domain by using an IPv6 address. Check the computer name, and try the operation again.

404

%ComputerName; cannot resolve with DNS.

Ensure there is network communication with the DNS server. If the problem persists, contact your network administrator.

405

The credentials provided do not indicate a valid domain user account.

1. Verify that the correct user name, a valid password, and the correct domain are entered and then try the operation again.\n2. Verify that the domain controller is operational and responding.

406

Access has been denied while contacting the server %ComputerName;.

1. Verify that the specified user account has administrative privileges on %ComputerName;.\n2. Verify that DCOM access, launch, and activation permissions are enabled on %ComputerName; for the Administrators group. Use dcomcnfg.exe to modify permissions, and then try the operation again.

407

The agent operation with server %ComputerName; was not successful.

Try the operation again. If the problem persists, ensure that the VMM server is able to communicate with the managed computer.

408

%ComputerName; has an unsupported version of the Virtual Machine Manager agent installed.

Uninstall the Virtual Machine Manager agent using Add or Remove Programs on %ComputerName;, and then try the operation again.

409

%ComputerName; is already associated with a different Virtual Machine Manager server. A computer can only be associated with one Virtual Machine Manager server at a time.

Remove the association of %ComputerName; from its current Virtual Machine Manager server or uninstall the Virtual Machine Manager agent using Add or Remove Programs on %ComputerName; and try the operation again.

410

Agent installation failed on %ComputerName;.

Try the operation again. If the problem persists, install the agent locally and then add the managed computer.

411

Agent installation failed because an installation is already in progress on server %ComputerName;.

Wait for the installation to complete, and then try the operation again.

412

SCVMM cannot configure Virtual Machine Remote Client (VMRC) on host server %ComputerName;.

Try the operation again.

413

The files needed to install agent, version %SoftwareVersion;, are missing from the Virtual Machine Manager server %ServerName;.

Reinstall the missing files by running Virtual Machine Manager Server Setup.

414

Agent installation could not access the ADMIN$ share on server %ComputerName;.

1. Verify that the selected user account has administrative privileges on %ComputerName;.\n2. Verify the permissions on the ADMIN$ share of %ComputerName;. The ADMIN$ share must allow write access to the Administrator group.\n3. Verify that the system time on the Virtual Machine Manager server and the server %ComputerName; is synchronized with the system time on the domain controller.

415

Agent installation failed copying %SourceLocation; to %InstallLocation;.

1. Ensure %ComputerName; is online and not blocked by a firewall.\n2. Ensure that there is sufficient free space on the system volume.\n3. Verify that the ADMIN$ share on %ComputerName; exists. If the ADMIN$ share does not exist, reboot %ComputerName; and then try the operation again.

416

Agent installation timed out while waiting on service %ServiceName; on %ComputerName;.

Ensure that the Windows Installer service is running on %ComputerName; and try the operation again.

417

There is a Virtual Machine Manager agent that is not responding or not compatible on %ComputerName;.

Uninstall the existing agent and then try the operation again.

418

Agent installation failed on %ComputerName; because WS-Management is not installed or it is disabled.

Ensure that the Windows Remote Management service is enabled and running on the server %ComputerName;. If necessary, install the WinRM component from https://go.microsoft.com/fwlink/? LinkId="84599". For more information, see the installation instructions in the VMM Planning and Deployment Guide.

419

Agent uninstallation failed on %ComputerName; because Agent is not installed.

Verify that Agent is installed on the computer.

420

Agent installation failed on %ComputerName; because of an incompatible operating system version.

Verify that %ComputerName; is running either Windows Server 2003 SP2 or Windows Server 2003 R2 operating system.

421

Agent installation failed on %ComputerName; because of a WS-Management configuration error.

In the Local Group Policy Editor (gpedit.msc), navigate to Computer Configuration\Administrative Templates\Windows Components\Windows Remote Management (WinRM), and then ensure that there are no policy settings configured for WinRM Client or WinRM Service.

422

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

Check the machine name, and then try the operation again.

423

Source machine is not associated with this Virtual Machine Manager server.

Check the source machine name, and then try the operation again.

424

The file %FileName; that the parameter -%Parameter; points to was not found.

Ensure that the required file exists and is accessible.

425

VMM was unable to import the user credentials from the security file.

Ensure that the security file is valid and the key used for encrypting the security file is correct, and then try the operation again.

426

The agent is not responding on the perimeter network machine %ComputerName; because either the agent is not installed; or %ComputerName; is not accessible from Virtual Machine Manager server.

Verify that the agent is installed on the computer, %ComputerName; is accessible from the Virtual Machine Manager server, and then try the operation again.

427

Certificate path not specified during addition of host %ComputerName; on a perimeter network.

Specify the location of the certificate obtained during local agent install on the host.

428

The agent cannot be uninstalled remotely from %ComputerName; without specifying administrator privileges for the machine.

Specify the administrator privileges, and then try the operation again.

431

The servers in domain %FriendlyName; cannot be enumerated.

Check the name, and then try the operation again.

432

Virtual Server installation was not successful on %ComputerName;.

Verify that an incompatible version of Virtual Server is not already installed. If the error persists, restart %ComputerName;, and then try the operation again.

433

The files needed to install Virtual Server are missing from Virtual Machine Manager server %ServerName;.

To install the missing files, run Virtual Machine Manager Server Setup again.

437

Service %ServiceName; could not be stopped on %ComputerName;.

Stop the service locally in the Services MMC snapin by running services.msc on %ComputerName;, choose the service %ServiceName;, right-click and then select Stop.

438

Service %ServiceName; is not present on %ComputerName;.

Check that the service exists in the Services MMC snapin on %ComputerName; by running services.msc.

439

VMM is unable to add the server %ComputerName; as a managed computer because the server is not listed in Active Directory Domain Services.

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

440

Virtual Machine Manager is unable to add the server %ComputerName; as a managed computer because the operating system is not supported. Managed computers must be running Windows Server 2003 SP2 or later.

Ensure that the host is running Windows Server 2003 SP2 or later. 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 add the host again.

441

Agent communication is blocked. On %ComputerName; the version of virtualization software or the VMM agent is unsupported.

Update the agent and virtualization software, and then try the operation again.

444

%ComputerName; is a Virtual Machine Manager server. A Virtual Machine Manager server cannot be associated with another Virtual Machine Manager server.

Uninstall the Virtual Machine Manager server from %ComputerName; using Add or Remove Programs on %ComputerName; and try the operation again.

445

Service %ServiceName; could not be started on %ComputerName;.

Start the service locally in the Services MMC snapin by running services.msc on %ComputerName;, choose the service %ServiceName;, right-click and then select Start.

446

%ComputerName; is not a fully qualified domain name.

Ensure that %ComputerName; is a fully qualified domain name, and try the operation again.

447

Agent installation failed on %ComputerName; because the supported version of Windows Remote Management (WinRM) is not installed.

Download WinRM from https://go.microsoft.com/fwlink/? LinkId="84599".

448

The files needed to install Microsoft Core XML Services (MSXML) 6.0 are missing from Virtual Machine Manager server %ServerName;.

To install the missing files, run Virtual Machine Manager Server Setup again.

449

Microsoft Core XML Services (MSXML) 6.0 installation was not successful on %ComputerName;.

Verify that an incompatible version of MSXML is not already installed. If the error persists, restart %ComputerName;, and then try the operation again.

450

The specified host name %FriendlyName; does not match the name in the security file. The name in the security file is %ComputerName;.

Ensure that the host name is correct in the security file and try the operation again.

451

The Virtual Machine Remote Console (VMRC) certificate request could not be saved to %FileName;, since a file with that name already exists on the specified path.

Delete the existing file, or specify a different path.

452

Virtual Machine Remote Console (VMRC) certificate request could not be saved to %FileName;.

1. Ensure that you have sufficient permissions to create %FileName;. 2. Ensure that the specified path is valid. 3. Ensure that the path does not include an incorrect value for file name, directory name, or volume label syntax.

453

No Virtual Machine Remote Console (VMRC) certificate file %FileName; was found on the Virtual Machine Manager client.

Ensure that you typed the path name correctly and that a certificate file exists on the specified path. Then try the operation again.

454

Virtual Machine Remote Console (VMRC) certificate file %FileName; is not valid.

Ensure that the file is a valid certificate file, and then try the operation again.

458

The Virtual Machine Manager agent could not be removed from %ComputerName;.

Uninstall the Virtual Machine Manager agent using Add or Remove Programs on %ComputerName;.

459

Agent update failed on %ComputerName;.

Try the operation again. If the error persists, reboot %ComputerName; and then try the operation again.

460

The file %FileName; that the parameter -%Parameter; points to exceeds the maximum size of %MaxLimit; characters.

Ensure that the required file is valid and then try the operation again.

461

Virtual Server installation was not successful on %ComputerName; because of the error: %DetailedErrorMessage;

Verify that an incompatible version of Virtual Server is not already installed. If the error persists, restart %ComputerName;, and then try the operation again.

462

Microsoft Core XML Services (MSXML) 6.0 installation was not successful on %ComputerName; because of the error: %DetailedErrorMessage;

Verify that an incompatible version of MSXML is not already installed. If the error persists, restart %ComputerName;, and then try the operation again.

463

Agent installation failed on %ComputerName;.

Ensure that %ComputerName; has Windows Installer version 3.1 or later installed, and then try the operation again.

464

Virtual Server cannot be installed because the driver for mounting virtual hard disks (vhdstor) is present on %ComputerName;.

Restart %ComputerName; and then try to install Virtual Server again.

465

The virtual machine configuration could not be added to %ComputerName; because the configuration file %FileName; could not be parsed correctly. It may be damaged.

Ensure that the configuration file is valid and then try to register the virtual machine again.

466

System Center Virtual Machine Manager Workgroup Edition cannot manage more than five hosts.

To manage more than five hosts, you must upgrade System Center Virtual Manage Manager. For information about upgrading, go to https://go.microsoft.com/fwlink/? LinkId="117133"

467

System Center Virtual Machine Manager Workgroup Edition cannot manage more than five hosts.

Remove some of the hosts that you are trying to add and then try the operation again. To manage more than five hosts, you must upgrade System Center Virtual Manage Manager. For information about upgrading, go to https://go.microsoft.com/fwlink/? LinkId="117133".

468

The specified computer %ComputerName; is a Windows host cluster, which cannot be added if the domain of the host does not have a two-way trust relationship with the domain of the VMM server or if the host is on a perimeter network.

Add the cluster as a trusted domain host.

500

Could not retrieve configuration data from the virtual machine host %ComputerName;.

Verify that Windows Management Instrumentation, Windows Remote Management (WS-Management), virtualization software, and Virtual Machine Manager Agent services are running on %ComputerName;. Then try the operation again.

501

The virtual machine host %ComputerName; cannot be removed because one or more virtual machines are active on the virtual machine host.

Remove all virtual machines from virtual machine host %ComputerName; using Remove-VM, and then try the operation again.

502

The selected network adapter does not exist on the virtual machine host.

Verify that the adapter is in the list obtained by running Get-VMHostNetworkAdapter -VMHost (Get-VMHost -ComputerName %ComputerName;).

503

The specified virtual network %VirtualNetworkName; does not exist.

Run Get-VirtualNetwork and ensure that the virtual network is on the list.

504

The virtual network %FriendlyName; already exists on the virtual machine host.

Check the virtual network name, and then try the operation again.

505

Virtual Machine Manager was unable to create a new virtual network %FriendlyName;.

Check the virtual network name, and then try the operation again.

506

The virtual network name %VirtualNetworkName; contains a character that is not valid.

Check the virtual network name and then try the operation again. For a host that is running Virtual Server, a virtual network name cannot contain any of the following characters: *?:<>/|\"

521

The lease renewal time must be less than the lease rebinding time. Also, the lease rebinding time must be less than IP address lease time.

Enter a valid lease time, and then try the operation again.

522

The minimum value allowed for IP lease time is 60 seconds.

Enter a valid lease time, and then try the operation again.

523

The minimum value allowed for lease rebinding time is 45 seconds.

Enter a valid lease time, and then try the operation again.

524

The minimum value allowed for lease renewal time is 30 seconds.

Enter a valid lease time, and then try the operation again.

525

Agent installation failed on %ComputerName; because of an incompatible operating system version.

Ensure that %ComputerName; is running either Microsoft Windows XP or Windows Server 2003 operating system.

526

Host configuration failed on %ComputerName; because no virtual machine paths are specified.

Ensure that at least one virtual machine path is specified.

550

VMM cannot access registry key %RegistryKey;.

Verify that the registry key exists, and then try the operation again.

551

VMM cannot access registry key value %RegistryKeyValueName; under %RegistryKey;.

Verify that the registry key value exists, and then try the operation again.

552

The registry key syntax %RegistryKey; is incorrect.

Ensure that the key is not empty, contains only valid characters and is less than 255 characters.

553

The type or name syntax of the registry key value %RegistryKeyValueName; under %RegistryKey; is incorrect.

Ensure that the type of value name is correct; the name is not empty, contains only valid characters and is less than 255 characters.

554

Permissions have not been granted to access the registry key %RegistryKey;.

Verify permissions on this registry key, and then try the operation again.

555

The operation on the registry key %RegistryKey; was not successful. A system error occurred, such as deletion of the key, or an attempt to create a key in the LocalMachine root, or the nesting level exceeds 510.

Verify the registry key properties, and then try the operation again.

556

VMM cannot delete the registry key %RegistryKey;. The subkey does not specify a valid registry subkey, has child subkeys or deletion of a root hive has been attempted.

Verify that the registry key is present, and then try the operation again.

606

Virtual Machine Manager cannot locate the specified answer file %SourceSysprepInfFile;.

Ensure the specified answer file path is valid, and then try the operation again.

608

Virtual Machine Manager cannot write to the Sysprep.inf file.

Verify that there is sufficient disk space on the Virtual Machine Manager server, and then try the operation again.

609

Virtual Machine Manager cannot detect a heartbeat from the specified virtual machine. Either the virtual machine is not running or Virtual Machine Additions is not installed.

Verify the status of the virtual machine by connecting to it using Virtual Machine Remote Client (VMRC), and then try the operation again.

610

Virtual Machine Manager was unable to find a value for the required Sysprep parameter %SysPrepEntry;.

Add the missing Sysprep parameter either to the answer file or to the operating system configuration, and then try the operation again.

611

Virtual Machine Manager cannot create the folder %DirectoryPath;.

Ensure that you have specified a valid path, and then try the operation again.

612

Virtual Machine Manager cannot delete the folder %DirectoryPath;.

You need to delete the folder manually.

613

Virtual Machine Manager cannot delete the file %FileName;.

You need to delete the file manually.

616

Specify the location of the virtual machine by its path. You cannot use a UNC name.

Enter the location of the virtual machine by its path, and then try the operation again.

617

Virtual Machine Manager cannot find or cannot access the location %FolderPath; specified for the virtual machine.

Ensure that the path is valid, and then try the operation again.

619

The -ISO and -HostDrive parameters are mutually exclusive. You can specify a value for either the -ISO parameter or the -HostDrive parameter, but you cannot specify a value for both parameters in the same operation.

Review the command, and then try the operation again.

620

The DVD drive must be specified by the drive letter, followed by a colon.

Review the parameter, and then try the operation again.

621

The -VirtualFloppyDisk and -HostDrive parameters are mutually exclusive. You can specify a value for either the -VirtualFloppyDisk parameter or the -HostDrive parameter, but you cannot specify a value for both parameters in the same operation.

Review the command, and then try the operation again.

622

The floppy drive must be specified by the drive letter, followed by a colon.

Review the parameter, and then try the operation again.

623

When the value for the -PhysicalAddressType Static parameter is specified, a Media Access Control (MAC) address for the -PhysicalAddress parameter must also be specified.

Enter a MAC address for the missing parameter, and then try the operation again.

624

If the value for the -PhysicalAddressType Dynamic parameter is specified, you cannot specify a value for the -PhysicalAddress parameter.

Review the command, and then try the operation again.

625

The specified MAC address format is incorrect. The MAC address format is 00-00-00-00-00-00.

Enter a valid MAC address, and then try the operation again.

626

Channels are not available on the IDE bus for the addition of a new device.

If you are trying to add a virtual hard disk, add the disk to a SCSI bus, and then try the operation again.

627

An additional virtual hard disk (VHD) can be attached to only one virtual machine at a time. The VHD %FilePath; cannot be attached to the new virtual machine because it is already attached to the virtual machine %VMName;, which is located on the host %VMHostName;.

Specify an additional virtual hard disk that is not attached to any other virtual machine, and then try the operation again.

628

There are no available slots on the SCSI bus to add new devices.

The SCSI bus cannot support the addition of new devices.

629

The virtual machine must be stopped before a virtual hard disk can be added.

Stop the virtual machine, and then try the operation again.

630

The computer name must be a valid IP address or a name containing letters and numbers. The computer name cannot contain spaces or any of the following characters `~!@#$%%^&*()=+[]{}\|;:'",<>/? .

Specify a valid computer name, and then try the operation again.

631

The product identification number must use the format xxxxx-xxxxx-xxxxx-xxxxx-xxxxx.

Specify a valid product identification number, and then try the operation again.

632

The passwords you have entered do not match.

Enter the password again.

633

You must enter valid values for the domain name, domain user, and domain password entries to join a domain. One or more of the values you have entered for joining the domain are not valid.

Verify the values for the domain name, domain user, and domain password entries, and then try the operation again.

634

The workgroup name cannot contain more than 15 letters or numbers. The value you have entered is not valid.

To join a workgroup, enter a valid value for the workgroup name, and then try the operation again.

635

Virtual Machine Manager is unable to securely store the password information on this machine.

Ensure that the Microsoft Cryptographic Service has been installed on the Virtual Machine Manager server and try the operation again.

636

Virtual Machine Manager is unable to retrieve previously stored password information.

Either restore the key data from a previous backup or enter the information again.

637

Virtual Machine Manager is unable to find a value for one or more required Sysprep parameters, such as FullName, ComputerName, or ProductKey.

Ensure that all required values are specified, and then try the operation again.

638

Virtual Machine Manager is unable to find a value for one or more required Sysprep parameters, such as FullName, ComputerName, or ProductKey.

Verify the values are specified in the Sysprep script, and then try the operation again.

639

Virtual Machine Manager does not support the specified processor type.

Select a supported processor, and then try the operation again.

640

The virtual machine must be in either the Poweroff or Stored state before SCVMM can perform the specified hardware changes.

Turn off the virtual machine or store it to the library, and then try the operation again.

641

VMM cannot perform the specified media change because the virtual machine is currently in an error, transitional, or a failed state.

Change the state, and then try the operation again.

642

The virtual machine must be turned off before Virtual Machine Manager can update the network configuration changes.

Turn off the virtual machine, and then try the operation again.

643

Unable to set virtual machine memory to %MemorySize; MB.

Ensure the virtual machine host has specified available memory, and then try the operation again.

644

The specified host drive %DriveName; does not exist on the host machine.

Modify the virtual DVD drive property to connect to an existing host drive.

645

The specified host drive %DriveName; does not exist on the host machine.

Modify the virtual floppy drive property to connect to an existing host drive.

646

Slots are not available on the network adapter’s bus for the addition of new devices.

The network bus cannot support the addition of new devices.

647

The time zone is not valid.

Refer to the Sysprep documentation for valid values for timezone, and then try the operation again.

658

The bus location for the object %FriendlyName; at (%BusType;, %Bus;, %Lun;) is not valid.

Ensure the bus location values are valid, and then try the operation again.

659

Another device is already at the location (%BusType;, %Bus;, %Lun;).

Select another destination for the disk, and then try the operation again.

660

LUN ID 7 is reserved for SCSI adapters and is not available for use.

Select another destination for the disk, and then try the operation again.

661

This operation cannot be completed because the virtual machine must be turned off.

Shutdown the virtual machine and try the operation again.

662

The library virtual hard disk does not support SCSI, IDE, bus or LUN switches.

Verify that you are using the correct command, and then try the operation again.

663

The -Name parameter cannot be empty or contain spaces for object %ObjectType;.

Provide a valid name for the object, and then try the operation again.

664

A virtual hard disk %FileName; cannot be attached to the same virtual machine or template more than once directly or via differencing disk.

Attachment of a virtual hard disk to a virtual machine or template multiple times is not supported.

665

The swap operation requires a disk to be connected to a virtual machine or template.

Verify that there is a valid connection, and then try the operation again.

666

To perform a swap operation both disks need to be connected to the same object.

Verify that both disks are connected to the same object, and then try the operation again.

667

The swap operation is not supported on virtual hard disks stored in the library.

Verify that the virtual hard disks are stored in a valid location, and then try the operation again.

668

A SCSI adapter does not exist on bus %Bus;.

Verify the contents of bus %Bus;, and then try the operation again.

669

The virtual machine must be run under a user account in order to use the -StartAction and -DelayStart parameters.

Use the -RunAsUserCredential to specify the user account, and then try the operation again.

670

The -RunAsUserCredential command requires a valid account and password.

Enter a valid account and password, and then try the operation again.

671

The -RunAsSystem and -RunAsUserCredential command cannot be specified at the same time.

Run each command separately.

672

The template being created should contain at least one virtual hard disk.

Specify at least one virtual hard disk, and then try the operation again.

673

The Boot.ini file is not on specified boot virtual hard disk that Sysprep need to be run on.

Specify a valid boot virtual hard disk, and then run Sysprep.

674

The Boot.ini file does not contain the value for the entry Section = %SysprepSection; Key = %SysprepKey;.

Specify a valid boot virtual hard disk, and then run Sysprep.

675

Unable to run Sysprep because the boot virtual hard disk does not contain any volumes.

Specify a valid boot virtual hard disk.

676

The Windows and System partitions are different. Sysprep is not supported.

Specify a virtual machine that has the same boot and windows partition, and then try the operation again.

677

This operating system %SoftwareVersion; is not supported when creating a template.

Select another virtual machine to create the template from, and then try the operation again.

678

Sysprep binary %FileName; does not exist for Windows version %SoftwareVersion; in Folder %FilePath;.

Add the missing Sysprep binaries for the specified Windows version in the specified folder, and then try the operation again.

680

Timeout occurred while waiting for Sysprep to finish processing on the virtual machine.

Ensure you are using the version of Sysprep binaries that match with virtual machine's Windows version, and then try the operation again.

682

A template cannot be created from virtual machine %VMName;.

Stop or shut down the virtual machine, and then try the operation again.

685

This job cannot be restarted until the virtual machine %VMName; is repaired.

Run Repair-VM to complete the job.

686

The version of Virtual Server on host %VMHostName; is not the supported VS R2 SP1 version.

The selected virtual machine cannot run sysprep. Upgrade Virtual Server, and then try the operation again.

687

Virtual machine %VMName; creation cannot restart. To restart a virtual machine must be in the Creation Failed or Customization Failed state.

Provide a valid virtual machine to restart the creation process.

688

To join a domain both parameters; -JoinDomain and -JoinDomainCredential must be specified.

Verify that both parameters are included, and then try the operation again.

689

The -JoinWorkgroup and -JoinDomain parameters cannot be used together.

Specify either -JoinWorkgroup or -JoinDomain parameters, and then try the operation again.

691

Virtual machine %VMName; cannot be cloned. A virtual machine must be in Poweroff or Stored state in order to be cloned.

Turn off the virtual machine or store it to the library, and then try the operation again.

692

Virtual Machine Manager cannot join %ObjectType; %FriendlyName; to the domain without a network adapter.

Add at least one network adapter to the virtual machine or template, and then try the operation again.

694

If you specify parameter -NoConnection, you cannot provide -VirtualNetwork.

Specify either -NoConnection or -VirtualNetwork parameter.

695

Either user credentials are required to perform this operation or virtual machine has to be set to run as system.

Either use the -RunAsUserCredential to specify the user account or -RunAsSystem to specify system account, and then try the operation again.

696

A virtual SCSI adapter can only be attached to Lun ID 6 or 7.

Review your command parameters and try the operation again.

697

Source template %FriendlyName; is not in a valid state.

Select a template in that is in a valid state.

698

An ISO %FileName; cannot be attached to the same virtual machine, template or hardware profile more than once.

Attach an ISO image to a virtual machine, template or hardware profile only once. Attachment of an ISO image to a virtual machine, template or hardware profile via multiple DVD drives is not supported.

706

Sysprep failed for virtual machine %VMName;.

Try the operation again.

707

Cannot dismiss sysprep failure for virtual machine %VMName; as virtual machine is not recoverable.

Retry sysprep or remove virtual machine.

708

Can only convert virtual hard disks belonging to a virtual Machine that is present on a virtual machine host.

Select a virtual hard disk attached to a virtual machine on the host, and then try the operation again.

709

Virtual hard disk conversion is supported only for virtual hard disks that are fixed or dynamically expanding.

Select a virtual hard disk that is either fixed or dynamically expanding, and then try the operation again.

711

SCVMM cannot change the name of the virtual machine because the virtual machine is not in either a Poweroff or Stored state.

Turn off the virtual machine or store it to the library, and then try the operation again.

712

A virtual machine must be in either the Poweroff, Saved, or Stored state to change the RunGuestCredential virtual machine property.

Turn off the virtual machine, save the virtual machine state, or store the virtual machine in the library, and then try the operation again.

713

SCVMM cannot modify StopAction property of the virtual machine because it is in either an unsupported, transitional, or a failed state.

If the virtual machine is in a transitional state, wait for the operation to complete, and then try the command again. If the virtual machine is in a failed or unsupported state, repair the failure, and then try the operation again.

714

SCVMM cannot modify the virtual machine because it is in either an unsupported, transitional, or a failed state.

If the virtual machine is in a transitional state, wait for the operation to complete, and then try the command again. If the virtual machine is in a failed or unsupported state, repair the failure, and then try the operation again.

715

The option %RepairOption; is not supported for repairing the virtual machine %VMName; in state %FromState;.

>Use an option supported by the state %FromState;, and then try the operation again.

716

CPUReserve value (%CPUReserve;) cannot be greater than CPUMax value (%CPUMax;).

Please review your parameters and run the command again.

717

The compact virtual hard disk %FileName; operation timed out after waiting for %VHDActionTimeoutInHours; hours.

Try the operation again.

718

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

Try the operation again.

719

The create virtual hard disk %FileName; operation timed out after waiting for %VHDActionTimeoutInHours; hours.

Try the operation again.

722

The virtual machine cannot be repaired because the last job that ran on the virtual machine is no longer available.

Repair the virtual machine, using the dismiss option if it is available. Otherwise, copy the files of the virtual machine to a new location and recreate the VM. To find the associated files, use the Get-VM cmdlet from the command line to retrieve the VM object. View the properties of the VM object to retrieve the location of the files.

723

Unable to restart the specified job. Only the most recent job that ran on the virtual machine %VMName; can be restarted.

Use the Repair VM action to repair the virtual machine.

728

The operation to expand virtual hard disk %FileName; timed out after %VHDActionTimeoutInHours; hours.

Retry the operation again.

729

The specified size for virtual hard disk %FileName; must be larger than its current size and less than the maximum size supported by Hyper-V.

Specify a valid size and then try the operation again.

730

Parameters cannot be specified for the guest operating system because the selected template was created as a non-customizable template (-NoCustomization parameter).

Please retry the operation without specifying guest operating system parameters.

733

File %FileName; was removed from Virtual Machine Manager, but it could not be deleted from host %VMHostName; because VMM does not have sufficient rights to delete this file.

If the file is no longer needed, manually delete it from the host.

735

Parameters cannot be specified for the guest operating system when creating a non-customizable template.

Review the command, and try the operation again.

800

VMM cannot find %FilePath;.

Ensure the path parameter value is valid, and then try the operation again.

801

VMM cannot find %ObjectType; object %FriendlyName;.

Ensure the library object is valid, and then try the operation again.

802

The %ObjectType; file %FilePath; is already in use by another %ObjectType;.

Wait for the object to become available, and then try the operation again.

803

Virtual machine %FriendlyName; already exists on the virtual machine host %VMHostName;

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

804

The template %FriendlyName; already exists.

Specify a unique name for the template, and then try the operation again.

807

The file location path must be a shared path.

Specify the shared path as \\servername\sharename, and then try the operation again.

808

VMM cannot access the specified file because access is denied. VMM must have the proper permissions to the file for access.

Change the file access permissions, and then try the operation again.

809

VMM cannot remove the virtual machine because it is in the %FromState; state.

Change the virtual machine's state, and then try the operation again.

811

VMM cannot add a virtual hard disk that is associated with a virtual machine.

Specify a virtual hard disk that is not associated with a virtual machine, and then try the operation again.

812

VMM cannot remove the disk because it is the parent of a differencing disk.

Remove all differencing disks associated with the parent disk, and then try the operation again.

813

The specified owner is not a valid Active Directory Domain Services account.

Specify a valid Active Directory Domain Services account, and then try the operation again.

814

Cannot remove virtual disk because a virtual machine is using this virtual disk.

To remove this virtual disk, remove this virtual disk object from the virtual machine using this virtual disk.

815

VMM cannot remove this library object because a virtual machine, template, hardware or guest operating system profile is using it.

To remove the library object, remove it from all virtual machines, templates, hardware and guest operating system profiles that are using it.

816

A valid name is required to complete this task.

Specify a valid name.

817

VMM cannot add %FileName; as %ObjectType;. The file extension of %FileName; does not match the supported file extensions for %ObjectType;.

Specify a file with a file extension that matches %ObjectType;, and then try the operation again.

818

VMM cannot find the library share.

Specify a valid library share, and then try the operation again.

819

Library share %FriendlyName; already exists.

Specify a unique library share name, and then try the operation again.

820

The path %SharePath; is not a share.

Specify a valid path for the share, and then try the operation again.

823

VMM cannot compact a virtual hard disk in the Library.

Compact the virtual hard disk on the virtual machine host instead.

824

VMM cannot link to this ISO because it is not a standalone ISO stored in a library.

Store the ISO image in the library or link to an ISO image in the library, and then try the operation again.

825

VMM cannot remove this library share since %ObjectType; %FriendlyName; is referenced in both this library share and another library share.

Remove %ObjectType; %FriendlyName; and then try the operation again.

826

Unable to add library share %SharePath; because the library share's local path, %FilePath;, is the parent or child folder of an existing library share.

Use an independent share, and then try the operation again.

827

Unable to perform this operation because the destination share, %SharePath;, either is not a library share in Virtual Machine Manager or is not present on library server %ServerName;.

Ensure the share path is on a library share on the specified library server, add the share to Virtual Machine Manager as a library share, or select a different library share.

828

The %ObjectType; "%FriendlyName;" already exists.

Specify a different name for the %ObjectType; being edited

834

The path %FileName; is not a registered share path on the library server %ComputerName;.

Specify a valid share path on %ComputerName;.

835

SCVMM does not have permissions to access the share %ShareName; on the library server %ComputerName;.

Ensure that both Local System and Virtual Machine Manager Servers groups have full access to the share on %ComputerName;.

842

VMM cannot expand a virtual hard disk in the Library.

Expand the virtual hard disk on the virtual machine host instead.

1201

Virtual machine %VMName; cannot be transferred. To be transferred, a virtual machine must be stopped, shut down, in a saved state or stored in the library. A virtual machine in a failed state cannot be transferred

Stop, shut down, or save the virtual machine. If the virtual machine is in a failed state, use "Repair virtual machine" to repair the virtual machine. Then try the operation again.

1202

You cannot migrate a virtual machine to the location where it currently resides.

Specify a new location to transfer the virtual machine, and then try the operation again.

1204

The server %VMHostName; does not contain any host bus adapter (HBA) ports. Fibre Channel SAN transfer cannot be used.

Transfer the virtual machine over the LAN.

1205

Virtual Machine Manager cannot transfer virtual machine %VMName; over the SAN because the host %VMHostName; does not have a Virtual Disk Service (VDS) hardware provider installed.

Instead, transfer the virtual machine over the LAN or install a VDS hardware provider on the host.

1206

A Virtual Disk Service (VDS) error occurred on server %VMHostName;.

Try the operation again.

1207

Virtual Machine Manager cannot transfer the virtual machine %VMName; over the SAN because the virtual machine resides on a volume that maps to a dynamic disk.

Transfer the virtual machine over the LAN, or see the Virtual Machine Manager Planning and Deployment Guide for information about using a SAN.

1208

Virtual Machine %VMName; is on a volume which maps to multiple disks. SAN transfer cannot be used.

Transfer the virtual machine over the LAN, or see the Virtual Machine Manager Planning and Deployment Guide for information about using a SAN.

1209

Virtual Machine %VMName; resides on a non SAN disk. SAN transfer cannot be used.

Transfer the virtual machine over the LAN, or see the Virtual Machine Manager Planning and Deployment Guide for information about using a SAN.

1210

The Virtual Machine %VMName; is placed on a SAN which does not support globally unique identifiers for LUNs. SAN transfer cannot be used.

Instead, transfer the virtual machine over the LAN.

1211

Unable to access Virtual Disk Service (VDS) 1.1 interface on server %VMHostName;.

To finish installing VDS 1.1, restart %VMHostName; to complete the installation.

1212

Virtual Machine %VMName; is placed on a basic disk which contains other volumes. SAN transfer cannot be used.

Instead, transfer the virtual machine over the LAN, or see Virtual Machine Manager Help for information about using a SAN.

1213

Unable to mount volume at %FolderPath; on server %VMHostName;.

Ensure that the path %FolderPath; exists and that the folder is empty. Ensure that another volume is not mounted at this path, and then try the operation again.

1214

Virtual Machine %VMName; resides on a LUN, which cannot be found.

Ensure that the LUN, which contains virtual machine %VMName;, is unmasked to virtual machine host %VMHostName;. Then try the operation again.

1215

An error has occurred while dismounting the volume at location %FolderPath;.

For more information, check the event log of the virtual machine host, and then try the operation again.

1216

The required version of Virtual Disk Service (VDS) is not installed on server %VMHostName;.

Install VDS 1.1 on the virtual machine host %VMHostName;, and then try the operation again.

1217

The files of virtual machine %VMName; reside on different LUNs. SAN transfer cannot be used.

Instead, transfer the virtual machine over the LAN, or see Virtual Machine Manager Help for information about using a SAN.

1219

The file system path %FolderPath; associated with virtual machine %VMName; is not valid.

Ensure the virtual machine %VMName; exists and the path %FolderPath; is valid, and then try the operation again.

1220

The file %FileName; was not transferred correctly.

Try the operation again.

1221

Virtual Machine %VMName; cannot be transferred over the SAN because it contains virtual disks that are shared with other virtual machines.

Verify that the virtual machine does not contain differencing disks that are shared with other virtual machines or transfer the virtual machine over the LAN.

1222

There is insufficient disk space on the volume %SystemVolumeDriveLetter; on server %VMHostName; to complete the transfer.

Free %BinaryDiskSpaceRequired; MB of disk space on the volume %SystemVolumeDriveLetter; on server %VMHostName; to transfer virtual machine %VMName; to %FolderPath;.

1223

Virtual machine %VMName; already exists on virtual machine host %VMHostName;.

Transfer virtual machine %VMName; to a different host, and then try the operation again.

1224

Virtual machine %VMName; cannot be transferred because it is associated with two files with identical names - %SourceFile1;, %SourceFile2;.

Disassociate one of the files from the virtual machine %VMName; or rename the file by performing the following steps: 1. Disassociate the file from the virtual machine 2. Rename the file 3. Associate the file with the virtual machine.

1227

The target location for a SAN transfer %FolderPath; cannot be on a FAT volume.

Specify a different target location on an NTFS volume, and then try the operation again.

1228

The server %VMHostName; cannot recognize the LUN that virtual machine %VMName; is placed on.

Check your Fibre Channel zoning policy to ensure that the server %VMHostName; can recognize the LUN virtual machine %VMName; is placed on. If you have recently changed your Fibre Channel configuration wait approximately 30 minutes and try the operation again. If server %VMHostName; is a virtual machine host you can manually refresh the properties by using the Refresh-VMHost cmdlet.

1229

The server %VMHostName; cannot recognize the LUN that virtual machine %VMName; is placed on.

Check your iSCSI configuration to Ensure that the server %VMHostName; can connect to the iSCSI target Virtual machine %VMName; is placed on. If you have recently changed your iSCSI configuration, wait approximately 30 minutes and try the operation again. If server %VMHostName; is a virtual machine host you can manually refresh the properties by using the Refresh-VMHost cmdlet.

1230

There are multiple virtual machines %NameList; on the LUN that virtual machine %VMName; is placed on. SAN transfer cannot be used.

Transfer the virtual machine over the LAN.

1231

The server %VMHostName; does not have the Microsoft iSCSI Initiator installed. iSCSI SAN transfer cannot be used.

Transfer the virtual machine over the LAN.

1232

An error occurred while logging off the iSCSI initiator on server %VMHostName; from target %IscsiTargetName;.

Check the event log of server %VMHostName; for more information. Verify that all open file handles on any of the disks of iSCSI target %IscsiTargetName; are closed, and try the operation again.

1233

The iSCSI initiator on server %VMHostName; is unable to log on to target %IscsiTargetName;.

For more information, check the event log of server %VMHostName;, and then try the operation again.

1234

The virtual machine %VMName; is exposed to a target which contains other LUNs. iSCSI transfer is not possible.

Transfer the virtual machine over the LAN.

1235

The iSCSI target %IscsiTargetName; is not visible to machine %VMHostName;.

Check your iSCSI configuration and then try the operation again.

1236

The iSCSI subsystem %FriendlyName; is not visible to machine %VMHostName;.

Check your iSCSI configuration and verify that iSCSI subsystem %FriendlyName; is visible to virtual machine host %VMHostName;, and then try the operation again.

1238

The virtual machine %VMName; cannot be transferred because it is located in a perimeter network.

Ensure that the selected virtual machine is not in a perimeter network, and then try the operation again.

1240

The file %FileName; is already present on server %VMHostName;.

Move the file %FileName; to a different location, and then try the operation again.

1242

The specified target path %SharePath; is not on a VMM library share on server %VMHostName;.

Specify a location that is on a library share, and then try the operation again.

1244

Virtual Machine %VMName; resides on a LUN, which is not visible to the Virtual Disk Service (VDS) hardware provider on machine %VMHostName;.

Ensure that the Virtual Disk Service (VDS) Hardware provider is installed and running on machine %VMHostName;. Then try the operation again.

1248

VMM cannot access the file or folder %FileName; because it is encrypted.

Remove the encryption from file or folder %FileName; and retry the operation.

1249

The server name specified in the target path %SharePath; does not match the fully qualified domain name of the selected VMM library server - %VMHostName;.

Specify the FQDN of the library server in the target path, and then try the operation again.

1250

Virtual Machine %VMName; cannot be transferred over the SAN because it contains an ISO - %FileName; that is shared with other virtual machines.

Ensure the virtual machine does not contain an ISO that is shared with other virtual machines, or transfer the virtual machine over the LAN.

1251

Virtual Machine %VMName; resides on a LUN, which does not have a volume on machine %VMHostName;.

If the LUN was recently moved, wait for the volume on the LUN to arrive and then try the operation again.

1252

The server %VMHostName; does not have an HBA which supports NPIV.

If server %VMHostName; contains an HBA that supports NPIV, ensure that the right version of firmware and driver are installed, or transfer the virtual machine over the LAN.

1253

NPIV transfer cannot be used because the server %VMHostName; does not have a Microsoft MPIO solution installed.

Transfer the virtual machine over the LAN.

1254

NPIV transfer cannot be used because the virtual machine %VMName; is not stored on a LUN that is unmasked to a Virtual Port.

Transfer the virtual machine over the LAN.

1255

An unknown error occurred performing an NPIV operation on server %VMHostName;.

Try the operation again.

1256

The physical port %PhysicalWWPN; on server %VMHostName; already has the maximum %MaxLimit; virtual ports.

Select a different server and try the operation again

1257

NPIV transfer cannot be used because the physical port %PhysicalWWPN; on server %VMHostName; is connected to a fabric that does not support NPIV.

Select a different server and try the operation again

1258

The creation of virtual port %VirtualWWPN; on server %VMHostName; failed due to lack of resources.

Ensure that server %VMHostName; has enough memory and try the operation again

1259

A virtual port with WWPN %VirtualWWPN; already exists on server %VMHostName;.

Select a different server and try the operation again.

1260

The format of the WWPN of virtual port %VirtualWWPN; is not valid.

Specify a valid WWPN and then try the operation again.

1261

An NPIV operation failed on server %VMHostName; because the SAN link is not operational.

Ensure that the server %VMHostName; is connected to the SAN and then try the operation again.

1262

The virtual port %VirtualWWPN; does not exist on server %VMHostName;.

Ensure that the virtual port %VirtualWWPN; exists on server %VMHostName; and then try the operation again.

1263

The format of the tag of the virtual port %VirtualWWPN; - %VirtualTag; is not valid.

Specify a valid tag and then try the operation again.

1264

The format of the symbolic name of the virtual port %VirtualWWPN; - %VirtualSymbolicName; is not valid.

Specify a valid symbolic name and then try the operation again.

1265

The format of the WWNN - %VirtualWWNN; of the virtual port %VirtualWWPN; is not valid.

Specify a valid WWNN and then try the operation again.

1266

The format of the WWPN of the physical port - %PhysicalWWPN; of virtual port %VirtualWWPN; is not valid.

Specify a valid WWPN and then try the operation again.

1267

The HBA %AdapterPNPInstanceName; was not found on server %VMHostName;.

Ensure that the adapter exists and then try the operation again.

1268

Virtual machine %VMName; could not be moved to virtual machine host %VMHostName; using this cluster configuration.

Check the cluster configuration and then try the operation again.

1269

Unable to move virtual machine %VMName; over LAN because pass-through disks are attached.

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

1270

%DetailedErrorMessage;

Try the operation again.

1271

%DetailedErrorMessage;

Try the operation again.

1272

Virtual machine %VMName; could not be moved to virtual machine host %VMHostName; because the target path was not specified.

Specify a valid target path and then try the operation again.

1273

Virtual machine %VMName; could not be moved because it has checkpoints.

Remove all of the checkpoints and then try the operation again.

1274

Saved Virtual machine %VMName; cannot be transferred over the SAN because it has pass-through disks.

Delete the saved state and then try the operation again.

1275

Virtual machine %VMName; could not be moved to Hyper-V host %VMHostName; because it has checkpoints.

Remove all of the checkpoints and then try the operation again.

1277

Virtual machine %VMName; cannot be transferred. Volume %SystemVolumeDriveLetter; on server %VMHostName; is unavailable for placement.

Select a volume that is available for placement.

1278

Virtual machine %VMName; cannot be moved to host %VMHostName;. The source and destination hosts have incompatible virtualization software.

Use a different destination host.

1279

Virtual machine %VMName; could not be moved because it has snapshot virtual hard disks.

Remove all of the checkpoints, merge the snapshot virtual hard disks (.avhd), and then try the operation again.

1281

%VMName; could not be migrated because it is a VMware template.

Select a virtual machine instead of a template and try the operation again.

1282

Virtual machine %VMName; could not be moved because it has checkpoints. Checkpoints are not supported for VMware virtual machines.

Remove all of the checkpoints and then try the operation again.

1283

VMM cannot transfer the virtual machine %VMName; over the SAN because this virtual machine is placed on multiple LUNs of different SAN types.

Ensure that virtual machine is placed on single type of SAN LUN or transfer the virtual machine over the LAN.

1284

Unable to migrate virtual machine %VMName; to host %VMHostName; over the SAN because SAN transfers between clustered and non-clustered hosts are not supported.

Transfer the virtual machine over the LAN.

1285

Virtual Machine Manager cannot perform hardware configuration changes on virtual machine %VMName; because it has snapshots or saved state. This functionality is not supported in the VMM library for Hyper-V virtual machines with saved state or snapshots.

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

1286

Virtual machine %VMName; on %VMHostName; could not be stored because it is in saved state.

Discard the saved state and then try the operation again.

1287

Virtual machine %VMName; on %VMHostName; could not be stored because it has multiple virtual hard disks with the same name %FileName;.

Rename the virtual hard disks to have unique names and then try the operation again.

1288

Virtual machine %VMName; cannot be migrated to or from VMware ESX Server host %VMHostName; because the host is in maintenance mode.

Retry the operation after the host is out of maintenance mode. To end maintenance mode, use VMware VirtualCenter.

1401

You do not have the permission required to perform this operation.

Contact the Virtual Machine Manager administrator to obtain the appropriate permissions.

1408

Cannot locate the user role because it no longer exists.

Close and reopen Windows PowerShell, and then try the operation again.

1410

The template %FriendlyName; has already been added to this user role.

Select a different template, and then try the operation again.

1417

Virtual Machine Manager cannot find a domain account for member %UserName;.

The user role member must have an Active Directory Domain Services account. Try the operation again with a valid domain account.

1600

VMM is unable to process one or more of the provided cmdlet parameters.

Type Get-Help %CmdletName; -full to view a list of defined parameters and complete descriptions. Then try the operation again.

1601

VMM is unable to connect to the Virtual Machine Manager server %ServerName; because the specified computer name could not be resolved.

Ensure that the computer name is correct, and then try the operation again. If the problem persists, contact your network administrator.

1602

Unable to connect to the Virtual Machine Manager server %ServerName;. The Virtual Machine Manager service on that server did not respond.

Verify that Virtual Machine Manager has been installed on the server and that the Virtual Machine Manager service is running. Then try to connect again. If the problem persists, restart the Virtual Machine Manager service.

1603

Unable to connect to the Virtual Machine Manager server %ServerName;. The attempt to connect timed out.

1) Verify that %ServerName; is online and can be accessed from your computer.\n2) If a firewall is enabled on %ServerName;, ensure that it is not blocking requests for TCP port %RemoteUIPort;.

1604

You cannot access Virtual Machine Manager server %ServerName;.

Contact the Virtual Machine Manager administrator to verify that your account is a member of a valid user role and then try the operation again.

1605

You cannot contact the Virtual Machine Manager server. The credentials provided have insufficient privileges on %ServerName;.

Ensure that your account has access to the Virtual Machine Manager server %ServerName;, and then try the operation again.

1606

Unable to connect to the Virtual Machine Manager server %ServerName; on port %RemoteUIPort;.

Verify that the server name and port number are correct.

1607

You cannot contact the Virtual Machine Manager server. The credentials provided have administrator privileges instead of Self-Service only privileges on %ServerName;.

Use the troubleshooting mode of the Self-Service portal, and then try the operation again.

1610

The connection to the Virtual Machine Manager server %ServerName; was lost.

Ensure that %ServerName; is online and that you can access the server remotely from your computer. Then connect to %ServerName; and try the command again using the new connection. Or, you can ensure that the Virtual Machine Manager service is started on %ServerName;. Then connect to %ServerName; and try the command again using the new connection. If the command fails again because of a connection failure, restart the Virtual Manager service and then try the operation again.

1611

Unable to retrieve the result of the job because the connection to the Virtual Machine Manager server %ServerName; was lost. The job will continue running on %ServerName; until it completes.

1) Verify that %ServerName; is online and can be remotely accessed from your computer.\n2) Verify that the Virtual Machine Manager service is started on %ServerName;. If the problem persists, restart the Virtual Machine Manager service.\n\nTo find out the result of the job, re-connect to the server, and run the following cmdlet:\nPS> Get-VMMServer %ServerName; | Get-Job | where { $_.ID -eq "%TaskID;"}

1615

VMM is unable to perform this operation without a connection to a Virtual Machine Manager server.

Use the Get-VMMServer cmdlet or the -VMMServer parameter to connect to a Virtual Machine Manager server. For more information, type at the command prompt: Get-Help Get-VMMServer -detailed.

1616

Unable to start VMMService because the VMM database has more than five hosts.

VMM Workgroup Edition can manage a maximum of five hosts. Uninstall the Virtual Machine Manager server using the "Remove data" option, or upgrade VMM Workgroup Edition to manage more than five hosts. Find information on upgrading at https://go.microsoft.com/fwlink/? LinkId="94662".

1617

Unable to log on by using the specified credentials.

Verify that the credentials specified are correct and then try logging on again.

1618

Unable to log on because a connection could not be established.

Contact the Virtual Machine Manager administrator to verify that the user account is still active and then try logging on again.

1619

Unable to log on because access was denied.

Contact the Virtual Machine Manager administrator to verify that the Self-Service Portal Web site is running under the NETWORK SERVICE identity and that no restrictions have been placed on this account that would prevent impersonation.

1700

The Virtual Machine Manager service on the %ServerName; server stopped while this job was running. This may have been caused by a system restart.

Restart the job by running the following command:\n\nPS> Restart-Job -Job (Get-VMMServer %ServerName; | Get-Job | where { $_.ID -eq "%TaskID;"})

1701

The job was stopped by the user %UserName;.

Restart the job by running the following command:\n\nPS> Restart-Job -Job (Get-VMMServer %ServerName; | Get-Job | where { $_.ID -eq "%TaskID;"})

1703

Unable to start the cmdlet %CmdletName; for JobGroup %TaskID;. One or more of the cmdlets is not valid for inclusion in that JobGroup.

For a description of the cmdlets in this type of JobGroup, see the help for cmdlet %CmdletName;.

1708

The %JobName; job cannot be restarted.

Wait for the object to be updated automatically by the next periodic %JobName; job.

1709

The %JobName; job cannot be canceled.

Wait for the job to finish.

1710

The %JobName; job requires alternate user credentials before it can be restarted.

Restart the job by supplying the credential parameter to the Restart-job cmdlet.

1730

The selected action could not be completed because the virtual machine is not in a state in which the action is valid.

Check the state of the virtual machine, and verify that the selected job can be run on a virtual machine in that state.

1732

The specified action could not be performed on virtual machine %VMName;. The request to change the state timed out.

Verify that the virtual machine is online, and then run the command again.

1733

Could not refresh virtual machine %VMName;.

Ensure that the virtual machine exists and that the WMI service is running on virtual machine host %VMHostName;, and then try the operation again.

1735

The virtual machines cannot be shut down because Virtual Guest Services is not installed on the guest operating system: %ObjectList;, or because the installed Virtual Guest Services does not support shutting down of the guest operating system that is running on the virtual machine.

To shut down, you must install Virtual Guest Services that support the shutting down of the guest operating system.

1737

The virtual machine %VMName; cannot be stored to a library server because its host is on a perimeter network.

Virtual machines cannot be transferred from hosts on perimeter networks because of security concerns. For more information about how to add a host in the perimeter network go to Virtual Machine Manager Help.

1738

The virtual machine %VMName; cannot be migrated to a different host because its current host is on a perimeter network.

Virtual machines cannot be transferred from hosts on perimeter networks because of security concerns. For more information about how to add a host in the perimeter network go to Virtual Machine Manager Help.

1749

The host group name contains a character that is not allowed (*?:<>/|\").

Specify a valid host group name.

1750

Unable to find the specified host group. The host group name may be incorrect, or the host group may have been moved or deleted.

Verify that the host group name is correct, that the host group exists on the Virtual Machine Manager server, and that the host group is in the specified host path.

1751

Unable to assign the name %VMHostName; to this host because this name is already in use.

Specify a unique name for the host, and then try the operation again.

1752

Unable to assign the host group the name %HostGroupName; in the specified path because another host group at the same level already has that name.

Specify a unique name or location for the host group, and then try the operation again.

1753

Unable to modify host group %HostGroupName; because the host group has been deleted.

To update the list of host groups, restart the Virtual Machine Manager service, or wait until the host groups list is automatically refreshed.

1755

Unable to delete host group %HostGroupName; because the host group is not empty. The host group may have hosts assigned to it, or hosts may be assigned to child host groups of this host group.

Remove all hosts from this host group and from any child host groups that the host group contains. Then retry this command.

1756

Unable to move a host group to itself.

Specify a different parent host group for the host group %HostGroupName;.

1757

Unable to move this host group to the %HostGroupName; host group because the specified host group is a child of this host group.

Choose a different host group to be the new parent of the %HostGroupName; host group.

1777

Virtual machine %VMName; cannot be cloned or migrated. To be cloned or migrated, a virtual machine must be stored in the library or turned off.

Stop or shut down the virtual machine, and then try the operation again.

1778

To be stored in the library, the virtual machine must be stopped or in a saved state.

Save state, stop or shut down the virtual machine, and then try the operation again.

2200

Could not find the specified virtual machine checkpoint.

Ensure the specified virtual machine checkpoint exists and try the operation again.

2206

Virtual machine %VMName; cannot be used for any checkpoint actions. For checkpoint actions, a virtual machine must be running, stopped, paused or in a saved state.

Ensure that the virtual machine is running, stopped, paused or in a saved state, and then try the command again.

2207

A new checkpoint for virtual machine %VMName; cannot be created because it exceeds the maximum of %Count; checkpoints allowed.

To create a new checkpoint for virtual machine %VMName;, remove an older checkpoint.

2208

The Virtual Machine Manager database %DatabaseName; could not be backed up at %FolderPath;.

Ensure that the specified folder exists, is not a root directory and is accessible to the SQL server.

2209

Failed to recover database %DatabaseName; from location %FileName; to SQL server. The SQL error is:\n%DetailedErrorMessage;

Ensure that the specified file is a valid VMM database backup.

2210

The path %FileName; specified for Virtual Machine Manager database backup file is not valid.

Ensure that the specified path is valid and that the Virtual Machine Manager database backup file exists on that path.

2211

An error has occurred while trying to remove all connections to database %DatabaseName;.

Ensure that the SQL Server service can be started and that you have permissions to query the SQL Server.

2212

The command is not valid.

Check the specified parameters and try the command again.

2213

There are no virtual hard disks attached to %VMName;.

To create a checkpoint, add a virtual hard disk to the virtual machine, and then try the operation again.

2214

Checkpoint actions on virtual machine %VMName; are unsupported because one or more hard disks are shared with other virtual machines. The shared hard disks are: %ObjectList;.

Ensure that the virtual machine doesn't share any hard disks with other virtual machines.

2216

Checkpoint creation on virtual machine %VMName; is unsupported because the virtual machine contains virtual hard disk %FileName;, and the path length of the checkpoint disk for this hard disk will exceed %MaxLimit; characters.

Transfer the virtual machine to a location where the path is shorter, or reduce the length of the virtual hard disk's filename and try the operation again.

2217

Checkpoint actions can be performed only for virtual machines that are on a host. Virtual machine %VMName; is in the library.

Place the virtual machine on a host and then try the operation again.

2219

A new checkpoint cannot be created for virtual machine %VMName; because it is attached to one or more pass-through disks

Ensure that the virtual machine is not attached to any pass-through disks and then try the command again.

2221

A new checkpoint cannot be created for virtual machine %VMName;. The virtualization software on host %VMHostName; does not allow a new checkpoint to be created for a virtual machine that is paused.

Ensure that the virtual machine is running, stopped, or in a saved state and then try the operation again.

2222

A new checkpoint cannot be created for virtual machine %VMName;. The virtualization software on host %VMHostName; does not allow a checkpoint name that exceeds %MaxLength; characters.

Specify a shorter checkpoint name and try the operation again.

2223

A new checkpoint cannot be created for virtual machine %VMName; on host %VMHostName; because virtual machine %VMName; has one or more virtual hard disks attached to a shared SCSI adapter.

Ensure that virtual machine does not have any virtual hard disks attached to shared SCSI adapters and then try the operation again.

2401

The specified path is not a valid share path on %ComputerName;.

Specify a valid share path on %ComputerName; to the virtual machine to be saved, and then try the operation again.

2406

VMM is unable to add host %ComputerName;.

1) Verify that the server name and the domain name are correct.\n2) Verify that the host is running Windows Server 2003 SP2 or a later version. If the operating system was updated recently, Active Directory Domain Services updates may still be pending. In that case, wait until Active Directory Domain Services updates run, and then add the host again. The update interval is determined by the Active Directory replication policy for the domain.

2411

Virtual Machine Manager is unable to find host %ComputerName;. The specified computer name contains characters that are not valid.

Verify that computer name does not contain * / \ ( or ), and then try the operation again.

2412

Virtual hard disks assigned to the IDE channel cannot be bigger than 127 GB.

If a larger drive is required, use the SCSI bus, and then try the operation again.

2600

Unable to connect to the database because of a fatal database error. It is unlikely that the database itself has been damaged.

Review the event log and take appropriate action. Ensure that SQL Server is running.

2601

Unable to connect to the VMM database.

Ensure that the SQL Server is running and configured correctly.

2602

Database integrity is in question because of a hardware or software problem.

Contact an experienced SQL administrator whenever this error occurs. Look at Windows Event Log for troubleshooting. Run DBCC CHECKDB to determine the extent of the damage. It is possible that the problem is in the cache only and not on the disk itself. If so, restarting SQL Server corrects the problem. Otherwise, use DBCC to repair the problem. In some cases, it may be necessary to restore the VMM database.

2603

Unable to connect to the VMM database because the database is in an inconsistent state.

Contact an experienced SQL administrator whenever this error occurs. In some cases, it may be necessary to restore the VMM database. If the problem persists, contact Microsoft Help and Support.

2604

Database operation failed.

Ensure that the SQL Server is running and configured correctly, and try the operation again.

2605

Unable to connect to the VMM database because of a general database failure.

Ensure that the SQL Server is running and configured correctly, then try the operation again.

2606

Unable to perform the job because one or more of the selected objects are locked by another job.

Either cancel those running jobs, or wait for them to complete, before trying this action again.

2818

The virtual machine name contains a character that is not allowed (*?:<>/|\").

Specify a valid virtual machine name.

2838

An unknown error occurred attempting to access a virtual hard disk image %FileName; on the %ServerName; server.

Ensure the file %FileName; is actually a virtual hard disk image.

2839

The virtual hard disk image %FileName; is not valid on the %ServerName; server.

Ensure that the file has the ".vhd" virtual hard disk image extension and that the file is actually a virtual hard disk image. If you are attaching it to an IDE bus, the maximum disk size is 127GB.

2845

A virtual network with the given ID could not be found on the %ServerName; server. This virtual network might be required as part of another object.

Ensure that the virtual network has not been removed or deleted, and then try the operation again.

2871

The value provided for the MAC address is not valid or is an incorrectly formatted address for the VM %VMName; on the %ServerName; server.

Enter a valid unicast MAC address in the format xx-xx-xx-xx-xx-xx.

2890

VMM cannot complete the Virtual Server operation on the %ServerName; server.

Check the Windows Event Log on the %ServerName; server to determine the cause of the error and make corrections. Then try the operation again.

2891

VMM cannot complete the Virtual Server operation on the %ServerName; server because of the error: %VMAsyncTaskErrorMessage;

Resolve the issue in Virtual Server and then try the operation again.

2900

An internal error has occurred.

Restart the agent on the machine %ServerName;, and then try the operation again.

2901

The operation did not complete successfully because of a parameter or call sequence that is not valid.

Ensure that the parameters are valid, and then try the operation again.

2902

There is not enough space on the disk to create %FileName; on the %ServerName; server.

Create additional disk space on the volume containing %FileName;, and then try the operation again.

2903

VMM could not locate the specified file %FileName; on the %ServerName; server. This file might be required as part of another object.

Ensure that you have specified a valid path parameter, and that all necessary files are present. Try the operation again.

2904

VMM could not find the specified path %FileName; on the %ServerName; server.

Ensure that you have specified a valid file name parameter, and then try the operation again.

2905

The file name, folder name, or volume label syntax %FileName; is incorrect on the %ServerName; server.

Ensure that the path name does not contain the characters (\ / : * ? " < > | ), and then try the operation again.

2906

The specified path %FileName; is not valid on the %ServerName; server.

Ensure that you have specified a valid path, and then try the operation again.

2907

The file name of file %FileName; exceeds the maximum path length of 260 characters on %ServerName;.

Specify a valid path, and then try the operation again.

2908

The file %FileName; cannot be accessed because it is in use by another process on the %ServerName; server.

Wait until the other process is completed, and then try the operation again.

2909

VMM cannot create the file %FileName; because the file name already exists on the %ServerName; server.

Specify a unique file name, and then try the operation again.

2910

VMM does not have appropriate permissions to access the resource %FileName; on the %ServerName; server.

Ensure that Virtual Machine Manager has the appropriate rights to perform this action.

2911

Insufficient resources are available to complete this operation on the %ServerName; server.

Ensure that the virtual machine host has sufficient memory and disk space to perform this action. Try the operation again.

2912

An internal error has occurred trying to contact an agent on the %ServerName; server.

Ensure the agent is installed and running. Ensure the WS-Management service is installed and running, then restart the agent.

2913

A generic Virtual Server exception has occurred on the %ServerName; server.

Try the operation again.

2914

The connection to the %ServerName; server cannot be established.

Ensure the server is up and running along with the virtualization service.

2915

The WS-Management service cannot process the request. Object not found on the %ServerName; server.

Ensure that the agent is installed and running. If the error persists, reboot %ServerName; and then try the operation again.

2916

VMM is unable to complete the request. The connection to the agent %ServerName; was lost.

Ensure that the WS-Management service and the agent are installed and running and that a firewall is not blocking HTTP traffic. If the error persists, reboot %ServerName; and then try the operation again.

2917

Virtual Machine Manager cannot process the request because an error occurred while authenticating %ServerName;. Possible causes are:\n1) The specified user name or password are not valid.\n2) The Service Principal Name (SPN) for the remote computer name and port does not exist.\n3) The client and remote computers are in different domains and there is not a two-way full trust between the two domains.

Log in by using an account on the same domain as the VMM server, or by using an account on a domain that has a two-way full trust with the domain of the VMM server, and then try the operation again. If this does not work, purge the Kerberos tickets on the VMM server by using kerbtray.exe, available at https://go.microsoft.com/fwlink/? LinkId="93709". Then, reset the SPN for %ServerName; by using setspn.exe available from https://go.microsoft.com/fwlink/? LinkId="93710". If this still does not fix the problem, make %ServerName; a member of a workgroup instead of a domain, restart the computer, rejoin the domain, and then try the operation again.

2918

The folder name %FileName; is not valid on the %ServerName; server.

Ensure that %FileName; is a valid folder name, and then try the operation again.

2919

The destination file %FileName; already exists or the destination device is not ready on the %ServerName; server.

Ensure that you have specified a valid path, delete the file if it exists, and then try the operation again.

2920

An I/O error occurred while opening the file %FileName; on the %ServerName; server.

Ensure that you have specified a valid path, delete the file if it exists, and then try the operation again.

2921

VMM cannot complete the operation on the file %FileName; on the %ServerName; server. One of the following system errors occurred: a file is read-only, the specified path is a directory, or Virtual Machine Manager does not have the required permissions.

Ensure that the path is valid and VMM has the appropriate rights to perform this action.

2922

VMM is unable to create a temporary file on the %ServerName; server. A unique temporary file name is not available.

Ensure that the system has enough resources and the appropriate rights to proceed, and then try the operation again.

2923

A malformed response was received trying to contact the agent on %ServerName; server.

Ensure the agent is installed and running. If the agent is running, restart the agent and verify that WS-Management is installed correctly.

2924

Unable to complete the request. Operation on the %ServerName; server timed out.

Try the operation again.

2925

The device used to access the specified path %FileName; is not ready on the %ServerName; server.

Insert the appropriate media into the available device or specify a different path, and then try the operation again.

2926

Logon failure. Unknown user name or bad password on the %ServerName; server.

Set a valid username and password and try the operation again.

2927

A Hardware Management error has occurred trying to contact server %ServerName;.

Check that WinRM is installed and running on server %ServerName;. For more information use the command "winrm helpmsg hresult".

2928

The specified logon credentials are not valid on the %ServerName; server.

Set a valid domain username and password and try the operation again.

2929

VMM could not resolve the specified file %FileName; on the %ServerName; server.

Ensure that you have specified a valid file name, then try the operation again.

2930

The network path %FileName; was not found on the %ServerName; server.

Ensure that the share name provided is valid and then try the operation again.

2940

VMM is unable to complete the requested file transfer. The connection to the HTTP server %BITSServerName; could not be established.

Ensure that the HTTP service and/or the agent on the machine %BITSServerName; are installed and running and that a firewall is not blocking HTTPS traffic.

2941

VMM is unable to complete the request. The connection to the agent on machine %ServerName; has been lost.

Ensure that the WS-Management service and the agent are installed and running and that a firewall is not blocking HTTP traffic.

2942

VMM is unable to complete the requested file transfer. The HTTP server %BITSServerName; returned access denied.

Ensure that the HTTP service and/or the agent on the machine %BITSServerName; are installed and running.

2943

VMM is unable to complete the requested operation because there are no logon servers available.

Ensure that the domain controller is up and running and that you have access to it.

2944

VMM is unable to complete the requested operation because the server name %ServerName; could not be resolved.

Try the operation again. If the problem persists, contact your network administrator.

2945

Unable to connect to the Virtual Server service on the server %ServerName;.

Ensure that the Virtual Server service and the Virtual Machine Manager Agent are installed and running on the server %ServerName;.

2946

A malformed response was received trying to contact server %ServerName; (%DetailedErrorMessage;).

Ensure that the communication is set up properly.

2947

Virtual Machine Manager cannot complete the VirtualCenter action on the server %ServerName; because of the following error: %DetailedErrorMessage;.

Resolve the issue and then try the operation again.

2948

Virtual Machine Manager cannot complete the VirtualCenter action on server %ServerName; because of the following error: %DetailedErrorMessage; (%Value;).

This error occurs when the key, name, or identifier for the element that you are trying to add already exists for an element in the collection. Provide unique values for those parameters and then try the operation again.

2949

Virtual Machine Manager cannot complete the VirtualCenter action on server %ServerName; because of the following error: %DetailedErrorMessage; (%Value;).

This error occurs when a function contains an invalid argument. Resolve the issue and then try the operation again.

2950

Virtual Machine Manager cannot complete the VirtualCenter action on server %ServerName; because of the following error: %DetailedErrorMessage;.

This error occurs when a referenced component of a managed object - either a data object type (such as a role or permission) or a primitive (such as a string) - cannot be found. Resolve the issue and then try the operation again.

2951

Virtual Machine Manager cannot complete the VirtualCenter action on server %ServerName; because of the following error: %DetailedErrorMessage; (%Value;).

This error occurs when an operation is denied access because of insufficient privileges on a managed object. Resolve the issue and then try the operation again.

2952

%FileName; cannot be created on server %ServerName; because the target volume is not set to "Available for placement."

Specify a different target volume or set the target volume to "Available for placement" and then try the operation again.

2953

VMware ESX Server host %ServerName; is not in the same VirtualCenter as host %VMHostName;.

Specify a different server and then try the operation again.

2971

The virtual machine %VMName; cannot be started because the run under credentials are not valid on the %ServerName; server.

Set the run under credentials for %VMName; to valid credentials and try the operation again.

2972

The credentials supplied for the virtual machine to run under are not valid.

Enter a valid account and password, and then try the operation again.

3100

VMM cannot open the specified VHD file %FileName; on the %ServerName; server.

Ensure that the file is present and accessible. Unmount the VHD file by using vhdmount.exe if the file is mounted. Try the operation again.

3101

VMM failed to mount VHD file %FileName; on the %ServerName; server. A timeout occurred.

Check Device Manager/System Devices to make sure that Microsoft Virtual Server Storage Bus is installed and functional. If it is not, install VHDMount component of Virtual Server. Restart Virtual Disk Service, and then try the operation again.

3102

VMM failed to mount VHD file %FileName; on the %ServerName; server. IOCTL Failed.

Check Device Manager/System Devices to make sure that Microsoft Virtual Server Storage Bus is installed and functional. If it is not, install VHDMount component of Virtual Server. Restart the Virtual Disk Service, and then try the operation again.

3103

VMM failed to find the SCSI address for mounted VHD file %FileName; on the %ServerName; server.

Check Device Manager/System Devices to make sure that Microsoft Virtual Server Storage Bus is installed and functional. If it is not, install VHDMount component of Virtual Server. Restart the Virtual Disk Service, and then try the operation again.

3105

VMM failed to load the vhdmount .dll file on the %ServerName; server.

Check Device Manager/System Devices to make sure that Microsoft Virtual Server Storage Bus is installed and functional. If it is not, install VHDMount component of Virtual Server.

3106

The VHD file %FileName; mount was canceled on the %ServerName; server.

Try the operation again.

3107

The format of the file %FileName; on the %ServerName; server is not compatible with the VHD format.

Ensure that the file is not corrupted, and try the operation again.

3108

The format of the file %FileName; on server %ServerName; is not recognized.

Ensure that the input .vmdk file is the .vmdk file that the .vmx file points to. \n\nThe .vmx file points to a .vmdk file that contains metadata. That .vmdk file in turn points to a binary .vmdk file. With the Copy-VMDK cmdlet, use the .vmdk file that contains the metadata. \n\nAdditionally make sure that both .vmdk files are not corrupted, and then try the operation again. If the problem persists, contact Microsoft Help and Support at https://go.microsoft.com/fwlink/? LinkId="45276".

3109

VMM is unable to create a snapshot set on %ComputerName;. The writer %VssWriterName; is in the failed state %VssWriterStatus;.

Try the operation again. If the problem happens again, disable the failing writer and/or the writer corresponding to this writer application for online physical-to-virtual handling.

3110

VMM is unable to create a snapshot set on %ComputerName;. An unexpected error occurred during the Volume Shadow Copy service operation.

Try the operation again.

3111

An unexpected error occurred on an attempt to contact Volume Shadow Copy service on %ComputerName;.

Verify that Volume Shadow Copy service is enabled, and try the operation again.

3112

VMM is unable to create a snapshot set on %ComputerName; because of a transient problem.

Check the recent records from the VolSnap source in the Application Event Log to determine the issue, and then try the operation again.

3113

VMM cannot create either the shadow copy storage file or other shadow copy data because there is not enough storage available on %ComputerName;.

Create sufficient space on disk to create the initial snapshot set and to record changes during the physical-to-virtual time. Try the operation again.

3114

VMM is unable to perform a snapshot set -related operation on %ComputerName;. This is a general failure in Volume Shadow Copy service.

1) Ensure that Volume Shadow Copy service is enabled on this computer. 2) Check recent records from the VolSnap source in the Application Event Log to determine the issue. 3) Try the operation again.

3115

The snapshot creation set on %ComputerName; was canceled.

Try the operation again.

3116

VMM is unable to create a snapshot set on %ComputerName;. A timeout occurred.

Try the operation again.

3117

If a value for the -DiskSizeAdd parameter is specified, a value for the -VolumeDeviceID parameter must also be specified.

Specify a value for the missing parameter -VolumeDeviceID or remove -DiskSizeAdd parameter, and then try the operation again.

3118

An intermediate job in a JobGroup must specify the value for the -VolumeDeviceID parameter.

Specify a value for the missing parameter -VolumeDeviceID or supply the -Trigger parameter to start operation of the JobGroup again.

3119

All binding parameters (-IDE or -SCSI, -Bus, -LUN) have to be specified as a set and accompany the -VolumeDeviceID parameter.

Specify a value for the missing parameters or remove binding parameters, and then try the operation again.

3120

The volume %VolumeDriveLetter; is not present on the %ServerName; computer.

Add a value to the -VolumeDeviceID parameter to specify a drive letter or name (in \\?\Volume{GUID}\ format) of a volume that exists on the source machine %ServerName;. If the configuration of the source machine changed, gather system information again by running the new-MachineConfig cmdlet.

3121

The destination location for the virtual hard disks (VHD) or for the Virtual Machine on the host has not been specified.

Specify the destination locations, and then try the operation again.

3122

All virtual hard disks on the same Virtual Machine should have the same owner assigned to them.

Specify the same value for the -Owner parameter for all jobs within the same JobGroup, and then try the operation again.

3123

The volume %VolumeDriveLetter; is already present in the selection of volumes.

Ensure there are no duplicate values and then try the operation again.

3124

The -IDE and -SCSI parameters are mutually exclusive.

Resolve the conflict, and then try the operation again.

3125

Parameters -Path and -Name are required for a standalone or a final job in a job group.

Specify the -Path and -Name parameters and try the operation again.

3126

Parameters -Name, -Description, -StartVM, -MemoryMB, -ProcessorCount, -ProcessorType, -RelativeWeight, -DriverPath, -RunAsSystem, -RunAsUserCredential, -StartAction, -StopAction, -DelayStart, -UseHardwareAssistedVirtualization can only be specified in a standalone or final JobGroup job.

Remove these parameters from the intermediate jobs and specify them on the final job.

3127

The job failed to configure %ComputerName; to restart in Windows PE.

Try the operation again.

3128

Unable to convert physical server. An internal agent error has occurred on %ComputerName;.

Ensure that the P2V agent is installed on %ComputerName; and that the P2V agent service is running, and then try the operation again.

3129

A timeout occurred while waiting on the agent service on %ComputerName; to respond.

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

3130

The specified driver path %FolderPath; is either not found or is not accessible.

Ensure that the path exists and Virtual Machine Manager server %ServerName; has read permissions to all the files under the specified path.

3131

The job failed to restart %ComputerName; (temporary computer name is %ServerName;) back into the original operating system. Automatic restart is scheduled to occur within 15 minutes.

If %ComputerName; does not restart in 15 minutes, manually restart it back into the original operating system using the boot menu.

3132

The job failed to copy %SourceLocation; to %InstallLocation;.

1. Ensure %ComputerName; is online and not blocked by a firewall.\n2. Ensure that there is sufficient free space on the system volume.\n3. Verify that the ADMIN$ share on %ComputerName; exists. If the ADMIN$ share does not exist, reboot %ComputerName; and then try the operation again.

3133

Virtual Machine Manager could not connect to source computer %ComputerName; after it restarted into Windows PE (temporary computer name is %ServerName;). Automatic restart to the original operating system is scheduled to occur within 15 minutes.

If %ComputerName; does not restart in 15 minutes, manually restart it back into the original operating system using the boot menu.

3134

An internal agent error has occurred on %ComputerName;.

Try the operation again.

3135

An error occurred while communicating with the agent on %ComputerName;.

Ensure %ComputerName; is online and not blocked by a firewall, and then try the operation again.

3136

An error occurred executing %FileName; on %ServerName;.

Try the operation again. If problem persists, reinstall the Windows Automated Installation Kit on %ServerName;.

3137

The driver installation file %FileName; cannot successfully install into the Windows PE image required for the physical-to-virtual conversion.

Remove %FileName;, and then try the operation again.

3138

The files needed to install the agent are missing from the Virtual Machine Manager server %ServerName;.

Run Setup again to install the missing files.

3139

Virtual Machine Manager could not connect to the physical-to-virtual source computer %ComputerName; after it restarted to its original operating system.

If %ComputerName; does not restart in 15 minutes, manually restart it back into the original operating system using the boot menu.

3142

Failed to fully clean up %ComputerName;.

Ensure that the correct boot loader is installed and remove all files named "$scvmm*.*" from the root directory of the boot volume on %ComputerName;, and then try the operation again.

3144

Unable to proceed because a SourceNetworkConnectionID is not specified. This parameter must have a value if a value is specified for any of the VirtualNetworkAdapter parameters.

Specify a value for the missing parameter -SourceNetworkConnectionID or remove any of the VirtualNetworkAdapter parameters and then try the operation again.

3145

The operating network adapter '%MACAddress;' is not found on the source machine %ServerName; or TCP/IP is not bound and enabled on this network adapter.

Add a value to the -SourceNetworkConnectionID parameter to specify the network connection name or the MAC address of a TCP/IP bound network adapter on source machine %ServerName;. If the configuration of the source machine changed, gather system information again by running the New-MachineConfig cmdlet.

3146

The parameter -Credential can only be specified in a standalone or final JobGroup job.

Remove this parameter from intermediate jobs, and specify it on the final job.

3147

The parameter -Credential must be specified on a standalone or final JobGroup job.

Specify a value for the missing parameter -Credential.

3148

The volume %VolumeDriveLetter; selected for physical-to-virtual imaging is not accessible from Windows PE. This is usually caused by missing or incorrect storage drivers. %ComputerName; may now need to be manually restarted into the original operating system using the boot menu.

Exclude this volume from conversion. Or, if you are performing offline physical-to-virtual conversions, create a new folder under %StaticDriverPath; on the VMM computer and then copy all of the storage or networks drivers to the new folder.

3149

The -Fixed and -Dynamic parameters are mutually exclusive.

Resolve the conflict, and then try the operation again.

3150

If a value for -Fixed or -Dynamic parameter is specified, a value for the -VolumeDeviceID parameter must also be specified.

Specify a value for the missing parameter -VolumeDeviceID or remove -Fixed or -Dynamic parameter, and then try the operation again.

3151

VMM failed to extend volume on the VHD file %FileName;. A timeout occurred.

Restart Virtual Disk Service, and then try the operation again.

3152

The network adapter '%MACAddress;' is already present in the selection of network adapters for conversion.

Ensure there are no duplicate values and then try the operation again.

3154

An internal error has occurred trying to contact an agent on the %ServerName; server.

Ensure the agent is installed and running. Ensure the WMI service is installed and running, then restart the agent.

3155

Cannot connect to the local WMI service.

Ensure the WMI service is installed and running on the Virtual Machine Manager server.

3156

The WMI service cannot process the request. Object not found on the %ServerName; server.

Ensure that the agent is installed and running. If the agent is installed, the WMI object may not have been found.

3157

VMM is unable to complete the request. The connection to the agent %ServerName; was lost.

Ensure that the computer %ServerName; exists on the network, WMI service and the agent are installed and running and that a firewall is not blocking HTTP and WMI traffic.

3158

VMM is unable to emulate the exact configuration of the source machine %ServerName;. The virtual machine memory could not be set to %MemorySize; MB because the current limit on virtual machine memory has been reached on the %VMHostName; host. The memory on the resulting virtual machine will be adjusted to the closest value within the valid range for this host.

Ensure the virtual machine host %VMHostName; has required available memory, and then change the memory on the resulting virtual machine to the desired value. Or, move the virtual machine to a host that has enough memory to start this virtual machine.

3159

The volume %VolumeDriveLetter; of source computer %ServerName; cannot be extended to the size of the resulting VHD due to a system error. The VHD is extended and will have unallocated space.

Consider expanding the volume after starting up the resulting Virtual Machine.

3160

The name of the source virtual machine is either outside of the valid range for a Virtual Machine name supported by Virtual Server or contains one of the following characters: (one of *?:<>/|\").

Override the source virtual machine name with a valid Virtual Server-based virtual machine name.

3200

The patch file %FileName; cannot be found.

Ensure that the patch file exists and is accessible by the machine account on the Virtual Machine Manager server. Then try the operation again.

3201

VMM could not copy the patch file %FileName; to temporary folder %FolderPath;.

Ensure that the file does not already exist in the temporary folder, then try the operation again.

3202

The patch file %FileName; format is not valid.

Specify a valid self-extractable executable file or a .cab file, and then try the operation again.

3203

Failed to extract patch file %FileName; to folder %FolderPath;.

1. Ensure that there is enough disk space on a system drive and the destination folder.\n2. Verify that the patch file is extractable, and then try the operation again.

3204

Failed to populate the cache at %FolderPath; because of an I\O error.

Ensure that the system has enough resources and the appropriate rights to proceed, and then try the operation again.

3205

No files were added to the patch cache.

Ensure that all patch files intended for import are in %FolderPath; on the Virtual Machine Manager server.

3206

Disk hardware or File System on volume %VolumeDriveLetter; is not supported by Volume Shadow Copy Service.

%ServerName; cannot be virtualized using an online conversion. Specify the -Offline parameter to perform an offline conversion.

3207

Cannot create a virtual machine for the x64 Windows operating system.

The selected machine %ServerName; cannot be virtualized. Virtual Server supports only 32-bit operating systems.

3208

Volume %VolumeDriveLetter; cannot be attached to IDE controller because the volume exceeds the maximum IDE disk size (%MaxLimit; GB) supported by virtualization software on host %VMHostName;.

The selected machine %ServerName; cannot be virtualized. Either assign this volume to a SCSI channel or exclude the volume from imaging, and then try the operation again.

3209

Volume %VolumeDriveLetter; cannot be attached to SCSI controller because the volume exceeds the maximum SCSI disk size (%MaxLimit; GB) supported by virtualization software on host %VMHostName;.

The selected machine %ServerName; cannot be virtualized. Exclude this volume from imaging, and then try the operation again.

3210

Boot and\or System volume %VolumeDriveLetter; was not selected or is not found on source machine %ServerName;.

Selected machine %ServerName; cannot be virtualized. Verify that the boot and system volumes are selected for migration. Then try the operation again.

3211

An older version of Virtual Server on host %VMHostName; has been detected and is not supported.

Selected machine %ServerName; cannot be virtualized on host %VMHostName;. Upgrade Virtual Server on the selected host to Virtual Server 2005 R2 SP1 or select a different host machine, and then try the operation again.

3212

VMM cannot find the latest version of file %FileName; that needs to be installed.

Selected machine %ServerName; cannot be virtualized. Contact Microsoft Help and Support for further assistance.

3213

VMM does not support the specific type of the system file %FileName; found on the source machine %ServerName;.

Selected machine %ServerName; cannot be virtualized. Contact Microsoft Help and Support for further assistance.

3214

Virtual Machine Manager cannot extract patch file %FileName; to folder %FolderPath;.

Verify that the physical disk contains enough space to accommodate the patch file, and then try the operation again.

3215

The source computer %ServerName; does not have enough memory to perform the offline physical-to-virtual conversion. %MemoryMinRequired;MB is required for this conversion.

Add additional physical memory to %ServerName; and try the operation again.

3216

Unable to convert %ServerName; because files that are required for the conversion are missing from the patch cache.

Download the update %FriendlyName; for %OSName; (%Language;, %OSPlatform;) from Windows Update to "%FolderPath;" on the Virtual Machine Manager server and then run the Add-Patch cmdlet.

3217

Unable to convert %ServerName; because required files to convert the source computer are missing.

Copy %FileName; to "%FolderPath;" on the Virtual Machine Manager server. The files are archived in %FileName;, which is located at %%WINDIR%%\Driver Cache\%OSPlatform; on %ServerName; or on the %OSName; (%Language;, %OSPlatform;) installation media. Run the Add-Patch cmdlet.

3218

NTFS boot volume %VolumeDriveLetter; is less than 4 GB in size. This configuration is not supported by Virtual Server.

Selected machine %ServerName; cannot be virtualized.

3219

Perimeter network host %VMHostName; cannot be used in physical-to-virtual or virtual-to-virtual conversions.

Specify a host located in a trusted domain, then try the operation again.

3220

%ServerName; cannot be converted. Boot volume %VolumeDriveLetter; must be attached as the first hard drive for the virtual machine to start up.

Modify the bus assignments to create space for the boot volume.

3221

The selected machine %ServerName; will be virtualized without CD\DVD drives. The channels are not available on the IDE bus for the addition of a DVD device to emulate the source machine configuration.

Modify the bus assignments or volume selection to create space on the IDE bus for the CD or DVD drive.

3222

The selected machine %ServerName; cannot be virtualized. The channels are not available on the IDE or SCSI buses for the addition of volume %VolumeDriveLetter;. Note that non-boot volumes always follow the boot volume during bus assignment.

Reduce the number of channels selected for migration volumes or change the bus assignment of the boot volume to fit volume %VolumeDriveLetter;.

3223

Boot volume %VolumeDriveLetter; must be attached to the IDE bus or SCSI bus 0 for the machine to boot up.

The selected machine %ServerName; cannot be virtualized. Modify the bus assignments for the boot volume which must be located on the first hard disk of the virtual machine, and then try the operation again.

3224

VMM is unable to locate the source computer %ComputerName; in Active Directory Domain Services.

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

3225

The Windows Automated Installation Kit is not installed.

Install Windows Automated Installation Kit version 1.0.0.0 on %ComputerName; and then try the operation again.

3226

Unable to run job group because an -Offline, -DriverPath, or -Shutdown parameter is specified on a job other than the final job. These parameters can only be specified in a standalone job or in the final job in a job group.

Remove these parameters from the intermediate jobs and specify them on the final job.

3227

Physical-to-virtual conversion failed because a -DriverPath or -Shutdown parameter was specified without specifying an -Offline parameter.

Specify a value for the missing parameter -Offline or remove -DriverPath, -Shutdown parameters to enable online physical-to-virtual conversion, and then try the operation again.

3229

Selected machine %ServerName; cannot be virtualized.

For more information, view details for this job.

3230

Unable to convert %ServerName; because required files are missing.

Download the update %FriendlyName; for %OSName; (%Language;, %OSPlatform;) from Windows Update (Support Link: %URL;) to "%FolderPath;" on the Virtual Machine Manager server and then run the Add-Patch cmdlet.

3232

A Virtual Disk Service (VDS) error occurred on the %ServerName; server.

Ensure that this service can be started on %ServerName; and check the Windows Event Log for troubleshooting information. Try the operation again.

3233

Failed to extract patch file %FileName;.

Verify that the patch file is extractable, and then try the operation again.

3234

Failed to copy file %SourceLocation; from source server %ComputerName; to folder %DestinationLocation; on the VMM server.

After resolving the problem, retry the operation or copy the files required for virtualization manually. Then use the add-patch cmdlet to populate the patch cache.

3235

Failed to extract patch file %FileName;. This patch applies to the operating system type or platform that is unsupported for virtualization.

Ensure that the patch file applies to 32-bit platform of an operating system that is supported for virtualization, and then try the operation again.

3236

Unable to convert %ServerName; because required files for the conversion are missing from the patch cache.

Download the update %FriendlyName; for %OSName; (%Language;, %OSPlatform;) from Windows Update to "%FolderPath;" on the Virtual Machine Manager server and then run the Add-Patch cmdlet.

3237

Unable to convert %ServerName; because required files are missing.

Copy %FileName; to "%FolderPath;" on the Virtual Machine Manager server. The files are archived in %FileName;, which is located on the %OSName; (%Language;, %OSPlatform;) installation media. And then run the Add-Patch cmdlet.

3238

Unable to convert %ServerName; because required files are missing.

Download the update %FriendlyName; for %OSName; (%Language;, %OSPlatform;) from Windows Update (Support Link: %URL;) to "%FolderPath;" on the Virtual Machine Manager server and then run the Add-Patch cmdlet.

3239

File %FileName; that is required to convert source computer %ServerName; is missing. The file might be located at %%WINDIR%%\Driver Cache\i386 on %ServerName;, or at i386\Uniproc directory on the %OSName; (%Language;) installation media.

Copy %FileName; to "%FolderPath;" on the Virtual Machine Manager server. Run the Add-Patch cmdlet.

3240

VMM discovered that a restart is pending after application of Microsoft updates on the source computer %ServerName;.

Restart source computer %ServerName; to enable conversion of this machine. Then try the operation again.

3241

The job cannot be restarted.

If a more recent conversion job of the source machine %ServerName; exists, restart that job instead. Otherwise, restart the conversion from the beginning.

3242

The converted virtual machine may not function correctly because it will not match the configuration of the source VMware virtual machine %FileName;.

Remove or supply a solution.

3243

Virtual Machine Manager is unable to update the operating system of the source VMware virtual machine %VMName;. The operating system, file system, or disk layout is not recognized.

The converted virtual machine may not start or operate correctly. For the list of supported Windows operating systems go to https://go.microsoft.com/fwlink/? LinkId="117761".

3244

Virtual machine %VMName; is not a valid virtual machine for V2V conversion.

Specify a valid virtual machine for V2V conversion and confirm that the virtual machine is shut down.

3402

The email address is not valid.

Ensure that the email address is correct.

3403

The reserve amount is not valid.

The percentage reserved must be between 0 and 100.

3404

The reserve amount is not valid.

The reserve amount must be greater than or equal to 0 and a valid integer.

3405

The event log for Virtual Machine Manager is missing or is not accessible.

Reinstall the Virtual Machine Manager to access the event log.

3406

The account %UserName; is not a domain account.

Enter a valid domain account name.

3407

The entered URL is not valid.

Enter a valid URL

3415

The -HostDrive and -AnyHostDrive parameters are mutually exclusive. You can specify a value for either the -AnyHostDrive parameter or the -HostDrive parameter, but you cannot specify a value for both parameters in the same operation.

Review the command and then try the operation again.

3453

Unable to verify the connection to the reporting server %ServerName;.

Ensure that System Center Virtual Machine Manager 2008 Management Pack and its reports are installed on the Operations Manager server. To download the management pack, go to https://go.microsoft.com/fwlink/? LinkID="85858".

3509

ID %ProcessorTypeGuid; is not found in the list of supported processors.

Ensure that the processor ID is valid and then try the operation again.

3513

Unable to set the value for %Parameter;. The sum of all elements exceeds the maximum length of %MaxLength;.

Choose a different value below the maximum length, and then try the operation again.

3514

Unable to connect to the Virtual Server service on the library server %ServerName;.

Ensure that the Virtual Server service is installed and running on the library server.

3516

The specified virtual network adapter configuration is not supported by the host virtualization software.

Update the virtual network adapter configuration and then try the operation again.

3518

The VLAN setting for one or more network adapters on virtual machine %VMName; is not compatible with the virtualization software on host %VMHostName;.

Ensure that virtual LAN identification is disabled for all network adapters listed in the hardware configuration of virtual machine %VMName; or specify a different host, and then try the operation again.

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.

10206

Setup requires Microsoft System Center Operations Manager SP1 to be installed.

Install Operations Manager 2007 SP1 and then run Setup again

10207

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

Specify a different VMM 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 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 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 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 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 https://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.

10218

Setup could not import the System Center Virtual Machine Manager 2008 Management Pack into Operations Manager 2007 because one or more required management packs are missing. The VMM 2008 Management Pack cannot be deployed unless the following component management packs are present in Operations Manager 2007:\nWindows Server Internet Information Services 2003\nWindows Server Internet Information Services 2008\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 2007:\n Microsoft Windows Server 2000/2003 Internet 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 https://go.microsoft.com/fwlink/? LinkId="86411"

10400

Before Virtual Machine Manager can add a host, the host must be restarted.

Restart %ComputerName; and then try adding the host again.

10401

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.

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.

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.

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.

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 from https://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 it meets the requirements. To download the tool as part of the Windows Logo Kit (WLK), go to https://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 https://go.microsoft.com/fwlink/? LinkID="120488". To download the latest update, go to https://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 https://go.microsoft.com/fwlink/? LinkId="120488" and then apply update 948515 from https://go.microsoft.com/fwlink/? LinkId="120407".

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.

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

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 the 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 network, 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 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 deployed on a host.

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

10611

Virtual Machine Manager does not support creation of highly available virtual machines 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 cluster %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 connected 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 Windows Vista.

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 specify 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 boot 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 operation again.

10628

Invalid memory size specified for virtual machine. The virtualization software on host %VMHostName; requires memory size to be a multiple of 4 MB.

Specify a memory size that is a multiple of 4 MB and then try the operation again.

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.

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 BIOS 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 Kit) 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 is connected to a virtual network switch that is not valid.

Ensure that 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 drive.

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

10651

Cannot create the template because source virtual machine %VMName; has checkpoints. \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 operation 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, VMware 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 not specified.

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

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 (-GuestOSProfile 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 checkpoints. 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.

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.

10670

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

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

10671

Hard disk file %FileName; is not compatible with the SCSI adapter on %VMName;.

Either specify a compatible hard disk file or convert hard disk file %FileName; by using the VMware VirtualCenter 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 location 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 operation 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.

10679

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

Manually delete resource %FileName; from the host.

10680

Disk %FileName; cannot be attached as a pass-through to 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 any other virtual machine, and then try the operation again.

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.

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 attached, and then try the operation again.

10688

Virtual hard disk %FileName; is of type .vmdk. VMM does not support 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 and 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.

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.

10811

The VMM server was unable to impersonate the supplied credentials.

The VMM server must run as the local system account to ensure that it can impersonate other users.

11020

Virtualization platform on host %VMHostName; doesn't allow boot and system volumes to be on a disk attached to SCSI adapter. Disk at the location (%BusType;, %Bus;, %Lun;) must be attached to the IDE bus for the machine to boot up and work properly.

Modify the bus assignments so that boot and system volume disks are located on IDE bus, and then try the operation again.

11021

Virtualization platform on host %VMHostName; doesn't support pass-though disks.

Remove pass-though disk from the VM or try different host

11022

The specified source virtual machine cannot be used to create a new virtual machine because the disk at location (%BusType;, %Bus;, %Lun;) is a pass-through disk and two virtual machines cannot share the same pass-through disk.

Specify a different virtual machine as the source, and then try the operation again.

11023

Host %VMHostName; doesn't have network adapter

Please select a different host and then try the operation again.

11024

The bus location for the disk at (%BusType;, %Bus;, %Lun;) is not valid on host %VMHostName; for one of the following reasons:\n1. The Bus exceeds the maximum number of SCSI adapters(%MaxBusCount;) supported by the virtualization software on host. \n2. The LUN exceeds the maximum number allowed (%MaxLunCount;) by the virtualization software on host.

Ensure that the bus location for the disk is valid, and then try the operation again.

11025

Host %VMHostName; is not available for placement.

Please select a different host and then try the operation again.

11026

Host %VMHostName; is not responding and is not available for placement.

Select a different host and then try the operation again.

11027

Clustered host %VMHostName; is not available for placement. For the host to be available for placement, the Cluster Service must be running on the host.

Select a different host and then try the operation again.

11028

Virtualization platform on host %VMHostName; does not support shared DVD ISO images.

Remove the shared ISO image from hardware profile or select a different host.

11029

The disk at the location (%BusType;, %Bus;, %Lun;) will be moved to the IDE bus. The virtualization platform on host %VMHostName; does not allow boot and system volumes to be on a disk attached to SCSI adapter.

Modify the bus assignments so that boot and system volume disks are located on IDE bus, and then try the operation again.

11030

Host %VMHostName; is not available for placement because it is in a state that has limited management functionality. To use an ESX Server host for placement, you must configure the security settings of the host to enable full management functionality.

Configure the security settings of host %VMHostName; to enable full management functionality and then try the operation again.

11031

Virtual machine %VMName; cannot be migrated from host %VMHostName; because the host is in a state that has limited management functionality. For hosts in the OK (Limited) state, a virtual machine can only be migrated within the same Virtual Center server.

Configure the security settings of host %VMHostName; to enable full management functionality, or select a target host within the same Virtual Center server, and then try the operation again.

11400

User role %FriendlyName; already exists.

Specify a different user role name and then try the operation again.

11402

Cannot remove member %UserName; because %UserName; is not a member of the specified user role.

Specify a different user role and then try the operation again.

11410

The user role no longer exists.

Close and reopen Windows PowerShell 1.0, and then try the operation again.

11411

Cannot use Set-VMMUserRole with an Administrator profile. There can be only one Administrator user role.

You can add or remove members to the Administrator user role, or delegate administration, by creating new Delegated Administrator user roles.

11415

The -ParentUserRole parameter is required for Set-VMMUserRole with a Delegated Administrator profile.

Select the ParentUserRole parameter for the new user role and then try the operation again.

11416

The -ParentUserRole specified must be a Delegated Administrator user role.

Select UserRole for the DelegatedAdmin profile as the ParentUserRole and then try the operation again.

11418

You do not have permission to access one or more of the objects required by this operation.

Contact the Virtual Machine Manager administrator to obtain the appropriate permissions.

11419

You do not have permission to modify this user role.

Contact the Virtual Machine Manager administrator to obtain the appropriate permissions.

11420

A connection cannot be established with the specified virtual machine.

Contact the Virtual Machine Manager administrator to verify that the user has access to this virtual machine and that the VirtualCenter host is running.

11421

There must be at least one member in the Administrator user role.

Attempt to remove users from the Administrator role again but leave at least one user in the role.

11422

The object used with the -AddScope or -RemoveScope parameter is not valid.

For the -AddScope or -RemoveScope parameters, only the following types of objects can be used: Template, HostGroup, or LibraryShare.

11425

The user role specified is not valid.

Valid values for the user profile are: Administrator, DelegatedAdmin or SelfServiceUser.

11428

The specified user role is not valid or no longer exists.

The SelfServiceUser value is the only valid value for -UserRole in this situation.

11429

The specified user role is not valid because owner %UserName; of this virtual machine is not a member of the specified user role.

Add %UserName; as a member of the specified user role or provide a different user role, and then try the operation again.

11430

Either the specified user role or the specified owner (%UserName;) for this virtual machine is not valid.

Either add %UserName; as a member of the user role and the try the operation again, specify a different user role for %UserName;, or specify a different owner.

11431

The user role specified cannot be applied to this virtual machine because no owner has been set for this virtual machine.

Set the user role again, specifying an owner who is a member of the user role.

11432

The specified parent user role is not a top-level user role.

Specify a top-level user role as the parent user role.

11433

This operation could not be completed because the virtual machine is not associated with any Self-Service user role.

Contact the Virtual Machine Manager administrator and have this virtual machine associated with a user role of which you are a member.

11436

The Virtual Machine Manager server could not validate user %UserName;.

Ensure that there is a two-way trust relationship between the domain of the VMM Server and the user's domain

11438

Virtual Machine Manager cannot add the library servers to the scope because the state of one or more of the library servers is not valid.

Ensure that all library servers you are adding to the scope are in the Responding state and then try the operation again.

11439

Virtual Machine Manager cannot add one or more objects to the scope of user role %UserRoleName; because the objects are not in the scope of the parent user role %FriendlyName;.

Ensure that all objects you are adding are in the scope of the parent user role and then try the operation again.

11440

The current session with the Self-Service Portal has been lost. This might have occurred by changing the browser's current internet zone for the Self-Service Portal without restarting the browser. This can also occur if the Web server has been reset.

Log on to the Self-Service Portal again. If this problem occurs frequently, contact your administrator.

11441

The connection to the Virtual Machine Management server for this session has been lost. The server may have been reset or is no longer available.

Confirm that scripting is enabled for your browser and log on to the Self-Service Portal again. If the problem persists contact your administrator.

11442

The current session with the Self-Service Portal has been lost. This can be caused by changing the current internet zone for the Self-Service Portal without restarting the browser or by directly browsing to a Self-Service Portal Webpage without first logging on to the site.

Log on to the Self-Service Portal again. If the problem persists, contact your administrator.

11443

Cannot attach the specified ISO to the virtual machine because user role %UserRoleName; associated with the virtual machine does not have access to the ISO.

Contact your VMM administrator to add the library share path for the ISO to user role %UserRoleName; or specify a different ISO and then try the operation again.

11444

Unable to add member %UserName; to the user role %UserRoleName;. Only domain users, security groups or computers can be user role members.

Select a valid user role member and try the operation again.

11445

Virtual Machine Manager could not place this virtual machine on host %VMHostName; because there are no volumes available for placement on this host.

Contact your VMM administrator to request at least one volume be made available for placement.

11446

Virtual Machine Manager could not place this virtual machine on host %VMHostName; because there are no default virtual machine paths on this host.

Contact your VMM administrator to request default virtual machine paths on this host or access to another host.

11447

Virtual Machine Manager could not place this virtual machine on host %VMHostName; because the host does not have any default virtual machine paths on volumes that are available for placement.

Contact your VMM administrator to request at least one default virtual machine path on a volume that is suitable and available for placement.

11448

Cannot create this virtual machine because the selected user role %UserRoleName; does not have create permissions.

Create a virtual machine from a user role which has permission or contact your administrator to gain the necessary permissions.

11449

Virtual Machine Manager could not place this virtual machine on host %VMHostName; because remote connections are not enabled on this Host.

Contact your VMM administrator to enabled remote connections on this host or request access to another host.

11601

Unable to move the host cluster %HostClusterName; to the specified path because another host cluster with the same name already exists at that level.

Specify a different location for the host cluster and then try the operation again.

11603

Unable to delete host group %HostGroupName; because the host group for VirtualCenter server %ServerName; is not empty. The host group may have hosts assigned to it, or hosts may be assigned to child host groups of this host group.

Remove all hosts from this host group and from any child host groups that the host group contains, and then try the operation again.

11604

Unable to delete host cluster %HostClusterName; because the host cluster in VirtualCenter server %ServerName; is not empty.

Remove all hosts from the host cluster and then try the operation again.

11606

The Virtual Machine Manager Administrator Console cannot connect to the specified Virtual Machine Manager server because the versions are not compatible.

Upgrade the Virtual Machine Manager client and then try the operation again.

11607

The Virtual Machine Manager Administrator Console cannot connect to the specified Virtual Machine Manager server because the versions are not compatible.

Upgrade the Virtual Machine Manager server and then try the operation again.

11608

The ID %TaskID; does not map to an existing VMM job.

Ensure that you typed the job ID correctly.

11800

Cannot implement PRO tip because it is not active.

To be implemented, a PRO tip must have Active status. Do not attempt to implement a PRO tip that is has %PROTipState; status.

11801

Cannot dismiss PRO tip because it has been implemented or implementation is in progress.

Do not attempt to dismiss a PRO tip that has %PROTipState; status.

11802

Unable to find the specified PRO tip.

Verify that the specified PRO tip has not been deleted.

11803

Unable to connect to the Operations Manager root server, %OperationsManagerServer;.

Ensure that the server exists and that System Center Operations Manager 2007 is installed and then try the operation again.

11804

The Virtual Machine Manager service does not have required credentials to access the Operations Manager SDK service on %OperationsManagerServer;.

Add the VMM service account as an Administrator on the Operations Manager server and then try the operation again.

11805

Unable to verify the connection to the Operations Manager root server, %OperationsManagerServer;.

Ensure that the server exists, that System Center Operations Manager 2007 is installed, that Virtual Machine Manager has the appropriate rights to perform this action, and then try the operation again.

11806

Discovery of PRO performance and usage data was terminated because the VMM 2008 Management Pack has not been imported into System Center Operations Manager 2007.

Ensure that VMM 2008 Management Pack is imported on the Operations Manager Server and then try the operation again.

11808

Unable to set the Operations Manager root server in VMM because the Operations Console for Operations Manager is not installed on the Virtual Machine Manager server.

Install the Operations Console for System Center Operations Manager 2007 on the Virtual Machine Manager server and then try the operation again.

11810

Unable to set %PROParameter; to the given value.

Enter a valid value for %PROParameter;. You can enter a number or a text string:\n\n Turn off PRO tips: "0" or "Off"\n Receive critical errors only: "1" or "CriticalOnly"\n Receive critical errors and warnings: "2" or "CriticalandWarning"

11811

Cannot implement PRO tip because no automatic recovery action is defined for the Operations Manager monitor that generated the tip.

Review knowledge for the PRO tip for recommended actions to resolve the issue.

11812

Cannot update PRO settings because the cmdlet includes invalid parameters.

To set PRO settings for a host group or a host cluster, you must set InheritPROSettings="False" and then set both the PRO monitoring level (PROMonitoringLevel parameter) and PRO automation level (PROAutomationLevel parameter). To inherit PRO settings from the parent host group, set InheritPROSettings="True".

11819

Unable to inherit PRO settings for the root host group.

Manually configure the PRO monitoring and automation settings.

11820

Cannot update PRO settings until the Operations Manager root server connection is configured.

Configure the Operations Manager root server connection using Set-VMMServer -OpsMgrServer.

11821

Operations Manager server cannot be specified because the VMM 2008 Management Pack has not been imported.

Use the Configure Operations Manager option of VMM Setup to import version %MPVersion; of the System Center Virtual Machine Manager 2008 Management Pack onto your Operations Manager server, and then retry the operation. It is recommended that you use Setup instead of downloading the management pack from the System Center Operations Manager 2007 Catalog to ensure that other required Operations Manager configuration tasks are completed.

11822

Operations Manager server cannot be specified because there is an incompatible VMM 2008 Management Pack on the Operations Manager server.

Use the Configure Operations Manager option of VMM Setup to import version %MPVersion; of the System Center Virtual Machine Manager 2008 Management Pack onto your Operations Manager server, and then retry the operation. It is recommended that you use Setup instead of downloading the management pack from the System Center Operations Manager 2007 Catalog to ensure that other required Operations Manager configuration tasks are completed.

11823

Discovery of one or more Virtual Machine Manager objects monitored by Operations Manager 2007 failed.

This might be caused by a missing or outdated version of the System Center Virtual Machine Manager 2008 Management Pack in Operations Manager 2007. To download version %MPVersion; of the management pack, open the System Center Operations Manager 2007 Catalog (https://go.microsoft.com/fwlink/? LinkId="86411").

11825

PRO tip implementation failed to start.

Ensure that the VMM Administrative Console is installed on the Operations Manager root management server and that the action account that Operations Manager uses has access to Virtual Machine Manager.

12409

%ComputerName; cannot be reached.

Verify network connectivity between the Virtual Machine Manager server and %ComputerName;. If the issue persists, contact your network administrator.

12421

The certificate file on the VMware VirtualCenter server is not valid.

Ensure that the file is a valid certificate file, and then try the operation again.

12700

VMM cannot complete the Hyper-V operation on the %ServerName; server because of the error: %VMAsyncTaskErrorMessage;

Resolve the issue in Hyper-V and then try the operation again.

12701

VMM cannot complete the VMware operation on the %ServerName; server because of the error: %VMAsyncTaskErrorMessage;

Resolve the issue in VMware and then try the operation again.

12702

Cannot bind to TCP port %TCPPort; because it is in use by another process on the %ServerName; server.

Wait until the other process is completed, and then try the operation again.

12703

VMM cannot establish a trust relationship for the SSL/TLS secure channel for %ServerName; server.

Install the certificate to the trusted people root store of the VMM server and then try the operation again.

12704

Unable to connect to the Hyper-V service on the server %ServerName;.

Ensure that the Hyper-V Virtual Machine Management service (vmms) and the Virtual Machine Manager Agent are installed and running on the server %ServerName;.

12705

The volume does not contain a recognized file system.

Please make sure that all required file system drivers are loaded and that the volume is not corrupted.

12706

The virtualization software on the host %ServerName; does not support the conversion operation on a virtual hard disk.

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

12707

The virtualization software on host %ServerName; does not support the compacting of a fixed virtual hard disk.

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

12708

The specified pass-through disk %FilePath; does not exist on host %ServerName;.

Select an offline pass-through disk and then try the operation again. If you have recently changed your disk configuration, wait approximately 30 minutes or you can manually refresh the properties by using the Refresh-VMHost cmdlet and then try the operation again.

12709

>The operation on %ComputerName; did not complete successfully because of the error: %DetailedErrorMessage;.

Ensure that the parameters are valid, and then try the operation again.

13200

The selected machine %ServerName; cannot be virtualized. Boot volume %VolumeDriveLetter; must be attached to the IDE bus for the virtual machine to start up.

Modify the Bus assignments so that the boot volume is located on the first hard disk of the virtual machine and then try the operation again.

13202

Virtual Machine Manager is unable to emulate the exact configuration of the source machine %ServerName;. The number of virtual processors could not be set to %ProcessorInfo;. The number of virtual processors on the resulting virtual machine will be adjusted to the closest value within the valid range for this host.

Ensure the virtual machine host %VMHostName; has adequate computational power and then adjust the number of virtual processors on the virtual machine. You can also move the virtual machine to a host with adequate computational power.

13203

Host %VMHostName; cannot be used in physical-to-virtual or virtual-to-virtual conversions.

Select a host running supported virtualization software and then try the operation again.

13204

Boot Configuration Data (BCD) WMI provider is not installed on the Virtual Machine Manager Server.

Install the BCD WMI provider on %ServerName; and then try the operation again.

13205

The Boot Configuration Data (BCD) file on virtual machine %VMName; is not recognized.

Ensure that the file boot\BCD on the boot volume of the virtual machine %VMName; is not corrupt.

13207

The file system of boot\system volume on virtual machine %VMName; is not recognized.

Ensure that the boot\system volume on the virtual hard disk has a valid file system.

13208

Unable to insert integration services disk because it is not found on the system drive path on host %VMHostName;.

Ensure that the host is running Virtual Server or Hyper-V virtualization software.

13209

Cannot insert integration services disk because virtual machine %VMName; on host %VMHostName; does not have a virtual DVD drive.

Ensure that the virtual machine has a virtual DVD drive and then try the operation again.

13210

Timeout occurred while waiting for VM integration services to be installed on virtual machine %VMName; residing on host %VMHostName;.

Ensure that the version of the VM integration services binaries matches the version of the guest operating system in the virtual machine and then try the operation again.

13212

%VMHostName; is not a valid host for the specified conversion.

Ensure that the host is running Virtual Server or Hyper-V virtualization software.

13213

%VMHostName; is not a valid host for the specified conversion.

The virtualization software on the source virtual machine host must be VMware.

13214

Parameters %NameList; cannot be specified at the same time.

Ensure that only one of these parameters is specified and then try the operation again.

13215

The file path %FileName; is not a valid VMware path.

Ensure that the path is in the correct format and then try the operation again.

13216

Some jobs in the jobs group have different source and target parameters.

Ensure that all jobs in a job group have the same source and target parameters.

13217

To install virtual guest services on virtual machine %VMName; residing on host %VMHostName;, the virtual machine must have at least one virtual hard disk.

Ensure that the virtual machine has at least one virtual hard disk with a valid operating system and then try the operation again.

13218

Virtual Guest Services are not available for the operating system on virtual machine %VMName; residing on host %VMHostName;. Virtual SCSI drives and virtual network cards may not function properly on this virtual machine.

Update the operation system on this virtual machine to the latest service pack and then try the operation again.

13219

The existing Virtual Guest Services on virtual machine %VMName; residing on host %VMHostName; was installed by an early version of Microsoft Virtual Server. The service cannot be updated directly.

Uninstall the existing Virtual Guest Services on the virtual machine by using the same virtualization software that installed it and then try the operation again.

13220

The selected machine %ServerName; cannot be virtualized. Hyper-V virtualization software volume %VolumeDriveLetter; must be attached to the IDE bus for the virtual machine to start up.

Modify the bus assignments so that the system volume is located on the IDE bus on the virtual machine and then try the operation again.

13221

The specified source virtual machine %VMName; contains virtual hard disk %FileName; more than once.

Ensure that the source virtual machine contains each virtual hard disk only once.

13222

An internal error occurred while Virtual Guest Services were being installed on virtual machine %VMName; residing on host %VMHostName;.

Try the operation again. If the same error occurs again, contact your support personnel for further help.

13223

An error occurred while Virtual Guest Services were being installed on virtual machine %VMName; residing on host %VMHostName;.

See Help for the Virtual Guest Services installer, resolve any issues preventing the installation from succeeding, and then try the operation again.

13224

Unable to install Virtual Guest Services on virtual machine %VMName; residing on host %VMHostName; because no virtual DVD device is available on the virtual machine. No DVD device is available on the IDE bus, and no more channels are available on the IDE bus to add a temporary DVD device.

Add a DVD drive to the virtual machine or modify the bus assignments or volume selection to create space on the IDE bus so that a temporary DVD drive can be created.

13225

The current version of Virtual Server on host %VMHostName; does not support conversion of the %SoftwareVersion; operating system.

Apply update 948515 to the Virtual Server software on host %VMHostName;. For more information, go to https://go.microsoft.com/fwlink/? LinkId="120407".

13226

Virtual hard disk %FileName; cannot be mounted on host %VMHostName; because it conflicts with other disks.

Wait a few moments and then try the operation again.

13227

Network adapter drivers are not available for the operating system of the source computer. The virtual machine will be created without network cards.

Update the virtual machine with the latest service pack and ensure that Virtual Guest Services are installed.

13228

Virtual Guest Services cannot be installed on virtual machine %VMName;, deployed on host %VMHostName;.

The host virtualization software must be either Virtual Server or Windows Server Virtualization.

13229

This action is not supported on virtual machines that have pass-through disks.

Install virtual guest services on the operating system of the virtual machine manually.

13230

Virtual Machine Manager encountered an error while connecting to the agent after restarting the computer %ComputerName; into Windows PE. This error may be due to missing WinPE drivers for local storage on the source machine.

Create a new folder under %StaticDriverPath; on the VMM machine and copy all of the storage or networks drivers for %ComputerName; to the new folder.

13231

Offline physical-to-virtual conversion cannot be performed on machines that have a non-ACPI hal.dll.

Try an online physical-to-virtual conversion for the supported operating systems.

13232

Virtual machine %VMName; on host %VMHostName; does not have any virtual hard disks. Virtual Guest Services cannot be installed on a virtual machine that does not have a virtual hard disk and operating system installed.

Attach a virtual hard disk and install an operating system on virtual machine %VMName; and then try the operation again.

13233

Unable to install Virtual Guest Services on virtual machine %VMName;. The Hyper-V Integration Services setup exited with error code %VGSInstallerError;.

For more information, refer to the Hyper-V documentation for virtual machine integration services at https://go.microsoft.com/fwlink/? LinkId="118036" and then try the operation again.

13234

The format of the file %FileName; on server %ServerName; is not supported.

Refer to the Virtual Machine Manager help for the list of supported VMDK file formats. Ensure that the format is listed as supported, and then try the operation again.

13235

Unable to uninstall the System Center Virtual Machine Manager P2V Agent from virtual machine %VMName; on host %VMHostName;.

Uninstall the System Center Virtual Machine Manager P2V Agent manually from the virtual machine.

13236

The -Check and -Trigger parameters cannot be specified together.

Use the -Check parameter to check for errors without starting the P2V operation or use -Trigger to begin the P2V conversion.

13237

Virtual Guest Services are not available for the operating system on virtual machine %VMName; residing on host %VMHostName;. Virtual SCSI drives and virtual network cards may not function properly on this virtual machine.

Update the operating system on virtual machine %VMName; to the latest service pack and then try installing Virtual Guest Services manually.

13238

The Virtual Machine Manager P2V Agent was not removed from the computer %ComputerName; because -Credential parameter has not been supplied.

Uninstall the System Center Virtual Machine Manager P2V Agent using Add or Remove Programs on %ComputerName;.

13239

-Credential parameter must be specified if -Force parameter is not specified.

Specify the -Credential parameter to remotely uninstall the System Center Virtual Machine Manager P2V Agent from %ComputerName;. If access to %ComputerName; is not available, use -Force parameter to remove the agent management records from System Center Virtual Machine Manager Server.

13240

Parameters -OfflineIPAddress, -OfflineSubnetMask, -OfflinePrefixLength, -OfflineDefaultGateway, -OfflineNICMacAddress can only be specified for offline conversion.

Remove offline conversion parameters

13241

One or more required parameters are missing. The following parameters must be specified: -OfflineIPAddress, -OfflineDefaultGateway, -OfflineNICMacAddress and -OfflineSubnetMask (for IPv4 addresses) or -OfflinePrefixLength (for IPv6 addresses).

Specify all required parameters and then try the operation again.

13242

One of the IP parameters provided for offline communication is not valid.

Confirm that the offline settings for IP address, subnet mask, prefix length, and default gateway are valid.

13243

The snapshot creation failed because VSS writer %VssWriterGuid; on source machine %ComputerName; did not respond within the expected time interval.

Ensure that VSS writer is functioning properly and then try the operation again.

13244

The volume %VolumeDriveLetter; selected for physical-to-virtual conversion is not accessible from Windows PE. This is usually caused by missing or incorrect storage drivers in Windows PE. %ComputerName; may now need to be manually restarted into the original operating system using the boot menu.

Exclude this volume from conversion. Or, if you are performing an offline physical-to-virtual conversion, create a new folder under %StaticDriverPath; on the VMM computer and then copy all of the storage or networks drivers to the new folder.

13245

Virtual Machine Manager encountered an error while connecting to the agent after restarting the computer %ComputerName; into Windows PE. This error may be due to missing Windows PE drivers for local storage or the network on the source machine.

Create a new folder under %StaticDriverPath; on the VMM machine and then copy all of the storage or networks drivers for %ComputerName; to the new folder.

13246

No compatible drivers were identified for the device: %DeviceDescription;. The offline physical-to-virtual conversion requires a driver for this device.\n\nDevice Type: %DeviceType;\nDevice Description: %DeviceDescription;\nDevice Manufacturer: %DeviceManufacturer;\nHardware IDs (listed in order of preference):\n%HardwareIDs;\nCompatible IDs (listed in order of preference):\n%CompatibleIDs;

Create a new folder under %StaticDriverPath; on the Virtual Machine Manager server and then copy the necessary 32-bit Windows Vista driver package files for this device to the new folder. The driver package files include the driver (.sys) and installation (.inf and .cat) files. Check the device manufacturer's website for the necessary drivers.

13247

No compatible drivers were identified for the device: %DeviceDescription;. The offline physical-to-virtual conversion requires a driver for this device.\n\nDevice Type: %DeviceType;\nDevice Description: %DeviceDescription;\nDevice Manufacturer: %DeviceManufacturer;\nHardware IDs (listed in order of preference):\n%HardwareIDs;\nCompatible IDs (listed in order of preference):\n%CompatibleIDs;

Create a new folder under %StaticDriverPath; on the Virtual Machine Manager server and then copy the necessary 32-bit Windows Vista driver package files for this device to the new folder. The driver package files include the driver (.sys) and installation (.inf and .cat) files. Check the device manufacturer's website or try the following link: %SuggestedDriverLocation; for the necessary driver files.

13248

VMM does not recognize the format of INF file %FileName;.

Ensure that the correctness of the driver package that %FileName; is a part of and then try the operation again.

13249

Online physical-to-virtual conversion of a domain controller is not recommended.

To perform an offline conversion, run the New-P2V cmdlet again, and specify the -Offline parameter.

13250

The selected machine %ServerName; cannot be virtualized. The system volume %VolumeDriveLetter; must be attached to the IDE bus for the virtual machine to start up.

If the size of the volume %VolumeDriveLetter; exceeds the maximum IDE bus disk size for Virtual Server, try using a Hyper-V host.

13251

To perform a physical-to-virtual conversion, all virtual hard disks of a highly available virtual machine must be placed on the same volume.

Specify the same location for all virtual hard disks and the virtual machine and then try the operation again.

13252

There is already an SSL certificate associated with port %TCPPort; on machine %ServerName;.

Ensure that no application on machine %ServerName; listens for HTTP traffic on TCP port %TCPPort; during the conversion. Alternatively use registry key HKLM\Software\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings\P2VBITSTcpPort on the VMM server to change the P2V transfer port number and add the necessary firewall rule for TCP port %TCPPort; on machine %ServerName;.

13600

The network location override flag must be set when specifying a network location.

Specify the OverrideNetworkLocation flag and then try the operation again.

13601

VLAN IDs are not consistent with the VLAN mode.

For the VLAN Access mode, specify only -VLANID. For the VLAN Trunk mode, specify only -VLANTrunkID.

13602

VLAN IDs are specified without the VLAN mode.

When using -VLANID or -VLANTrunkID, specify the -VLANMode.

13603

The -OverrideNetworkLocation parameter is inconsistent with -NetworkLocation.

If -OverrideNetworkLocation is set to TRUE, specify -NetworkLocation. If -OverrideNetworkLocation is set to FALSE, omit -NetworkLocation.

13604

The Virtual Machine Manager server lost connectivity to host %VMHostName; after applying the network settings. This might be the result of an incorrect VLAN setting.

Check connectivity from the Virtual Machine Manager server to the host. If there is no connectivity, try connecting a terminal to the host and reverting the changes by using the Hyper-V Virtual Network Manager locally on the host. If that is not possible, provide connectivity between the host and the VMM Server by using a different network adapter.

13605

Cannot set VLAN properties on physical network adapter %FriendlyName;, because it is not connected to a virtual network.

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

13606

Cannot connect physical network adapter %FriendlyName; to virtual network %VirtualNetworkName;, because it is connected to another virtual network.

Disconnect the physical network adapter from the other virtual network and then try the operation again.

13607

The specified network location is not valid.

Specify a different network location and then try the operation again.

13609

The specified MAC address range conflicts with an existing Organizationally Unique Identifier (OUI) or reserved address.

Specify a MAC address range, which does not conflict with an existing OUI or reserved range.Virtual Machine Manager default range is 00:1D:D8:B7:1C:00-00:1D:D8:F4:1F:FF.

13610

The specified MAC address range %RangeStart; - %RangeEnd; is not valid.

1. Specify an end address for the range that is greater than the start address.\n\n2.Ensure that the first three octets of the start address and the end address for the range are equal.

13611

All addresses in the MAC address range have been used.

Extend the MAC address range or specify a new range.

13612

Cannot connect the virtual network adapter because virtual switch %FriendlyName; on host %VMHostName; has no available ports.

Use the VMware Virtual Infrastructure Client to increase the number of ports.\n\nNote: This setting requires the host to be restarted.

13613

Cannot set VLAN properties on virtual network %FriendlyName;, because the virtual network is not bound to the host.

Connect the virtual network to the host and then try the operation again.

13619

The host physical network adapter cannot be removed from virtual network %VirtualNetworkName; because the virtual network has a VMware service console port on host %ServerName;.

Remove the service console port from virtual network %VirtualNetworkName; by using the VMware Virtual Infrastructure Client or specify a different virtual network.

13621

The -Path parameter must be specified for New-VirtualNetwork.

Specify the -Path parameter and then try the operation again.

13623

Cannot remove physical network adapter %FriendlyName; from virtual network %VirtualNetworkName; because the adapter is not connected to the virtual network.

Specify a different host network adapter and then try the operation again.

13626

The specified virtual network does not exist.

Run Get-VirtualNetwork and ensure that the virtual network is on the list.

13800

The host cluster name contains a character that is not allowed.

A host cluster name cannot contain any of the following characters: : * ? < > / | \ ". Check the host cluster name and then try the operation again.

13801

A host cluster with the name %HostClusterName; already exists.

Specify a different host cluster name and then try the operation again.

13802

A cluster with the name %HostClusterName; does not exist.

Specify a different cluster name and then try the operation again.

13803

The cluster node failure reserve equals or exceeds the number of nodes in cluster %HostClusterName;.

Specify a cluster node failure reserve less than the number of nodes in the cluster and then try the operation again.

13806

The host does not exist in cluster %HostClusterName;.

Specify a different host name and then try the operation again.

13807

Unable to add %ComputerName; as a virtual machine host.

Ensure that the specified machine name is a cluster name or a node of a cluster, and then try the operation again.

13808

Unable to add %ComputerName; as a Library server.

Ensure that the specified machine name is a clustered file server or a node of a cluster, and then try the operation again.

13811

Virtual network %FriendlyName;, configured on host %ComputerName;, is not highly available.

To make the virtual network highly available, ensure that a virtual network with the same name, tag, and connectivity exists on all hosts in the cluster.

13813

The specified VMware resource pool was not found.

Ensure that the resource pool exists in this virtualization manager and then try the operation again.

13814

The virtual machine %ComputerName; cannot be moved to VMware resource pool %FriendlyName;.

Ensure that the target resource pool belongs to the same computer resource and then try the operation again.

13815

Virtual Machine Manager could not enumerate the network shares on %ComputerName;.

Ensure that the computer %ComputerName; exists, that the specified credentials have administrative rights, and then try the operation again.

13919

Specified failure node reserve (%ParameterValue;) exceeds the %MaxLimit; limit for host cluster %HostClusterName; (total nodes in cluster- 1).

Specify a failure node reserve less than or equal to %MaxLimit;.

13921

Highly available virtual machine %VMName; is not supported by VMM because one or more of its network adapters is not configured correctly.

Ensure that all of the virtual network adapters are either disconnected or connected to highly available virtual networks.

13922

Highly available virtual machine %VMName; is not supported by VMM because one or more of its network adapters is not configured correctly.

Ensure that all of the virtual network adapters are either disconnected or connected to highly available virtual networks. Additionally, each port group the VM is connected to must be present on each of the nodes of the cluster.

13923

Highly available virtual machine %VMName; is not supported by VMM because its cluster resource group is not configured correctly.

Ensure that the resource group only contains a single VM resource, a single VM configuration resource, and zero or more disk resources all belonging to this VM.

13924

Highly available virtual machine %VMName; is not supported by VMM because the VM uses non-clustered storage.

Ensure that all of the files and pass-through disks belonging to the VM reside on highly available storage.

13925

Host cluster %HostClusterName; cannot be removed directly from Virtual Machine Manager because it is a VMware cluster.

To remove the host cluster from Virtual Machine Manager, remove the Virtualization Manager that it belongs to. To destroy the host cluster, use the VMware Virtual Infrastructure Client.

13926

Host cluster %HostClusterName; was not fully refreshed. The host cluster might appear to not have highly available storage or virtual networks.

Ensure that all the nodes are online and do not have Not Responding status in Virtual Machine Manager. Then refresh the host cluster again.

See Also

Concepts

User Interface Error Messages