Resources For IT Professionals
Page Details
Options

Revision #2

Wiki  >  TechNet Articles  >  System Center 2012 – Virtual Machine Manager (VMM) Error Codes [13000-13999]  >  Revision #2
System Center 2012 – Virtual Machine Manager (VMM) Error Codes [13000-13999]
You are currently reviewing an older revision of this page.
Go to current version

Use Ctrl-F to find a specific code.

Some codes have a recommended action using PowerShell as well as the general action.

Links to other error code pages can be found at Virtual Machine Manager (VMM) for System Center 2012 Error Codes.

 

If you have additional information about an error, please add it to the "Additional Troubleshooting Information" column.

 

Code Message Recommended Action (in product) Additional Troubleshooting Information
13200 The selected machine %ServerName; cannot be virtualized. Boot volume %VolumeDrive Letter; 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.
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 %Rang eEnd; and then try the operation again.
13202 Virtual Machine Manager is unable to emulate the exact configuration of the sourc e machine %ServerName;. The number of virtual processors could not be set to %ProcessorInfo;. The number of virtual pro cessors 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 computatio nal power and then adjust the number of virtual processors on the virtual machine. You can also move the virtual machin e to a host with adequate computational power.
13203 Host %VMHostName; cannot be used in physical-to-virtual or virtual-to-virtual con versions. 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 Machin e Manager management server. Install the BCD WMI provider on %ServerName; and then try the operat ion again.
13205 The Boot Configuration Data (BCD) file on virtual machine %VMName; is not recogni zed. Ensure that the file boot\BCD on the boot volume of the virtual mach ine %VMName; is not corrupt.
13206 Virtual Machine Manager cannot locate the boot or system volume on virtual machin e %VMName;. The resulting virtual machine might not start or operate properly. BLANK
13207 The file system of boot\system volume on virtual machine %VMName; is not recogniz ed. Ensure that the boot\system volume on the virtual hard disk has a va lid 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 virtualiza tion 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 vir tual machine %VMName; residing on host %VMHostName;. Ensure that the version of the VM integration services binaries matc hes 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 virtualiza tion 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 t he 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 opera tion 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 %V MHostName;, the virtual machine must have at least one virtual hard disk. Ensure that the virtual machine has at least one virtual hard disk w ith a valid operating system and then try the operation again.
13218 Virtual Guest Services are not available for the operating system on virtual mach ine %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 se rvice 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 s oftware 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 t he IDE bus on the virtual machine and then try the operation again.
13221 The specified source virtual machine %VMName; contains virtual hard disk %FileNam e; more than once. Ensure that the source virtual machine contains each virtual hard di sk only once.
13222 An internal error occurred while Virtual Guest Services were being installed on v irtual machine %VMName; residing on host %VMHostName;. Try the operation again. If the same error occurs again, contact you r support personnel for further help.
13223 An error occurred while Virtual Guest Services were being installed on virtual ma chine %VMName; residing on host %VMHostName;. See Help for the Virtual Guest Services installer, resolve any issue s 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 conve rsion of the %SoftwareVersion; operating system. Apply update 948515 to the Virtual Server software on host %VMHostNa me;. For more information, go to http://go.microsoft.com/fwlink/?LinkId=120407.
13226 Virtual hard disk %FileName; cannot be mounted on host %VMHostName; because it co nflicts 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 t hat 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 Wi ndows 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 virtua l 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 storag e 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.

Command Line Interface: 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 opera ting systems.
13232 Virtual machine %VMName; on host %VMHostName; does not have any virtual hard disk s. 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 virtua l 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 http://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 virt ual machine %VMName; on host %VMHostName;. Uninstall the System Center Virtual Machine Manager P2V Agent manual ly 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 P2 V operation or use -Trigger to begin the P2V conversion.
13237 Virtual Guest Services are not available for the operating system on virtual mach ine %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 lates t service pack and then try installing Virtual Guest Services manually.
13238 The Virtual Machine Manager P2V Agent was not removed from the computer %Computer Name; 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 C enter Virtual Machine Manager P2V Agent from %ComputerName;. If access to %ComputerName; is not available, use -Force p arameter to remove the agent management records from System Center Virtual Machine Manager management server.
13240 Parameters -OfflineIPAddress, -OfflineSubnetMask, -OfflinePrefixLength, -OfflineD efaultGateway, -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 spe cified: -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, prefi x 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 oper ation again.
13244 The volume (%VolumeDriveLetter;) selected for physical-to-virtual conversion is n ot accessible from Windows PE. This is usually caused by missing or incorrect storage drivers in Windows PE. The comput er (%ComputerName;) may now need to be manually restarted into the original operating system using the startup menu. Exclude this volume from conversion. Or, if you are performing an of fline physical-to-virtual conversion, create a new folder under %StaticDriverPath; on the VMM management server, and th en copy all of the storage or networks drivers to the new folder.

Command Line Interface: Exclude this volume from conversion. Or, if you are performing an of fline physical-to-virtual conversion, create a new folder under %StaticDriverPath; on the VMM management server, and th en 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 the computer (%ComputerName;) to the new folder.

Command Line Interface: Create a new folder under %StaticDriverPath; on the VMM machine and then copy all of the storage or networks drivers for the computer (%ComputerName;) to the new folder.
13246 No compatible drivers were identified for the device: %DeviceDescription;. The of fline physical-to-virtual conversion requires a driver for this device.\n\nDevice Type: %DeviceType;\nDevice Descriptio n: %DeviceDescription;\nDevice Manufacturer: %DeviceManufacturer;\nHardware IDs (listed in order of preference):\n%Hard wareIDs;\nCompatible IDs (listed in order of preference):\n%CompatibleIDs; Create a new folder under %StaticDriverPath; on the Virtual Machine Manager management 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 of fline physical-to-virtual conversion requires a driver for this device.\n\nDevice Type: %DeviceType;\nDevice Descriptio n: %DeviceDescription;\nDevice Manufacturer: %DeviceManufacturer;\nHardware IDs (listed in order of preference):\n%Hard wareIDs;\nCompatible IDs (listed in order of preference):\n%CompatibleIDs; Create a new folder under %StaticDriverPath; on the Virtual Machine Manager management 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 the Setup information file (%FileName;). Ensure that the correctness of the driver package that the Setup inf ormation file (%FileName;) is a part of, and then try the operation again.
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.

Command Line Interface: 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 %Volum eDriveLetter; must be attached to the IDE bus for the virtual machine to start up. If the size of the volume %VolumeDriveLetter; exceeds the maximum ID E 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 a vailable 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 computer %S erverName;. Ensure that no application on computer %ServerName; listens for HTTP traffic on TCP port %TCPPort; during the P2V conversion.\n\n Alternatively:\nOn the VMM management server, create a DW ORD registry key at HKLM\Software\Microsoft\Microsoft System Center Virtual Machine Manager management server\Settings\ P2VBITSTcpPort, set its value to the port number you want to use, and then restart the VMM service.
13253 Conversion of the virtual hard disk at (%BusType;, %Bus;, %Lun;) of the virtual m achine %VMName; residing on host %VMHostName; is not supported. Refer to the Virtual Machine Manager help for the list of supported virtual hard disk formats. Ensure that the disk format is listed as supported, and then try the operation again.
13254 Background Intelligent Transfer Service is disabled on the source machine %Server Name;. Use service management console to enable the BITS service.
13255 HTTP SSL service is disabled on the source machine %ServerName;. Use service management console to enable the HTTP SSL service.
13256 The disk with index %Id; on source machine %ServerName; is an attached virtual ha rd disk. This configuration is not supported for physical-to-virtual conversions. Detach the virtual hard disk and then try the operation again.
13257 Virtual Machine Manager management server is unable to convert %ServerName; becau se required files are missing. Copy the file %FileName; to "%FolderPath;" on the Virtual Machine Ma nager management server, run the Add-Patch cmdlet to add the required files to the Virtual Machine Manager patch cache, and then try the operation again. The file %FileName; is located either at %%WINDIR%%\Driver Cache\%OSPlatform; on %Se rverName;, or on the %OSName; (%Language;, %OSPlatform;) installation media.\nIf %FileName; is not available, locate %F ileName2; (Version: %FileVersion;) on the installation media, copy the file to "%FolderPath;", and then run the Add-Pat ch cmdlet to add the required files to the Virtual Machine Manager patch cache.
13258 Virtual Machine Manager could not convert %ComputerName; because Virtual Server, on host %VMHostName;, does not support running the %OSName; operating system on a guest virtual machine. Use a Hyper-V host for the conversion.
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 m ode, 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 management server lost connectivity to host %VMHostNa me; after applying the network settings. This might be the result of an incorrect VLAN setting. Check connectivity from the Virtual Machine Manager management serve r to the host. If there is no connectivity, try connecting a terminal to the host and reverting the changes by using th e Hyper-V Virtual Network Manager locally on the host. If that is not possible, provide connectivity between the host a nd the VMM management 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 t ry the operation again.
13606 Cannot connect physical network adapter %FriendlyName; to virtual network %Virtua lNetworkName;, because it is connected to another virtual network. Disconnect the physical network adapter from the other virtual netwo rk and then try the operation again.
13607 The specified network location is not valid. Specify a different network location and then try the operation agai n.
13609 The specified MAC address range conflicts with an existing Organizationally Uniqu e Identifier (OUI) or reserved address. Specify a MAC address range, which does not conflict with an existin g 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 or equal tha n the start address.\n\n2. Ensure that the first three octets of the start address and the end address for the range ar e 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 a gain.
13614 Host %ComputerName; does not support this VLAN setting. BLANK
13615 Configuring a virtual DHCP server is not supported on host %ComputerName;. BLANK
13616 Binding a virtual network to the host partition is not supported on host %Compute rName;. BLANK
13617 Connecting more than one physical network adapter to a virtual network is not sup ported on host %ComputerName;. BLANK
13618 A network location is required when overriding the network location. Specify a network location and then try the operation again.
13619 The host physical network adapter cannot be removed from virtual network %Virtual NetworkName; because the virtual network has a VMware service console port on host %ServerName;. Remove the service console port from virtual network %VirtualNetwork Name; by using the VMware Virtual Infrastructure Client or specify a different virtual network.
13620 Changing the name of a virtual network is not supported on an ESX host. BLANK
13621 The -Path parameter must be specified for New-VirtualNetwork. Specify the -Path parameter and then try the operation again.
13622 Physical network adapter %FriendlyName; does not support VLAN Trunk mode. BLANK
13623 Cannot remove physical network adapter %FriendlyName; from virtual network %Virtu alNetworkName; because the adapter is not connected to the virtual network. Specify a different host network adapter and then try the operation again.
13624
13625 A large number of hosts or virtual machines were selected for display. The networ k diagram may load slowly and be difficult to use when displaying large numbers of hosts or virtual machines.\n\nDo you want to continue?
13626 The specified virtual network does not exist. Verify the virtual network name by refreshing the Host Properties di alogue box, go to the Hardware tab and click the Virtual Network option. Then try the operation again.

Command Line Interface: Run Get-VirtualNetwork and ensure that the virtual network is on the list.
13627 If network adapter %FriendlyName; is bound to this virtual network, there will be no physical network adapters dedicated to managing host communications. This may prevent Virtual Machine Manager from managing this host over the network.\n\n Do you want to continue?
13628 Virtual Machine Manager has detected more than one network adapter named %Friendl yName; on host %VMHostName;. Information collected about this adapter by VMM may be inaccurate. To verify the network a daptor's configuration, use Hyper-V Manager.
13629 Virtual Machine Manager has detected more than one network adapter with the same name. For more details, please refresh host %VMHostName;, and then refer to the job history entry for the host refresh job.
13630 Virtual Machine Manager has detected more than one network adapter with the same name. For more details, please refresh host cluster %HostClusterName; and refer to the job history entry for the host c luster refresh job.
13631 Unable to assign the name (%Name;) to this logical network because this name is a lready in use. Specify a unique name for the logical network, and then try the oper ation again.
13632 Unable to find the specified logical network. The logical network name may be inc orrect, or the logical network may have been deleted. Verify that the logical network name is correct and that the logical network exists on the Virtual Machine Manager management server.
13633 VMM is unable to assign the specified name (%Name;) to the network site because a nother network site in this logical network already has that name. Specify a unique name for the logical network definition, and then t ry the operation again.
13634 VMM is unable to find the specified network site. The network site name may be in correct, or the network site may have been deleted. Verify that the network site name is correct and that the network si te exists on the Virtual Machine Manager management server.
13635 Unable to find the specified IP subnet. The IP subnet may have been deleted. Verify that the IP subnet exists on the Virtual Machine Manager mana gement server.
13636 Unable to find the specified IP subnet-VLAN. The IP subnet-VLAN may have been del eted. Verify that the IP subnet-VLAN exists on the Virtual Machine Manager management server.
13637 The specified list contains overlapping subnets: %Subnet;. Specify a set of non-overlapping IP subnets, and then try the operat ion again.
13638 Unable to assign the subnet %Subnet; because it overlaps with an existing subnet. Specify a non-overlapping subnet, and then try the operation again.
13639 The format of the subnet string: %Subnet; is invalid. The expected format is: "{I Pv4 address| IPv6 address}/(subnet mask prefix length)". Specify the subnet in the correct format.
13640 The specified host groups contain overlapping host groups. Specify a non-overlapping set of host groups, and then try the opera tion again.
13641 The specified subnet prefix must be between the starting and ending values for th e range.\nStarting value: %RangeStart;\nEnding value: %RangeEnd; Specify a suitable subnet prefix.
13642 Unable to remove the subnet (%Subnet;) because one or more static IP address pool s are associated with it. Remove all static IP address pools associated with the subnet and tr y the operation again.
13643 The specified list of logical networks contains duplicate elements. Specify a list of unique logical networks, and then try the operatio n again.
13644 The specified list of subnet VLANs contains duplicate elements. Specify a list of unique subnet VLANs, and then try the operation ag ain.
13645 The definition for the subnet (%Subnet;) and VLAN (%VlanId;) could not be found f or the host group (%Name;). Define the subnet and VLAN in a logical network definition.
13646 The specified IP address range is not valid.\nStarting value: %RangeStart;\nEndin g value: %RangeEnd; 1. Specify an end address for the range that is greater or equal tha n the start address.\n\n2. Ensure that the address range is included in the specified subnet.
13647 The specified IP address (%IPAddress;) is not of the expected address protocol ve rsion (IPv4 or IPv6). Specify an IP address of the correct address protocol version.
13648 The specified IP address set (%IPAddressSet;) is not in a valid format. 1. Specify a comma separated list of IP address ranges of the format : IP address 1 - IP address 2\n\n2. Make sure all addresses are of the same type (IPv4 or IPv6).
13649 The range specified for the static IP address pool overlaps with the range of add ress managed by an existing static IP address pool. Specify a non-overlapping IP address range, and then try the operati on again.
13650 Unable to assign the static IP address pool the name (%Name;) because another sta tic IP address pool already has that name within the network site. Specify a unique name for the static IP address pool, and then try t he operation again.
13651 Unable to find the specified MAC address pool. The MAC address pool may have been deleted. Verify that the MAC address pool exists on the Virtual Machine Manag er management server.
13652 Unable to assign the MAC address pool name (%Name;) because another MAC address p ool already has that name. Specify a unique name for the MAC address pool.
13653 The specified range of the MAC address pool overlaps with ranges of existing MAC address pools. Specify a MAC address range that does not overlap ranges of existing MAC address pools.
13654 The specified input (%ComputerName;) is not a valid Internet name. Make sure the name contains only valid characters (letters and numbe rs, hyphen and period).
13655 The WINS server address: "%IPAddress;" is not a valid IP address. Enter a valid IP address, and then try the operation again.
13656 The DNS server address: "%IPAddress;" is not a valid IP address. Enter a valid IP address, and then try the operation again.
13657 The virtual IP (VIP) address range conflicts with a default gateway or with a res erved IP address for the static IP address pool. Make sure the virtual IP (VIP) address range does not contain a defa ult gateway or a reserved IP address and then try again.
13658 The specified reserved IP addresses are outside of the range that is managed by t he static IP address pool. Specify addresses that are within the managed address range.
13659 The specified virtual IP (VIP) addresses are outside of the range that is managed by static IP address pool. Specify addresses that are within the managed address range.
13660 The address protocol version of the reserved IP addresses does not match the addr ess protocol version of the static IP address pool. Specify IP addresses of the correct address protocol version.
13661 The address protocol version of the virtual IP (VIP) addresses does not match the address protocol version of the static IP address pool. Specify IP addresses of the correct address protocol version.
13662 The NetBIOS and WINS servers are not valid on IPv6 static IP address pools. Do not enable Net BIOS or set WINS servers on an IPv6 static IP addr ess pool.
13663 The specified IP subnet is not of the expected address protocol version (IPv4 or IPv6). Specify an IP subnet of the correct address protocol version.
13664 Multiple VLANs are assigned to a host network adapter in ACCESS VLAN mode. Specify the subnet VLAN that should be assigned to the host network adapter.
13665 VMM cannot specify both VLAN and logical network configuration at the same time. Specify either the VLAN or logical network configuration.
13666 The specified address is outside of the address range managed by the address pool .\nSpecified address: %Address;\nRange starting address: %RangeStart;\nRange ending address: %RangeEnd;\nIP address po ol: %Name; Specify an address within the range managed by the pool.
13667 The specified address (%IPAddress;) is within a reserved address range of an addr ess pool (%Name;). Specify an address within the available range by the pool.
13668 The specified address (%IPAddress;) is already allocated by an IP address pool (% Name;). Specify an address that is not already allocated by the address pool .
13669 All addresses in the address pool (%Name;) have been used. Expand the address pool or use another address pool.
13670 No static IP address pools are available from which to allocate the requested add resses. Create a static IP address pool.
13671 VMM is unable to delete the static IP address pool (%Name;) because it has alloca ted IP addresses. Please return all the allocated IP addresses to the pool by using th e Revoke-SCIPAddress cmdlet, and then retry this operation. You can retrieve the allocated addresses by using the Get-S CIPAddress cmdlet with the -StaticIPAddressPool parameter.
13672 Unable to find the specified allocated IP address. The allocated IP address may h ave been deleted. Verify that the allocated IP address exists on the Virtual Machine M anager management server.
13673 All virtual IP (VIP) addresses in the address pool (%Name;) have been used. Expand the set of available virtual IP (VIP) addresses or use anothe r address pool.
13674 Unable to delete the MAC address pool (%Name;) because it has allocated MAC addre sses. Please return all the allocated MAC addresses to the pool by using t he Revoke-SCMACAddress cmdlet, and then retry this operation. You can retrieve the allocated addresses by using the Get -SCMACAddress cmdlet with the -MACAddressPool parameter.
13675 Unable to find the specified allocated MAC address. The allocated MAC address may have been deleted. Verify that the allocated MAC address exists on the Virtual Machine Manager management server.
13676 The specified address (%Address;) is not part the virtual IP (VIP) address set fo r the address pool (%Name;). Specify an address within the virtual IP (VIP) address set of the po ol.
13677 Unable to find the specified load balancer. The load balancer may have been delet ed. Verify that the load balancer exists on the Virtual Machine Manager management server.
13678 Unable to find the specified load balancer model settings. The load balancer mode l settings may have been deleted. Verify that the load balancer model settings exist on the Virtual Ma chine Manager management server.
13679 No configuration provider exists for the load balancer. Add configuration provider for the load balancer and try again.
13680 Multiple configuration providers match for the specified load balancer. Specify which configuration provider to use for the load balancer.
13681 The configuration provider specified for the load balancer does not match. The co nfiguration provider type, manufacturer and model must match the load balancer. Specify the correct configuration provider for the load balancer and try again.
13682 A configuration provider must be specified for this load balancer manufacturer an d model. Specify the configuration provider to user for this load balancer ma nufacturer and model.
13683 The load balancer (%Address;) is already being managed by Virtual Machine Manager . Specify a different load balancer address and then try the operation again.
13684 The configuration provider for load balancer reported an error. Correct the error and try again.
13685 The configuration provider for load balancer returned an unexpected result. Check the logs and correct the issue, and then try again.
13686 VMMM is unable to find the specified load balancer virtual IP (VIP) address templ ate. The load balancer VIP address template may have been deleted. Verify that the load balancer virtual IP (VIP) address template exis ts on the Virtual Machine Manager management server.
13687 VMM is unable to assign the virtual IP (VIP) address template name (%Name;) becau se another VIP address template already has that name. Specify a unique name for the virtual IP (VIP) address template.
13688 VMM is unable to find the specified load balancer virtual IP (VIP) address. The l oad balancer VIP address may have been deleted. Verify that the load balancer virtual IP (VIP) address exists on the Virtual Machine Manager management server.
13689 Virtual IP (VIP) address persistence is enabled, but no persistence is specified. Specify a virtual IP (VIP) address persistence.
13690 Insufficient parameters to create a virtual IP (VIP) address. Specify all necessary parameters including protocol and load balanci ng method, or provide a virtual IP (VIP) address template.
13691 A virtual IP (VIP) address with the specified name (%VIPName;) or address (%IPAdd ress;) already exists on the load balancer (%Name;). Specify a different name or IP address and try again.
13692 Unable to find the specified load balancer virtual IP (VIP) member. The load bala ncer virtual IP (VIP) member may have been deleted. Verify that the load balancer virtual IP (VIP) member exists.
13693 Unable to add a virtual IP (VIP) member with the specified address (%Address;) an d port (%Port;) because the VIP member ('%VIPName;') already exists. Specify a different address and/or port for the new virtual IP (VIP) member.
13694 Cannot specify both the "-MakeGeneric" and the load balancer manufacturer or mode l parameters. Specify either the "-MakeGeneric" parameter or the load balancer man ufacturer and model.
13695 Cannot specify both "-DisablePersistence" and a persistence parameter. Specify either the "-DisablePersistence" parameter or a persistence.
13696 A non-generic virtual IP (VIP) address template requires both load balancer manuf acturer and model. Specify both the load balancer manufacturer and model or neither.
13697 The virtual IP (VIP) address protocol name cannot be null or empty. Specify a valid name for the virtual IP (VIP) address protocol.
13698 The virtual IP (VIP) address persistence name cannot be null or empty. Specify a valid name for the virtual IP (VIP) address persistence.
13699 The virtual IP (VIP) address load balancing method name cannot be null or empty. Specify a valid name for the virtual IP (VIP) address load balancing method.
13700 The specified value (%Value;) is not a valid default gateway metric value. Specify a value between 1 and 9999.
13701 The list of DNS servers contains the duplicate address (%Address;). Remove duplicate entries from the list and try again.
13702 The list of WINS servers contains the duplicate address (%Address;). Remove duplicate entries from the list and try again.
13703 The list of DNS search suffixes contains the duplicate DNS search suffix (%Value; ). Remove duplicate entries from the list and try again.
13704 The list of default gateways contains the duplicate address (%Address;). Remove duplicate entries from the list and try again.
13705 The HTTPS certificate subject name is required and must not be empty if the load balancer protocol specifies HTTPS termination. Specify the HTTPS certificate subject name and try again.
13706 The host network adapter (%Name;) is not associated with any logical networks. Specify the logical networks to which the host network adapter has a ccess.
13707 The host network adapter (%Name;) is associated with a logical network (%LogicalN etworkName;), but there are no corresponding subnets or VLANs defined for this logical network to which the virtualizat ion host (%VMHostName;) has access. Specify one or more subnets or VLANs for the logical network (%Logi calNetworkName;) in a network site to which the virtual machine host (%VMHostName;) has access.
13708 There is no subnet or VLAN connectivity for the logical network (%LogicalNetworkN ame;) on the host network adapter (%Name;). Specify the subnets or VLANs to which the host network adapter has a ccess.
13709 VLANs (%VlanIds;) are missing from the host network adapter (%Name;) for one or m ore explicitly specified subnets or VLANs. Update the network configuration on the host network adapter.
13710 The host network adapter (%Name;) only has access to a partial list of the implie d subnets or VLANs for the logical network (%LogicalNetworkName;) to which the host (%VMHostName;) has access. Update the network configuration on the host network adapter.
13712 The virtual IP (VIP) address (%VIPName;) is not present on the load balancer (%Na me;). The VIP address may have been deleted from the load balancer. Verify that the virtual IP (VIP) address exists on the load balancer .
13713 A certificate matching the specified subject name (%CertificateSubjectName;) was not found on the load balancer (%Name;). Verify that the certificate exists on the load balancer.
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 aga in.
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.
13804 Access to the cluster %ComputerName; was denied. Ensure that the specified credentials have access to query cluster r esources and 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 clus ter, you might need to wait for the cluster name to be added to Active Directory Domain Services.
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 o f 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.
13809 Unable to run WMI query on cluster %ComputerName;. Ensure that the specified computer name is a cluster name and that t he cluster service is properly installed and running.
13810 Cannot remove host %ComputerName; because it is a part of host cluster %HostClust erName;. Removing the entire cluster will remove all of its hosts. BLANK
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.
13812 Virtual network %FriendlyName; already exists on the highly available host. BLANK
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 %Frien dlyName;. Ensure that the target resource pool belongs to the same computer re source 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 c redentials have administrative rights, and then try the operation again.
13816 Virtual Machine Manager detected that the library server %ComputerName; is a clus tered file server. Virtual Machine Manager will install agent on all the nodes of the failover cluster that is hosting this file server.
13817 Virtual Machine Manager detected that the library server %ComputerName; is a fail over cluster node. If you want to add clustered library server, you should specify the network name of the clustered li brary server. Are you sure you want to add the failover cluster node as a standalone library server?
13916 Not all of the host cluster nodes have processors that are mutually compatible.
13917 The following virtual machines have more processors than one or more of the hosts in the host cluster: %NameList;.
13918 Cannot assign virtual machine %VMName; to a VMware resource pool because the virt ual machine is not on a VMware ESX host. BLANK
13919 Specified failure node reserve (%ParameterValue;) exceeds the %MaxLimit; limit fo r host cluster %HostClusterName; (total nodes in cluster- 1). Specify a failure node reserve less than or equal to %MaxLimit;.
13920 The discovered host cluster (%HostClusterName;) will not be added to Virtual Mach ine Manager, because a cluster with the same name already exists.
13921 The highly available virtual machine (%VMName;) is not supported by VMM because o ne or more of its network adapters is not configured correctly. Ensure that all of the virtual network adapters are either disconnec ted or connected to highly available virtual networks.
13922 The highly available virtual machine (%VMName;) is not supported by VMM because o ne or more of its network adapters is not configured correctly. Ensure that all of the virtual network adapters are either disconnec ted or connected to highly available virtual networks. Additionally, each port group to which the virtual machine is co nnected must be present on each of the nodes of the cluster.
13923 The highly available virtual machine (%VMName;) is not supported by VMM because i ts cluster resource group is not configured correctly. Ensure that the resource group only contains a single virtual machin e resource, a single virtual machine configuration resource, and zero or more disk resources all belonging to this virt ual machine.
13924 The highly available virtual machine (%VMName;) is not supported by VMM because t he virtual machine uses non-clustered storage. Ensure that all of the files and pass-through disks belonging to the virtual machine reside on highly available storage.
13925 Host cluster %HostClusterName; cannot be removed directly from Virtual Machine Ma nager 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 because not all of the nod es could be contacted. Highly available storage and virtual network information reported for this cluster might be inac curate. Ensure that all the nodes are online and do not have Not Responding status in Virtual Machine Manager. Then refresh the host cluster again.
13927 Host cluster %HostClusterName; was moved, renamed, or deleted outside Virtual Mac hine Manager. Verify the name of the cluster you want to refresh and then try the operation again.
13928 Highly available virtual machine %VMName; is offline on host %VMHostName;. 1. Ensure that the virtual machine has not been removed from host %V MHostName; by using Hyper-V Manager.\n2. Ensure that all of the resources in cluster resource group %GroupName; are onl ine by using Failover Cluster Manager.
Revert to this revision