User Interface Error Messages

201

Cannot ensure configuration of the service %ServiceName;.

Check the Windows Event Log for troubleshooting information.

203

VMM cannot start the service %ServiceName; service.

Run services.msc, select and right-click the service %ServiceName;, and then click Start.

205

System Center Virtual Machine Manager was not installed successfully.

Review the error log information and then try running Setup again.

208

Another instance of System Center Virtual Machine Manager 2008 Setup is running.

Close all open instances of the Virtual Machine Manager Setup program and then try the installation again.

210

Setup cannot create the file %FileName;.

Verify that Setup has permission to create the file, and then try the operation again.

212

The configuration data for this product is corrupted.

Contact your support personnel for further help.

214

The computer does not meet the minimum processor configuration requirements to run Virtual Machine Manager. The minimum required processor speed is %ProcessorClockSpeed; MHz.

Either upgrade the processor speed in the computer or install Virtual Machine Manager on a different computer that meets the hardware requirements.

216

This computer does not meet the recommended amount of memory.

The recommended amount of memory for optimal performance is %MemoryRecommended; MB. Either upgrade the amount of memory in the computer or install Virtual Machine Manager on a different computer that meets the hardware requirements.

220

This computer is not part of a domain.

Virtual Machine Manager requires a computer that is a member of a domain. Join this computer to a domain, and then run Setup again.

222

There is insufficient disk space on the program files volume %BinaryVolumeDriveLetter; to complete the installation.

Create %BinaryDiskSpaceRequired; MB of disk space on the volume to continue with the installation.

224

Setup has detected instance MICROSOFT$VMM$ running on an older version of SQL Express 2005.

Uninstall MICROSOFT$VMM$ and then run Virtual Machine Manager Setup again to install SQL Express 2005 Service Pack 1.

226

%ProductName; Beta is currently installed.

To upgrade %ProductName;, refer to the upgrade documentation at https://go.microsoft.com/fwlink/? LinkId="117133". To perform a new installation, uninstall all Beta Virtual Machine Manager components and then install Virtual Machine Manager 2008.

228

A different version of %ProductName; is currently installed.

Uninstall the existing %ProductName; from Add/Remove Program and then run Setup again.

230

Virtual Machine Manager cannot be successfully installed because service %ServiceName; is marked for deletion.

Reboot the server, and then run Setup again.

233

The SQL Server database %DatabaseName; is currently in use by another program or process.

Select another database and try again.

235

Setup has detected a database that is not compatible with the version being installed.

Delete %DatabaseName; from SQL instance %SqlInstance; and then continue with Setup.

239

Setup has detected an unsupported version of Microsoft WinFX Runtime Components or .NET Framework 3.0.

Uninstall the existing version, and then run Setup again.

241

Disk space cannot be calculated.

Select a different installation location, and then try the operation again.

243

System Center Virtual Machine Manager requires Windows Remote Management (WinRM) 1.1.

To download WinRM 1.1, go to https://go.microsoft.com/fwlink/? LinkId="84599".

245

SQL service %ServiceName; is not running on the computer.

Verify that service %ServiceName; is running, and then try the operation again.

247

Setup has detected an unsupported version of Windows Remote Management (WinRM). Virtual Machine Manager requires WinRM 1.1.

To download WinRM 1.1, go to https://go.microsoft.com/fwlink/? LinkId="84599".

249

Agent connection port and file transfer port cannot be of the same number.

Enter different port numbers.

256

VMM cannot load the file %FileName;. The file may be corrupted or missing.

Run the Virtual Machine Manager Setup program directly from the product CD. If the setup program from the CD fails, obtain a new copy of the CD from your vendor.

260

The product key is not valid.

The product key is located on the back of the Virtual Machine Manager product CD. Enter a valid product key and then try installation again.

263

%InputParameterTag; exceeds %MaxLimit; characters.

Enter a valid input, and then try the operation again.

266

The path %FileName; exceeds %MaxLimit; characters.

Enter a shorter path name, and then try the operation again.

268

Not all database files from a previous installation were found at %Location;.

Delete the existing file or choose an alternative location for your database.

270

The location cannot be on removable media or a network share.

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

272

The selected location %DirectoryPath; is read-only, hidden, a system folder, or a root volume.

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

274

The directory %DirectoryPath; is not on an NTFS volume.

Install prerequisite software and Virtual Machine Manager on an NTFS volume, and then try the operation again.

276

The parameter %CommandlineArgument; is not valid.

See "Installing Virtual Machine Manager" in the Virtual Machine Manager Setup help for information about parameter usage.

278

The parameter %CommandlineArgument; does not have a value associated with it.

See "Installing Virtual Machine Manager" in the Virtual Machine Manager Setup help for information about the specific parameter.

280

The passwords entered do not match.

Enter the passwords again, and then try the operation again.

282

The evaluation copy of System Center Virtual Machine Manager has expired.

For details about obtaining a license, go to the System Center Virtual Machine Manager Web site at https://go.microsoft.com/fwlink/? LinkId="117146".

285

%InputParameterTag; must be an integer between 0 and 65535.

Enter the port number again.

289

The .ini file is not specified in the command line.

For more information, see "Installing Virtual Machine Manager" in the Virtual Machine Manager Setup help.

292

Configuration of Virtual Machine Manager failed.

For more information about configuration, see "Troubleshooting" in the Virtual Machine Manager Setup help.

294

Setup was unable to remove Virtual Machine Manager from the Windows Firewall exceptions list.

If Windows Firewall is enabled, remove Virtual Machine Manager from the exceptions list. In Control Panel, click Windows Firewall, click the Exceptions tab, and remove from the list of exceptions.

297

The requested action cannot be specified by using the command line.

For more information, see "Installing Virtual Machine Manager" in the Virtual Machine Manager Setup help.

299

Share %ShareName; does not exist on the VMM server.

Enter the name of an existing share.

303

The folder %FolderPath; cannot be deleted.

Delete the folder manually.

305

Virtual Machine Manager cannot be installed on a computer running this operating system.

Install Virtual Machine Manager on a computer running Windows Server 2003 R2.

307

The folder %FolderPath; cannot be created. The folder may already exist.

Delete the folder if it exists, and then run Setup again.

309

Either the existing Virtual Machine Manager database could not be accessed, or the database is corrupted.

Restore to a valid database and ensure that the SQL Server service is running. Run Setup again.

311

The prerequisite check was not successful.

View the errors in the Virtual Machine Manager Setup log file %SetupLogFile;, view the errors and make the required changes. Run Setup again.

313

Active Directory Domain Services cannot validate user %UserName;.

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

316

Setup could not configure the firewall exceptions.

If the configuration is being run from OEM Setup, verify that Setup has the necessary privileges to configure firewall exceptions, and then run the configuration again. Otherwise, uninstall the VMM server and then install it again.

319

The Virtual Machine Manager database was not created.

The Virtual Machine Manager database was not created. Delete %DatabaseName;.mdf and %DatabaseName;_log.ldf if they exist at %FolderPath; or use a unique name for the database. Also, verify that disk quota management is not enabled for the drive where the database is being created. Then run Setup again.

321

Database files in %DataFilesCompleteLocation; could not be removed.

Delete the files manually.

323

The Virtual Machine Manager database was not created from the existing database files.

Delete the existing files or choose another location for the database.

326

Cannot create service %ServiceName;.

Reboot the computer, uninstall Virtual Machine Manager, and then run Setup again.

328

Setup was unable to configure service %ServiceName;.

Check the Windows Event Log for troubleshooting information.

330

Cannot delete necessary setup files from %InstallLocation;.

Delete the files manually.

332

VMM cannot start Setup.

Run Setup from the product CD. If you are running it from the CD already, the CD is corrupted. Request a new CD from your administrator.

336

Setup could not query the Web site setting.

Ensure that the IIS Admin Service is running and then try running VMM Self-Service Portal Setup again. If you are installing the portal on a computer that is running Windows Server 2008, also ensure that the Web Server (IIS) role is added and that the IIS 6 Management Compatibility role service is installed.

339

Setup cannot connect to the specified SQL Server instance.

Ensure that the server name and instance name are correct. If you are installing VMM remotely, ensure that remote connections are set up correctly, and then try Setup again.

343

%Prerequisite; installation has failed. For error detail, see %SetupLogFile;.

Manually install %Prerequisite;.

346

Cannot access the registry key %RegistryKey; for the Microsoft SQL Server instance %SqlInstance;.

Verify that the SQL 2005 instance is installed and configured correctly.

350

Setup cannot write to file %FileName;.

Delete the file if it exists, and then run Setup again.

358

Setup was unable to set permissions on folder %DirectoryPath;.

Ensure that the folder %DirectoryPath; is a valid location and that the current user has permission to access the location.

360

Setup cannot find a SQL Server instance on %ComputerName;.

Verify that SQL Server 2005 is properly installed and that the SQL Server service is running.

362

The SQL database %DatabaseName; does not exist.

Check the "Create a new database" check box to create a new database, or use an existing database.

364

Setup cannot find a database in the SQL Server instance %SqlInstance;.

Select the "Create a new database" check box to create the database, or select another SQL Server instance.

366

System Center Virtual Machine Manager requires the Windows Automated Installation Kit (WAIK) to be installed.

To download the Windows Automated Installation Kit, go to https://go.microsoft.com/fwlink/? LinkID="86477".

368

To continue, your computer must be restarted.

Cancel the Virtual Machine Manager server setup, restart the computer, and then run the Virtual Machine Manager server setup again.

370

The VMM Self-Service Portal requires the IIS 6 Management Compatibility role service.

Open Server Manager, select the Web Server (IIS) role, click "Add Role Services", and then install the IIS 6 Management Compatibility role service.

455

%Value; is not a valid entry

Please specify a value between 0 and 255.

467

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

Remove some existing hosts and then try the operation again. To manage more than five hosts, upgrade VMM Workgroup Edition. Find information on upgrading at https://go.microsoft.com/fwlink/? LinkId="94662".

503

The specified virtual network %VirtualNetworkName; does not exist.

Verify the virtual network name by refreshing the Host Properties dialogue box, go to the Hardware tab and click the Virtual Network option. Then try the operation again.

510

A virtual network path was not selected.

Select a virtual network path, and then try the operation again.

512

The network IP address must be the base of the subnet.

Enter a valid IP address that is the base of the subnet, and then try the operation again.

514

The ending IP address is not in a valid range. The last valid address of the subnet is reserved.

Enter a valid IP Address within the range, and then try the operation again.

516

The DHCP settings could not be saved. The DHCP Server address is not in a valid range. DHCP Server address should be between the first valid IP address and starting IP address.

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

518

The network mask is not valid. The network mask format should be xxx.xxx.x.x.

Enter a valid network mask, 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.

524

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

Enter a valid lease time, 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.

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.

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.

557

You must enter at least one virtual machine path.

Add a default virtual machine path, and then try the operation again.

650

A known image file is not selected.

Select an image file or choose a different capture mode.

652

The value for VM Memory is empty.

Enter a value for the amount of VM Memory, and then try the operation again.

654

The value %MemorySize; MB specified for virtual machine memory is not within a valid range on the %VMHostName; host.

Enter a value between %MinMemory; and %MaxMemory; MB for virtual machine memory, and then try the operation again.

656

The value entered for the MAC address is not valid.

Enter a MAC address in the format xx-xx-xx-xx-xx-xx or choose to use a dynamic address, and then try the operation again.

681

A destination file name is required when creating a new disk.

Create a new file name, and then try the operation again.

686

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

The selected virtual machine %VMName; cannot run Sysprep on host %VMHostName;. Upgrade Virtual Server on the selected host to the R2 SP1 version, and then try the operation again.

699

Virtual machine %VMName; needs to be in a virtual machine host to share its disks.

Deploy the virtual machine to a virtual machine host and try the operation again.

701

Virtual hard disk %FileName; needs to be of fixed size type for sharing to be allowed.

Provide a virtual hard disk that is of fixed size and try again.

703

Destination for the disk is %ObjectType;. Sharing virtual hard disks is only allowed between virtual machine objects.

Provide a virtual machine and try again.

705

Destination for the virtual hard disk %FileName; is not a shared SCSI bus.

Set the SCSI adapter as destination for the shared disk and try again.

720

A user name must be specified.

Enter a user name and then try the operation again.

725

Unable to configure hardware because a text file is not specified.

Enter a text file and then try the operation again.

734

The value %MemorySize; MB specified for virtual machine memory is not within a valid range.

Enter a value between %MinMemory; and %MaxMemory; MB for virtual machine memory, 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.

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, first remove it from all virtual machines, templates, hardware and guest operating system profiles that are using it, then try the operation again.

817

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

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

845

The share path %FileName; is too long.

Verify that the fully qualified path to the share has fewer than %MaxLength; characters, then attempt to add it again.

1408

Cannot locate the user role because it no longer exists.

Close and reopen the Virtual Machine Manager Administrator Console, and then try the operation again.

1417

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

A member of a user role must have an Active Directory Domain Services account. Specify a valid domain account, or click Browse to select an account, and then try the operation again.

1419

Unable to create the virtual machine because no suitable host for this virtual machine was found.

Contact the Virtual Machine Manager administrator.

1603

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

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

1613

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

You must be logged on under an account that is a member of a valid Administrator or Delegated Administrator user role to open the Administrator Console.

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.

To restart this job, navigate to the Jobs view and select the job in the results pane. Then, in the Actions pane, click Restart.

1736

Cannot connect to virtual machine %VMName; because the Virtual Guest Services feature is not available.

If the Administrator Console is on a computer running Microsoft Vista without Service Pack 1, Windows XP without Service Pack 3, or Windows Server 2003, you must install Virtual Guest Services manually on the virtual machine to enable connections. If Virtual Guest Services are already installed, ensure that the component has not been disabled.

1758

Unable to change the host group name because no name was specified.

Enter a name for this host group.

1783

Unable to migrate multiple virtual machines at the same time.

Select each virtual machine and migrate it individually.

2401

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

2403

VMM cannot rename %FileName; because the specified name is not valid.

A folder name cannot contain any of the following characters: \ / : * ? " < > |. Specify a valid folder name, and try the operation again.

2405

VMM is unable to find a domain account for owner %UserName;.

The owner must have an Active Directory Domain Services account. Either type an account, or click Browse to select an account, and then try the operation again.

2408

VMM is unable to browse volumes on %ComputerName;, because access is denied.

Membership in the Administrators, Power Users, Print Operators, or Server Operators group on %ComputerName; is required to enumerate volumes.\nEnsure you have sufficient permissions, and then try the operation again.

2410

When using the Join Domain feature, the password is displayed as clear text when creating a virtual machine on a host. This would permit anyone with access to the host or virtual machine access to the password.

Use an account with limited privileges that can only create computer accounts and join them to the domain or use Active Directory Services Interface (ADSI) and Windows Script Host (WSH) to create a Visual Basic Script (VBScript) that automates the creation of computer accounts. A sample script is given in the Microsoft Knowledge Base, article Q315273 (https://support.microsoft.com/default.aspx? scid="kb";en-us;q315273).

2416

Cannot install the VMware Infrastructure Client on virtual machine %VMName; because Internet Explorer could not be found or accessed.

Ensure that Internet Explorer is in the system path, or install the VMware Infrastructure Client manually.

2418

The following errors were encountered while adding members to this user role: %InvalidUserRoleMembers;

Select a set of valid domain accounts to add to this user role.

2607

The SQL Server service account does not have permission to access Active Directory Domain Services (AD DS).

Ensure that the SQL Server service is running under a domain account or a computer account that has permission to access AD DS.For more information, see "Some applications and APIs require access to authorization information on account objects" in the Microsoft Knowledge Base at https://go.microsoft.com/fwlink/? LinkId="121054".

3120

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

Specify a volume that exists on the source machine %ServerName;. If the configuration of the source machine changed, gather system information again by restarting the Convert Physical Server wizard.

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.

3231

Unable to convert the physical server. Virtual Machine Manager requires a host with Hyper-V or Virtual Server 2005 R2 SP1.

Use the "Add hosts" action in the Administrator Console to add a host and then try the operation again.

3407

The entered URL is not valid.

Enter a valid reporting server address in the Reporting settings in the Administration pane.

3451

Error while connecting to the reporting server.

Ensure that Virtual Machine Manager management pack and its reports are installed on the Operations Manager server.

3510

There is insufficient disk space on the volume %VolumeDriveLetter; to complete placement of the virtual machine.

Free %BinaryDiskSpaceRequired; of disk space on the volume %VolumeDriveLetter;, or choose a different volume to continue with the placement.

3517

Unable to save the virtual machine configuration files because volume %VolumeDriveLetter; is marked as unavailable for placement.

Select a different save path for this virtual machine and then try the operation again.

10202

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

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

10205

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

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

10607

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

Specify the -VirtualHardDisk or -PassThroughDisk parameter.

10649

Unable to migrate the virtual machine %VMName; because the processor is not compatible with the host %VMHostName;.

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

10683

Unable to contact cluster service on %ComputerName;.

Ensure that the cluster service is properly installed and running.

11000

The number of processors requested on the virtual machine %VMName; (%Count;) exceeds the maximum supported by the host virtualization software (%MaxLimit;).

Select a different host or reduce the number of processors on the virtual machine and then try the operation again.

11002

The memory requested for the virtual machine %VMName; (%MemorySize; MB) is not within the range that the host virtualization software supports.

Select a different host or change the requested memory for the virtual machine to a value within the supported range (%MemorySizeMinLimit; - %MemorySizeMinLimit;), and then try the operation again.

11004

The number of devices attached to the SCSI bus on the virtual machine %VMName; exceeds the maximum number supported by the host virtualization software (%MaxLimit;).

Reduce the number of SCSI devices to %MaxLimit; or fewer and then try the operation again.

11006

The virtual machine %VMName; is configured as highly available but the selected host is not a highly available host.

Select a highly available host for the virtual machine and then try the operation again.

11008

This configuration causes the host cluster to become overcommitted.

Select a different highly available host and then try the operation again.

11010

The Network location %NetworkLocation; associated with the virtual machine %VMName; does not exist on host %VMHostName;.

Select a different host and then try operation again.

11012

The virtual machine %VMName; is not configured as highly available but the selected host is highly available.

Select a non-highly available host for the virtual machine and then try the operation again.

11014

The projected CPU utilization will exceed the available CPU on the host.

Select a different host and then try the operation again.

11018

All of the volumes on %VMHostName; are marked as not available for placement.

Select a different host or add more storage and then try the operation again.

11032

Virtual machine %VMName; cannot be placed on Hyper-V host %VMHostName; because it has checkpoints in a format incompatible with Hyper-V virtualization platform.

Select a different host and then try the operation again.

11034

The network adapter associated with network location %NetworkLocation; on host %VMHostName; is not connected.

Ensure that the network adapter is enabled and connected, and then try the operation again.

11036

Virtual machine %VMName; cannot be placed on host %VMHostName; because the host is a node in a host cluster that is managed by Virtual Machine Manager. Virtual Machine Manager does not support performing a physical-to-virtual conversion (P2V) or a virtual-to-virtual conversion (V2V) to a target host that is in a host cluster.

Try the operation again, and select a host that is not in a host cluster.

11201

Disk %DiskName; is selected multiple times for pass though to a physical host drive.

Select a different disk and then try the operation again.

11400

User role %FriendlyName; already exists.

Enter a different name for the user role and then try the operation again.

11411

Cannot use Set-VMMUserRole with an Administrator profile. There can be only one Administrator user role.

Modify the existing Administrator UserRole or create a new UserRole from DelegatedAdmin profile to delegate administration.

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.

11425

The user role specified is not valid.

Provide a valid value for User Profile. Valid values are: Administrator, DelegatedAdmin or SelfServiceUser.

11427

The ownership for this virtual machine cannot be changed because the new owner is not a member of a user role that has access to this virtual machine.

Either change the new owner to a user who has access to this virtual machine, or contact your Virtual Machine Manager administrator to request access for the user you want to own this virtual machine and then try the operation again.

11430

Either the specified user role or the specified owner (%UserName;) for this virtual machine is not valid.

Add %UserName; as a member of the user role and try again or provide a different user role or a different owner.

11432

The specified parent user role is not a top-level user role.

Specify a top level user role as the parent.

11434

The virtual machine cannot be created because a virtual machine name was not specified.

Enter a valid virtual machine name and then try the operation again.

11436

The Virtual Machine Manager server could not validate user %UserName;.

Contact your Virtual Machine Manager administrator to verify that there is a two-way trust relationship between the user domain and the domain of the Virtual Machine Manager server.

11600

A VMware ESX Server host cannot be moved to the root host group.

ESX hosts must be in a host group that maps to a Datacenter node in VMware VirtualCenter. The root host group does not map to a Datacenter node.

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.

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.

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 on the server, and that Virtual Machine Manager has the appropriate rights to perform this action.

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.

12401

Unable to display Windows PowerShell script because Notepad could not be found.

Add the path to Notepad.exe to the Path environment variable on the Advanced tab in Windows System Properties.

12407

You cannot open the VMM Administrator Console because your user role in Virtual Machine Manager does not have access to any host groups. \n\nThis happens when an administrator is given a Delegated Administrator profile but is not assigned any host groups to administer.

Ask your VMM administrator to assign the host groups that you will administer to your user role.

12412

This action does not allow an empty password.

Enter the password.

12418

Invalid port number for %InputParameterTag;.

Enter an integer from 1 through 65535 for the port.

12422

Cannot add VMware ESX host %VMHostName; to Virtual Machine Manager because the host already is associated with a VMware VirtualCenter server (%VCSName;) that is managed by VMM.

To associate the VMware ESX host with a different VMware VirtualCenter server, first remove the host from VMM, and then add the host to VMM again, this time specifying the new VirtualCenter server.

12424

Cannot add VMware ESX host %VMHostName; to host group %HostGroupName; because the host group is not in a VMware VirtualCenter datacenter.

To add a VMware ESX host, you must add it within a VMware VirtualCenter datacenter. Select a host group that represents its VMware VirtualCenter datacenter or a child of that host group.

13201

The specified number of virtual processors (value %ProcessorInfo;) is not within a valid range for the virtualization software of host %VMHostName;.

Select a number of virtual processors between %RangeStart; and %RangeEnd; 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 to the new folder.

13249

Online physical-to-virtual conversion of a domain controller is not recommended.

Run the Convert Physical Server Wizard again, and choose the Offline Conversion option on the Volume Configuration page.

13626

The specified virtual network does not exist.

Verify the virtual network name by refreshing the Host Properties dialogue box, go to the Hardware tab and click the Virtual Network option. Then try the operation again.

13805

Unable to contact cluster service on %ComputerName;.

Ensure that the provided name is a cluster name or the computer name of a node in the cluster, and that the cluster is listed in Active Directory Domain Services. For a newly created cluster, you might need to wait for the cluster name to be added to Active Directory Domain Services.