Virtual Machine Manager Error Codes (13000-13499)

Links to other error code pages can be found on the Virtual Machine Manager (VMM) 2008 R2 Error Codes page.

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

Code	Message	Recommended Action (in product)	Additional Troubleshooting Information
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.
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.
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.
13206	Virtual Machine Manager cannot locate the boot or system volume on virtual machine %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 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 http://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 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 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.	Run the Convert Physical Server Wizard again, and choose the Offline Conversion option on the Volume Configuration page.
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 computer %ServerName;.	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 server, create a DWORD registry key at HKLM\Software\Microsoft\Microsoft System Center Virtual Machine Manager 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 machine %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 %ServerName;.	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 hard 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 server is unable to convert %ServerName; because required files are missing.	Copy the file %FileName; to "%FolderPath;" on the Virtual Machine Manager 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 %ServerName;, or on the %OSName; (%Language;, %OSPlatform;) installation media.n/ If %FileName; is not available, locate %FileName2; (Version: %FileVersion;) on the installation media, copy the file to "%FolderPath;", and then run the Add-Patch 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.