System Center 2012 – Virtual Machine Manager (VMM) Error Codes [3000-3499]

System Center 2012 – Virtual Machine Manager (VMM) Error Codes [3000-3499]

Use Ctrl-F to find a specific code.

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

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

 

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

 

Code

Message

Recommended Action (in product)

Additional Troubleshooting Information

3100

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

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

3101

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

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

3102

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

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

3103

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

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

3105

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

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

3106

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

Try the operation again.

3107

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

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

3108

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

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

3109

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

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

3110

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

Try the operation again.

3111

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

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

3112

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

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

3113

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

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

3114

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

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

3115

The snapshot creation set on %ComputerName; was canceled.

Try the operation again.

3116

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

Try the operation again.

3117

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

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

3118

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

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

3119

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

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

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.

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

3121

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

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

3122

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

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

3123

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

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

3124

The -IDE and -SCSI parameters are mutually exclusive.

Resolve the conflict, and then try the operation again.

3125

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

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

3126

The parameters -Name, -Description, -StartVM, -MemoryMB, -ProcessorCount, -Proces sorType, -CPURelativeWeight, -DriverPath, -RunAsSystem, -RunAsUserCredential, -StartAction, -StopAction, -DelayStartSec onds, -UseHardwareAssistedVirtualization can only be specified in a standalone or final JobGroup job.

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

3127

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

Try the operation again.

3128

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

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

3129

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

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

3130

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

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

3131

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

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

3132

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

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

3133

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

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

3134

An internal agent error has occurred on %ComputerName;.

Try the operation again.

3135

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

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

3136

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

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

3137

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

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

3138

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

Run Setup again to install the missing files.

3139

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

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

3140

(Internal error.)

3141

(Internal error.)

3142

Failed to fully clean up %ComputerName;.

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

3143

(Internal error.)

3144

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

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

3145

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

If the configuration of the source machine has recently changed, gat her system information again by restarting the Convert Physical Server wizard.

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

3146

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

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

3147

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

Specify a value for the missing parameter -Credential.

3148

The volume %VolumeDriveLetter; selected for physical-to-virtual imaging is not accessible from Windows PE. This is usually caused by missing or incorrect storage drivers. %ComputerName; may now need t o 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.

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

3149

The -Fixed and -Dynamic parameters are mutually exclusive.

Resolve the conflict, and then try the operation again.

3150

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

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

3151

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

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

3152

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

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

3153

The volume %VolumeDriveLetter; of source computer %ServerName; cannot be extended to the size of the resulting VHD because the file system on the volume does not support this operation. The VHD is extended and will have unallocated space.

3154

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

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

3155

Cannot connect to the local WMI service.

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

3156

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

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

3157

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

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

3158

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

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

3159

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

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

3160

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

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

3200

The patch file %FileName; cannot be found.

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

3201

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

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

3202

The patch file %FileName; format is not valid.

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

3203

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

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

3204

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

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

3205

No files were added to the patch cache.

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

3206

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

%ServerName; will be converted using an offline conversion. If you w ant to perform an online conversion exclude the volume %VolumeDriveLetter; in the Volume Configuration page and choose Online conversion in Conversion Options.

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

3207

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

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

3208

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

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

3209

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

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

3210

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

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

3211

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

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

3212

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

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

3213

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

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

3214

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

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

3215

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

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

3216

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

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

3217

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.

3218

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

Selected machine %ServerName; cannot be virtualized.

3219

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

Specify a host located in a trusted domain, then try the operation a gain.

3220

%ServerName; cannot be converted. Boot volume %VolumeDriveLetter; must be attache d as the first hard drive for the virtual machine to start up.

Modify the bus assignments to create space for the boot volume.

3221

The selected machine %ServerName; will be virtualized without CD\DVD drives. The channels are not available on the IDE bus for the addition of a DVD device to emulate the source machine configuration.

Modify the bus assignments or volume selection to create space on the IDE bus for the CD or DVD drive.

3222

The selected machine %ServerName; cannot be virtualized. The channels are not ava ilable on the IDE or SCSI buses for the addition of volume %VolumeDriveLetter;. Note that non-boot volumes always follow the boot volume during bus assignment.

Reduce the number of channels selected for migration volumes or change the bus assignment of the boot volume to fit volume %VolumeDriveLetter;.

3223

Boot volume %VolumeDriveLetter; must be attached to the IDE bus or SCSI bus 0 for the machine to boot up.

The selected machine %ServerName; cannot be virtualized. Modify the bus assignments for the boot volume which must be located on the first hard disk of the virtual machine, and then try t he operation again.

3224

VMM is unable to locate the source computer %ComputerName; in Active Directory Do main Services.

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

3225

The Windows Automated Installation Kit is not installed.

Install Windows Automated Installation Kit version 1.0.0.0 on %Compu terName; and then try the operation again.

3226

Unable to run job group because an -Offline, -DriverPath, or -Shutdown parameter is specified on a job other than the final job. These parameters can only be specified in a standalone job or in the fi nal job in a job group.

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

3227

Physical-to-virtual conversion failed because a -DriverPath or -Shutdown parameter was specified without specifying an -Offline parameter.

Specify a value for the missing parameter -Offline or remove -Driver Path, -Shutdown parameters to enable online physical-to-virtual conversion, and then try the operation again.

3228

Online physical-to-virtual conversion cannot be performed for the operating system %OperatingSystem; on the source computer %ServerName;.

3229

Selected machine %ServerName; cannot be virtualized.

For more information, view details for this job.

3230

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

Download the update %FriendlyName; for %OSName; (%Language;, %OSPlat form;) from Windows Update (Support Link: %URL;) to "%FolderPath;" on the Virtual Machine Manager management server and then run the Add-Patch cmdlet.

3231

Unable to convert the physical server. Virtual Machine Manager requires a host wi th Hyper-V.

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

3232

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

Ensure that this service can be started on %ServerName; and check th e Windows Event Log for troubleshooting information. Try the operation again.

3233

Failed to extract patch file %FileName;.

Verify that the patch file is extractable, and then try the operatio n again.

3234

Failed to copy file %SourceLocation; from source server %ComputerName; to folder %DestinationLocation; on the VMM management server.

After resolving the problem, retry the operation or copy the files r equired for virtualization manually. Then use the add-patch cmdlet to populate the patch cache.

3235

Failed to extract patch file %FileName;. This patch applies to the operating system type or platform that is unsupported for virtualization.

Ensure that the patch file applies to 32-bit platform of an operatin g system that is supported for virtualization, and then try the operation again.

3236

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

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

3237

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

Copy %FileName; to "%FolderPath;" on the Virtual Machine Manager man agement server. The files are archived in %FileName;, which is located on the %OSName; (%Language;, %OSPlatform;) insta llation media. And then run the Add-Patch cmdlet.

3238

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

Download the update %FriendlyName; for %OSName; (%Language;, %OSPlat form;) from Windows Update (Support Link: %URL;) to "%FolderPath;" on the Virtual Machine Manager management server and then run the Add-Patch cmdlet.

3240

VMM discovered that a restart is pending after application of Microsoft updates o n the source computer %ServerName;.

Restart source computer %ServerName; to enable conversion of this ma chine. Then try the operation again.

3241

The job cannot be restarted.

If a more recent conversion job of the source machine %ServerName; exists, restart that job instead. Otherwise, restart the conversion from the beginning.

3242

The converted virtual machine may not function correctly because it will not match the configuration of the source VMware virtual machine %FileName;.

Remove or supply a solution.

3243

Virtual Machine Manager is unable to update the operating system of the source VM ware virtual machine %VMName;. The operating system, file system, or disk layout is not recognized.

The converted virtual machine may not start or operate correctly. Fo r the list of supported Windows operating systems go to http://go.microsoft.com/fwlink/?LinkId=117761.

3244

Virtual machine %VMName; is not a valid virtual machine for V2V conversion.

Specify a valid virtual machine for V2V conversion and confirm that the virtual machine is shut down.

3402

The email address is not valid.

Ensure that the email address is correct.

3403

The reserve amount is not valid.

The percentage reserved must be between 0 and 100.

3404

The reserve amount is not valid.

The reserve amount must be greater than or equal to 0 and a valid integer.

3405

The event log for Virtual Machine Manager is missing or is not accessible.

Reinstall the Virtual Machine Manager to access the event log.

3406

The account %UserName; is not a domain account.

Enter a valid domain account name or click Add to select one, and then try the operation again.

Command Line Interface: Enter a valid domain account name.

3407

The entered URL is not valid.

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

Command Line Interface: Enter a valid URL

3415

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

Review the command and then try the operation again.

3450

Not able to connect to the reporting server.

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.

3452

The folder containing Virtualization Reports was not found on the reporting serve r.

Ensure that the Microsoft Virtualization Reports management pack is installed and the reports are present under Microsoft.Virtualization.Reports folder.

3453

Unable to verify the connection to the reporting server %ServerName;.

Ensure that System Center Virtual Machine Manager 2008 R2 Management Pack and its reports are installed on the Operations Manager server. To download the management pack, go to http://go. microsoft.com/fwlink/?LinkID=85858.

 

Leave a Comment
  • Please add 1 and 1 and type the answer here:
  • Post
Wiki - Revision Comment List(Revision Comment)
Sort by: Published Date | Most Recent | Most Useful
Comments
Page 1 of 1 (1 items)
Wikis - Comment List
Sort by: Published Date | Most Recent | Most Useful
Posting comments is temporarily disabled until 10:00am PST on Saturday, December 14th. Thank you for your patience.
Comments
Page 1 of 1 (1 items)