troubleshooting vmm

Troubleshooting VMM

Troubleshooting VMM

How to Troubleshoot VMM / Configuration Settings Checked by the VMMCA Page 1

How to Troubleshoot VMM..................................................................................................................... 4

Configuration Settings Checked by the VMMCA ................................................................................. 4

Configuration Settings Checked by the VMMCA ..................................................................................... 4

You can use the VMMCA to check the following pre-installation configuration settings: ................. 4

You can use the VMMCA to check the following post-installation configuration settings: ................ 5

Troubleshooting Setup Issues ................................................................................................................. 6

VMM Server Installation Fails with Error 205 .................................................................................... 6

Possible causes ................................................................................................................................ 6

Solutions .......................................................................................................................................... 6

VMM Server Installation Fails with Error 319 .................................................................................... 6

Possible causes ................................................................................................................................ 6

Solutions .......................................................................................................................................... 6

VMM Server Installation Fails with Error 2917 .................................................................................. 6

Possible causes ................................................................................................................................ 6

Solutions .......................................................................................................................................... 6

Re-installing VMM After Renaming the Computer Fails with Error 257 ............................................ 7

Possible causes ................................................................................................................................ 7

Solutions .......................................................................................................................................... 7

Remote SQL Server Installation Fails with Error 404 ......................................................................... 7

Possible causes ................................................................................................................................ 7

Solutions .......................................................................................................................................... 7

Cannot Uninstall the VMM Self-Service Portal .................................................................................. 7

Possible causes ................................................................................................................................ 7

Solutions .......................................................................................................................................... 7

Troubleshooting Host Cluster Issues in VMM ......................................................................................... 8

Unsupported Cluster Configuration status for a virtual machine ....................................................... 8

Possible causes ................................................................................................................................ 8

Solutions .......................................................................................................................................... 8

Troubleshooting Virtual Machine Issues ................................................................................................. 9

No Option to Use SAN Migration ...................................................................................................... 10

Possible cause (or causes) ............................................................................................................. 10

Solution (or solutions) ................................................................................................................... 10

Troubleshooting Virtual Machine Conversion Issues ............................................................................ 10

Communication Issues (Offline P2V) ................................................................................................. 10



Volume Shadow Copy Service Issues (P2V) ....................................................................................... 10


Troubleshooting VMM



Agent Issues (P2V) ............................................................................................................................. 11



Patch or Driver Issues (P2V) .............................................................................................................. 11



Less than 512 MB RAM (offline P2V only) ......................................................................................... 11



Offline P2V ......................................................................................................................................... 11



Firewall Issues (P2V) .......................................................................................................................... 11



BITS transfer fails (P2V) ..................................................................................................................... 12



Error with a Host in Limited State (V2V) ........................................................................................... 12



Missing Hosts (V2V) ........................................................................................................................... 12



Communication Issues (V2V) ............................................................................................................. 12



Updates ............................................................................................................................................ 13



Permissions Issues (V2V) ................................................................................................................... 13



Unrecognized .vmx or .vmdk File Format (V2V) ................................................................................ 13



Operating System Issues ................................................................................................................... 13

Troubleshooting VMM




VMM 2008 Error Codes ......................................................................................................................... 14

User Interface Error Messages .......................................................................................................... 14

Error Messages .............................................................................................................................. 14

Command-Line Interface Error Messages ......................................................................................... 42

Error Messages .............................................................................................................................. 42

Troubleshooting Operations Manager, PRO, and Reporting Issues in VMM ...................................... 116

Configure Operations Manager Setup option is not completed successfully ................................. 116

Possible causes ............................................................................................................................ 116

Solutions ...................................................................................................................................... 117

Access denied when specifying the Operations Manager server for VMM .................................... 117

Possible causes ............................................................................................................................ 117

Solution........................................................................................................................................ 117

Troubleshooting VMM Cmdlet Issues ................................................................................................. 118

The Add-Patch cmdlet does not run on a VMM 2008 server installed on a Windows Server 2008

computer ......................................................................................................................................... 118

Possible cause (or causes) ........................................................................................................... 118

Solution (or solutions) ................................................................................................................. 118

Troubleshooting VMM


How to Troubleshoot VMM

This section provides information about tools and methodologies available to help you troubleshoot

issues that you might experience with Virtual Machine Manager (VMM) 2008 or Virtual Machine

Manager 2008 R2.

Configuration Settings Checked by the VMMCA

Virtual Machine Manager 2008 and 2008 R2 Configuration Analyzer (VMMCA) is a diagnostic tool

that you can use to evaluate important pre-installation or post-installation configuration settings for

computers that might serve or are serving Virtual Machine Manager (VMM) roles or other VMM

functions. The VMMCA is a very useful diagnostic tool for troubleshooting VMM issues. This topic

describes all the configuration settings that you can check by using the VMMCA.

To download the VMMCA, go to System Center Virtual Machine Manager 2008 and 2008 R2

Configuration Analyzer (http://go.microsoft.com/fwlink/?LinkID=100597).

Configuration Settings Checked by the

VMMCA

Virtual Machine Manager 2008 and 2008 R2 Configuration Analyzer (VMMCA) is a diagnostic tool

that you can use to evaluate important pre-installation or post-installation configuration settings for

computers that either might serve or are serving Virtual Machine Manager (VMM) roles or other

VMM functions. You should use this version of the VMMCA with VMM 2008 and VMM 2008 R2 only.

To download the Virtual Machine Manager 2008 and 2008 R2 Configuration Analyzer, go to System

Center Virtual Machine Manager 2008 and 2008 R2 Configuration Analyzer

(http://go.microsoft.com/fwlink/?LinkID=100597).

You can use the VMMCA to check the following pre-

installation configuration settings:

• The correct version of Windows Remote Management (WinRM) is installed on the

prospective VMM server.

• The domain functionality level appropriately set for the prospective VMM server.

• If a computer restart is required on the prospective VMM server.

• The prospective VMM database is accessible.

• Windows PowerShell 1.0 is installed for the prospective VMM Administrator Console and

VMM Self-Service Portal.

• Internet Information Services (IIS) is enabled and properly configured on the prospective

VMM Self-Service Portal.

• The available memory is not less than the required minimum amount for the prospective

VMM server, VMM Administrator Console, and VMM Self-Service Portal.

• The processor speed is not less than the required minimum processor speed for the

prospective VMM server, VMM Administrator Console, and VMM Self-Service Portal.

Troubleshooting VMM

Configuration Settings Checked by the VMMCA / You can use the VMMCA to check the

following post-installation configuration settings: Page 5

You can use the VMMCA to check the following post-

installation configuration settings:

• Recommended VMM update 961983 is installed on the VMM server.

• Recommended Windows Remote Management (WinRM) update 971244 is installed on the

VMM server.

• The virtual machine update interval exceeds the recommended interval on the VMM server.

• The host update interval exceeds the recommended interval on the VMM server.

• The virtual machine properties update interval is within the recommended range on the

VMM server.

• Reporting is configured on the VMM server.

• Computers are being monitored by System Center Operations Manager on the VMM server.

• The VMM database is accessible.

• The number of jobs on the VMM server is less than the recommended number.

• The number of hosts on the VMM server is less than the recommended number.

• The number of hosts in a single host group on the VMM server is less than the recommended

number.

• The correct version of Windows Remote Management (WinRM) is installed on the specified

hosts.

• The required updates of Hyper-V (updates 950050 and 956589) and BITS (update 956774)

are installed on the specified hosts.

• Recommended Windows Management Instrumentation (WMI) updates 958124 and 954563

are installed on the specified hosts.

• Recommended Windows update 955805 is installed on the specified hosts.

• The following recommended Hyper-V updates are installed on the specified hosts:

• 952247

• 956697

• 957967

• 958184

• 959978

• 971677

• Virtual Server R2 SP1 is installed on the specified hosts that are running Windows

Server 2003.

• The specified Hyper-V hosts that are being managed by VMM 2008 R2 are running Windows

Server 2008 SP2 or later.

• The Windows Management Instrumentation (WMI) virtualization store is in a healthy state

on the specified hosts.

• The virtualization software services are running on the specified hosts.

• The Windows Remote Management (WinRM) Service is running on the specified hosts.

• All removable writeable disks are initialized on the specified hosts.

• An up-to-date version of the HP MPIO DSM driver is installed on the specified hosts.

• VMM can access the Admin$ share on the specified hosts.

• No mounted VHD exists on the specified hosts.

• Recommended Failover Cluster Management console updates 951308 and 958065 are

installed on the specified clustered hosts.

• Highly available virtual machines are not in an unsupported cluster configuration state.

• The specified VMware VirtualCenter servers are in a healthy state.

• The Volume Disk Snapshot:Volume Shadow Copy Service is running on the specified target

computers for P2V conversion.

Troubleshooting VMM

Troubleshooting Setup Issues / VMM Server Installation Fails with Error 205 Page 6

Troubleshooting Setup Issues

This topic provides guidance for troubleshooting issues with installing Virtual Machine Manager 2008

(VMM) and VMM 2008 R2 components.

VMM Server Installation Fails with Error 205

Possible causes 1. The SQL Server name that you entered has more than 15 characters.

2. The 32-bit version of ASP.NET is installed on a 64-bit computer.

Solutions 1. Ensure that the SQL Server name does not contain more than 15 characters, and then try the

operation again.

2. Switch from the 32-bit version of ASP.NET to the 64-bit version of ASP.NET 2.0 according to

the instructions at http://go.microsoft.com/fwlink/?LinkId=98566.


Possible causes 1. A default VMM database might already exist on this computer.

2. Disk quota management might be enabled and enforced.

Solutions 1. Either delete the existing VMM database files and then run Setup again or run Setup again

and use a unique name for the VMM database. By default, the VMM data file is named

VirtualManagerDB.mdf and the log file is named VirtualManagerDB_log.ldf. By default, the

VMM database files are located in the %SYSTEMDRIVE%\Program Files (x86)\Microsoft SQL

Server\MSSQL.1\MSSQL\Data folder.

2. Ensure that disk quota management is not enabled for the drive where the database is being

created.


Possible causes 1. The user name or password specified is not valid.

2. The credentials used to set up VMM do not belong to a domain with a two-way trust

relationship with the domain of the VMM server.

3. There are issues with either the Kerberos tickets or the Service Principal Name (SPN) for the

computer.

Solutions 1. For causes 1 and 2, log in by using credentials that are on the same domain as the VMM

server or with credentials on a domain that has a two-way trust relationship with the domain

of the VMM server, and then run Setup again.

Troubleshooting VMM

Troubleshooting Setup Issues / Re-installing VMM After Renaming the Computer Fails with

Error 257 Page 7

2. For cause 3, purge the Kerberos tickets by using kerbtray.exe, available at

http://go.microsoft.com/fwlink/?LinkId=93709. Then reset the SPN for the VMM server by

using setspn.exe with local system credentials. Setspn.exe is available from

http://go.microsoft.com/fwlink/?LinkId=93710. To start a local system process, use the

command at.exe. For example:

At.exe <time in the future, such as 10:26> /interactive cmd.exe

If this does not work, make the computer a member of a workgroup instead of a domain,

restart the computer, and then join the computer to the domain again.

Re-installing VMM After Renaming the Computer Fails with

Error 257

Possible causes SQL Server Setup fails if you rename the computer after uninstalling VMM and then try to reinstall

VMM. For more information about the underlying issue, see

http://go.microsoft.com/fwlink/?LinkId=88056.

Solutions Uninstall SQL Server and the full SQL Server instance from the computer, and then reinstall VMM.

Caution

This will result in the loss of the VMM database and all management and configuration

information.

Remote SQL Server Installation Fails with Error 404

Possible causes You entered the remote SQL Server location as an IP address during Setup.

Solutions To connect to the VMM database, you must manually modify the connection string using the

following steps:

1. In the registry, navigate to the following subkey:

\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine

Manager Server\Settings\Sql.

2. Right-click ConnectionString, click Modify, and then change the Server= value data by

deleting the IP address and replacing it with the computer name for the remote SQL Server.

Cannot Uninstall the VMM Self-Service Portal

Possible causes You cannot uninstall the Self-Service Portal if Internet Information Server (IIS) is not enabled.

Solutions

Troubleshooting VMM

Troubleshooting Host Cluster Issues in VMM / Unsupported Cluster Configuration status for

a virtual machine Page 8

If you receive the error “World Wide Web Publishing Service (W3SVC) is either not installed or

disabled. Please make sure that IIS is present on your computer,” enable IIS, and then try uninstalling

the VMM Self-Service Portal again.

Troubleshooting Host Cluster Issues in VMM

This topic provides guidance for troubleshooting issues with configuring and managing host clusters

to support highly available virtual machines (HAVMs) in Microsoft® System Center Virtual Machine

Manager 2008 (VMM) and System Center Virtual Machine Manager 2008 R2.

Unsupported Cluster Configuration status for a virtual

machine

Possible causes To view the reason why a highly available virtual machine has Unsupported Cluster Configuration

status, display the Hardware Configuration tab of the Virtual Machine Properties dialog box in the

VMM Administrator Console. Then, in the Advanced settings, click Availability. If the virtual machine

has Unsupported Cluster Configuration status, the Details area displays the error that placed the

virtual machine in that state.

The most common causes of Unsupported Cluster Configuration status for an HAVM are:

• The HAVM is on a non-Cluster Shared Volume (CSV) LUN that contains more than one virtual

machine.

• The virtual machine is using non-clustered storage.

• One or more virtual network adapters on the HAVM are not connected to a common virtual

network. Virtual networks that have identical settings are referred to as common virtual

networks. If the virtual networks on all hosts in the host cluster do not have identical

settings, a highly available virtual machine connected to such virtual network might lose

connectivity when it is migrated or fails over to another cluster node.

• The resource group for a Hyper-V virtual machine in a failover cluster that was created in

Windows Server 2008 contains resources in addition to the Virtual Machine, Virtual Machine

Configuration, and Physical Disk resources. These additional resources typically are third-

party resources that provide functionality such as replicating storage within a multi-site

cluster. For Hyper-V virtual machines managed by VMM, the virtual machine resource group

in a Windows Server 2008 failover cluster can only contain Virtual Machine, Virtual Machine

Configuration, and Physical Disk resources.

• In VMM 2008, an ISO image is attached to the HAVM. Often, the ISO image will be

c:\windows\system32\vmguest.iso. This issue was resolved in VMM 2008 R2.

• A VMware HAVM is connected to a port group that does not exist on all nodes of the host

cluster. On host clusters that VMM is managing, each port group must be configured on all

VMware ESX Server hosts in the cluster.

Solutions The following are solutions to the most common issues that cause an Unsupported Cluster

Configuration status for an HAVM:

• If you have configured highly available virtual machines in Hyper-V to share the same LUN,

and the LUN is not on a Cluster Shared Volume (CSV), you must update the virtual machine

configurations in Failover Cluster Manager (previously known, in Windows Server 2008, as

Troubleshooting VMM

Troubleshooting Virtual Machine Issues / Unsupported Cluster Configuration status for a

virtual machine Page 9

Failover Cluster Management) and Hyper-V so that each virtual machine resides on its own

unshared LUN.

• If the HAVM is stored on system drive C: or any disk that is not clustered, ensure that all files

and pass-through disks belonging to the virtual machine reside on clustered disks.

• Ensure that all virtual network adapters on the virtual machine are connected to common

virtual networks. Virtual networks that have identical settings are referred to as common

virtual networks. To find the common virtual networks for a host cluster, in the VMM

Administrator Console, view the Networks tab in the host cluster properties. To configure

virtual networks on the hosts, use the Networking tab in host properties. For more

information about configuring virtual networks, see How to Add or Modify Virtual Networks

on a Host (http://go.microsoft.com/fwlink/?LinkID=163453).

For a virtual network to be considered common by VMM and available to highly available

virtual machines on a host cluster, each virtual network in the host cluster must meet the

following requirements:

• The virtual network name must be identical on each host in the cluster. In

VMM 2008, virtual networks are recognized as common virtual networks only if the

cases of all letters in the network names match. This restriction was removed in

VMV 2008 R2. When it identifies common virtual networks, VMM 2008 R2 does not

evaluate the case of the letters in the network names.

• The host network adapters to which the virtual network is attached on each host in

the cluster must have the same location.

• The virtual network must have the same tag on each host in the cluster.

After you update the virtual network configurations on all nodes, refresh the cluster to ensure that

each virtual network is detected as common. Then check the Networks tab in the host cluster

properties to verify that the networks have been added to it.

• If the unsupported cluster configuration is caused by a resource group for a Hyper-V virtual

machine in a Windows Server 2008 failover cluster that includes resources other than the

Virtual Machine, Virtual Machine Configuration, and Physical Disk resources, install the

System Center Virtual Machine Manager 2008 Update (KB961983)

(http://go.microsoft.com/fwlink/?LinkId=182647) to resolve the issue. For a description of

the updates, see KB article 961983, Description of the hotfix rollup package for System

Center Virtual Machine Manager 2008: April 14th, 2009

(http://go.microsoft.com/fwlink/?LinkId=182648).

• If you are using VMM 2008, check whether the highly available virtual machine has an ISO

image attached (for example, c:\windows\system32\vmguest.iso). If an image is attached,

remove the image by using Hyper-V Manager. Then, in Virtual Machines view of the VMM

Administrator Console, refresh the virtual machine by using the Repair action. Right-click the

virtual machine, click Repair, and then click Ignore.

• For a VMware HAVM, ensure that the port group to which the virtual machine is connected

exists on all nodes of the host cluster.

Troubleshooting Virtual Machine Issues

The topics in this section provide guidance for troubleshooting issues with virtual machines when you

are using Virtual Machine Manager (VMM).

Troubleshooting VMM

Troubleshooting Virtual Machine Conversion Issues / No Option to Use SAN Migration Page 10

No Option to Use SAN Migration

When you try to use SAN to migrate a virtual machine, only the network option is available, and the

“SAN Explanation” indicates that there is more than one virtual machine on the same LUN.

Possible cause (or causes) In non-clustered cases, LUNs are migrated through masking that prevents simultaneous access to the

same LUN by multiple hosts.

Solution (or solutions) Deploy or create only one virtual machine per LUN.

Troubleshooting Virtual Machine Conversion

Issues

This topic provides guidance for troubleshooting issues during physical to virtual (P2V) and virtual to

virtual (V2V) conversions in Virtual Machine Manager (VMM) 2008 and VMM 2008 R2.

Before beginning a formal troubleshooting process, confirm that the source computer meets the

requirements described in P2V: Requirements for Physical Source Computers or V2V: Requirements

for Virtual Machines.

Communication Issues (Offline P2V)

Possible cause (or causes) In an offline P2V conversion, Virtual Machine Manager cannot contact the source computer after it

reboots into the Windows Preinstallation Environment (Windows PE).

Solution (or solutions) Determine whether Windows PE has storage or network drivers by examining the following log files

on the source computer while it is under Windows PE: x:\Windows\inf\setupapi.app.log and

x:\Windows\inf\setupapi.dev.log. You can also check the scvmm_winpe_setupapi.log file on the boot

volume of the source computer after it is rebooted to the original operating system from WinPE. Find

out which drivers are required, and copy the driver packages to the Driver Import folder in the VMM

installation root: for VMM 2008, %SYSTEMDRIVE%:\Program Files\Microsoft System Center Virtual

Machine Manager 2008\Driver Import, and for VMM 2008 R2, %SYSTEMDRIVE%:\Program

Files\Microsoft System Center Virtual Machine Manager 2008 R2\Driver Import.

Volume Shadow Copy Service Issues (P2V)

Possible cause (or causes) The Volume Shadow Copy Service (VSS) fails to take a snapshot of the contents of the source

computer's drives.

Solution (or solutions)

Troubleshooting VMM

Troubleshooting Virtual Machine Conversion Issues / Agent Issues (P2V) Page 11

View the system and application event logs for VSS errors on the source computer. If you cannot

correct them, try to do an offline P2V, which does not use VSS.

Agent Issues (P2V)

Possible cause (or causes) Installation of the VMM agent on the source computer fails.

Solution (or solutions) If the installation of the VMM agent on the source computer fails, view the VMM*.log on the source

computer to gather additional information. The log files are saved in C:\Documents and Settings\All

Users\Application Data\VMMLogs with Windows 2000 Server, Windows XP, or Windows Server 2003

or in C:\Users\All Users\VMMLogs with Windows Vista or Windows Server 2008.

Patch or Driver Issues (P2V)

Possible cause (or causes) A patch or driver file that is required for the P2V Fixup step is missing.

Solution (or solutions) If a patch file or driver is missing, download the requested patch and driver files to the Patch Import

directory on the VMM server (the default path is <C>:\Program Files\Microsoft System Center Virtual

Machine Manager 2008\Patch Import), and extract the files by using the Add-Patch cmdlet.

Less than 512 MB RAM (offline P2V only)

Possible cause (or causes) The source computer has less than 512 MB RAM.

Solution (or solutions) Add more RAM to the source computer to equal at least 512 MB.

Offline P2V

Possible cause (or causes) Cannot troubleshoot offline P2V.

Solution (or solutions) To enable tracing on the source computer during an offline P2V, create a file named

scvmm_enable_winpe_tracing.txt and save it to the root of the source computer's boot volume. This

file does not need to contain any data or information. A trace file named scvmm_winpe.etl will be

created and saved on the source computer.

Firewall Issues (P2V)

Troubleshooting VMM

Troubleshooting Virtual Machine Conversion Issues / BITS transfer fails (P2V) Page 12

Possible cause (or causes) Firewall blocks P2V by not allowing an exception for remote administration (RemoteAdmin service).

Solution (or solutions) If the firewall is controlled by Group Policy, use GPEDIT.msc to enable an exception for the IP address

of the VMM host, for open ports, and for authorized applications. The path is: GPEDIT.msc-

>Computer configuration->Administrative Templates->Network->Network Connections->Windows

Firewall.

BITS transfer fails (P2V)

During a P2V conversion, the Background Intelligent Transfer Service (BITS) transfer fails with the

error ERROR_NO_TRACKING_SERVICE.

Possible cause (or causes) The HTTP SSL service might be down.

Solution (or solutions) Ensure that the HTTP SSL service is running, and then try the P2V conversion again.

Error with a Host in Limited State (V2V)

Possible cause (or causes) When a Hyper-V host is selected as the target host for a V2V conversion, the Migrate Wizard displays

the following warning: "Virtual machine <VMName> cannot be migrated from host <source host>

because the host is in a state that has limited management functionality. For hosts in the OK

(Limited) state, a virtual machine can be migrated only within the same VirtualCenter server.

Solution (or solutions) Proceed with the V2V conversion as normal. This error is unrelated to V2V.

Missing Hosts (V2V)

Possible cause (or causes) Migrate Wizard lists only ESX Server hosts. How can I perform a V2V conversion to a Hyper-V host (or

to any host that is not listed)?

Solution (or solutions) Make sure that the default filter is expanded to show All Hosts.

Communication Issues (V2V)

Possible cause (or causes) During a V2V conversion, communication fails between the VMM server or the destination host and

the ESX Server host, the VMM library, or the Windows shared folder that stores the VMware

configuration and data files.

Troubleshooting VMM

Troubleshooting Virtual Machine Conversion Issues / Updates Page 13

Solution (or solutions) The resolution depends on the scenario:

• If the VMware virtual machine is on an ESX Server host, check Secure Shell (SSH) and HTTPS.

• If the VMware virtual machine is on the VMM library, check WSMan permissions and settings

and Windows Firewall exceptions for the Background Intelligent Transfer Service (BITS) and

HTTPS ports.

• If the VMware virtual machine is on a Windows or NFS shared folder, check WSMan on the

destination host or Server Message Block (SMB).

Updates

Possible cause (or causes) A patch or driver file that is required for the operating system fix up is missing.

Solution (or solutions) Download the required patch and driver files to the Patch Import directory on the VMM server (the

default path is %SYSTEMDRIVE%\Program Files\Microsoft System Center Virtual Machine

Manager 2008\Patch Import), and then extract the files by using the Add-Patch cmdlet.

Permissions Issues (V2V)

Possible cause (or causes) VMM does not have permission to access one or more files involved in the V2V process from the

command line.

Solution (or solutions) The resolution depends on the location of the source VMware virtual machine. If the virtual machine

and virtual machine configuration file are on a Windows or NFS shared folder, make sure that the

machine account for the destination host (and the account under which VMM service is running on

the VMM server) has access to the share. If the virtual machine is on an ESX Server host, make sure

that the host is in an OK state.

Unrecognized .vmx or .vmdk File Format (V2V)

Possible cause (or causes) A V2V conversion was performed on a configuration file with an unsupported or unrecognized .vmx

or .vmdk file format.

Solution (or solutions) If the .vmx or .vmdk file format of the source virtual machine is not recognized, V2V conversion is not

supported for that virtual machine in this version of VMM.

Operating System Issues

Possible cause (or causes)

Troubleshooting VMM

VMM 2008 Error Codes / User Interface Error Messages Page 14

VMM cannot find a supported operating system or does not recognize the physical disk layout on the

new .vhd file, and VMM cannot complete the conversion.

Solution (or solutions) If VMM does not support the disk layout or operating system of the VMware virtual machine, VMM

will convert the VMDKs to VHDs and create the virtual machine but will not complete the operating

system fix up. As a result, the virtual machine might not start up or function correctly.

VMM 2008 Error Codes

User Interface Error Messages

The following table contains error messages that you might encounter when using the System Center

Virtual Machine Manager (VMM) 2008 user interface.

Error Messages

Code Message Recommended Action

200 Cannot connect to the service

%ServiceName;.

Check the Windows Event Log for

troubleshooting information.

201 Cannot ensure configuration of the

service %ServiceName;.



202 Cannot connect to the Service Control

Manager (SCM).



203 VMM cannot start the service

%ServiceName; service.

Run services.msc, select and right-click the

service %ServiceName;, and then click Start.

204 VMM cannot start the %ServiceName;

service.

Run services.msc, select and right-click the

service %ServiceName;, and then click Stop.

205 System Center Virtual Machine Manager

was not installed successfully.

Review the error log information and then try

running Setup again.

206 Setup was unable to receive the system

configuration.

Ensure that the Windows Management

Instrumentation service is running, and then

try the operation again.

208 Another instance of System Center

Virtual Machine Manager 2008 Setup is

running.

Close all open instances of the Virtual

Machine Manager Setup program and then

try the installation again.

209 The Setup log file path %FileName; is

not valid.

Select a valid Application Data folder path,

and then try the operation again.

210 Setup cannot create the file

%FileName;.

Verify that Setup has permission to create the

file, and then try the operation again.

Troubleshooting VMM


211 The Setup log file path %FileName; is

too long.

Verify that the Application Data folder path

has fewer than 260 characters, and then run

Setup again.

212 The configuration data for this product

is corrupted.

Contact your support personnel for further

help.

213 Setup cannot read the file %FileName;. Ensure that Setup has permissions to read the


214 The computer does not meet the

minimum processor configuration

requirements to run Virtual Machine

Manager. The minimum required

processor speed is

%ProcessorClockSpeed; MHz.

Either upgrade the processor speed in the

computer or install Virtual Machine Manager

on a different computer that meets the

hardware requirements.

215 This computer does not meet the

minimum memory requirements to run

Virtual Machine Manager. The minimum

memory required is

%MemoryMinRequired; MB; and the

recommended memory is

%MemoryRecommended; MB.

Either upgrade the amount of memory in the

computer or install Virtual Machine Manager

on a different computer that meets the

hardware requirements.

216 This computer does not meet the

recommended amount of memory.

The recommended amount of memory for

optimal performance is

%MemoryRecommended; MB. Either upgrade

the amount of memory in the computer or

install Virtual Machine Manager on a different

computer that meets the hardware

requirements.

217 The remote SQL Server administrator

credentials provided are not valid.

Ensure that the remote SQL Server

administrator credentials are valid, and then


220 This computer is not part of a domain. Virtual Machine Manager requires a computer

that is a member of a domain. Join this

computer to a domain, and then run Setup

again.

221 There is insufficient disk space on the

system volume

%SystemVolumeDriveLetter; to

complete the installation.

Create %SystemDiskSpaceRequired; MB of

disk space on the system volume to continue

with the installation.


program files volume

%BinaryVolumeDriveLetter; to complete

the installation.

Create %BinaryDiskSpaceRequired; MB of disk

space on the volume to continue with the

installation.

223 There is insufficient disk space on the Create %DatabaseDiskSpaceRequired; MB of

Troubleshooting VMM


database volume

%DatabaseVolumeDriveLetter; to

complete the installation.

disk space on the volume to continue with the

installation.

224 Setup has detected instance

MICROSOFT$VMM$ running on an older

version of SQL Express 2005.

Uninstall MICROSOFT$VMM$ and then run

Virtual Machine Manager Setup again to

install SQL Express 2005 Service Pack 1.

225 Setup has detected SQL instance

%SqlInstance; on the local server.

Select "Use an existing SQL Server instance",


226 %ProductName; Beta is currently

installed.

To upgrade %ProductName;, refer to the

upgrade documentation at

http://go.microsoft.com/fwlink/?

LinkId="117133". To perform a new

installation, uninstall all Beta Virtual Machine

Manager components and then install Virtual

Machine Manager 2008.

227 The required service %ServiceName; is

disabled.

Enable the service and then run Setup again.

228 A different version of %ProductName; is

currently installed.

Uninstall the existing %ProductName; from

Add/Remove Program and then run Setup

again.


requires Windows PowerShell 1.0.

To download Windows PowerShell 1.0, go to


LinkId="77521".

230 Virtual Machine Manager cannot be

successfully installed because service

%ServiceName; is marked for deletion.

Reboot the server, and then run Setup again.

231 The SQL Server instance %SqlInstance; is

not supported.

Use a Microsoft SQL Server 2005 SP2 instance,

and then continue with Setup.

233 The SQL Server database

%DatabaseName; is currently in use by

another program or process.

Select another database and try again.

234 The existing Virtual Machine Manager

database is not accessible.

Ensure that SQL instance %SqlInstance; is

installed properly and running. Also ensure

that %DatabaseName; is accessible.

235 Setup has detected a database that is

not compatible with the version being

installed.

Delete %DatabaseName; from SQL instance

%SqlInstance; and then continue with Setup.


requires Internet Information Services

(IIS).

To enable Internet Information Services (IIS)

for Windows Server 2003, you must add the

Windows Server IIS 6.0 component.\n\nTo

enable IIS for Windows Server 2008, you must

Troubleshooting VMM


add the Web Server (IIS) role and enable the

ASP.NET, IIS 6 Metabase Compatibility and IIS

6 WMI Compatibility server role services.

239 Setup has detected an unsupported

version of Microsoft WinFX Runtime

Components or .NET Framework 3.0.

Uninstall the existing version, and then run

Setup again.


version of Windows PowerShell. System

Center Virtual Machine Manager

requires Windows PowerShell 1.0.

Uninstall the existing version of Windows

PowerShell, and then to download Windows

PowerShell 1.0, go to


LinkId="77521".

241 Disk space cannot be calculated. Select a different installation location, and

then try the operation again.

242 VMM cannot read the Virtual Machine

Manager installation path registry key.

Some folders cannot be deleted.

View the error log for a complete list of

folders, and delete those folders manually.


requires Windows Remote Management

(WinRM) 1.1.

To download WinRM 1.1, go to


LinkId="84599".

244 The Windows Remote Management

(WinRM) service is not running on the

computer.

Verify that WinRM service is running, and


245 SQL service %ServiceName; is not

running on the computer.

Verify that service %ServiceName; is running,


246 The World Wide Web Publishing Service

is not running on the computer.

Verify that World Wide Web Publishing

Service is running, and then try the operation

again.


version of Windows Remote

Management (WinRM). Virtual Machine

Manager requires WinRM 1.1.

To download WinRM 1.1, go to


LinkId="84599".

248 VMM server connection port cannot be

0.

Enter a valid port number.

249 Agent connection port and file transfer

port cannot be of the same number.

Enter different port numbers.


Workgroup Edition cannot manage

more than five hosts. The specified

Virtual Machine Manager database

exceeds this limit.

Specify a new database or a VMM database

that contains a maximum of five hosts. To

manage more than five hosts, upgrade VMM

Workgroup Edition. For information about

upgrading, go to


Troubleshooting VMM


LinkId="117133".

256 VMM cannot load the file %FileName;.

The file may be corrupted or missing.

Run the Virtual Machine Manager Setup

program directly from the product CD. If the

setup program from the CD fails, obtain a new

copy of the CD from your vendor.

257 An error has occurred while trying to

configure Virtual Machine Manager.

Uninstall Virtual Machine Manager from Add

or Remove Programs and then run Setup

again.

260 The product key is not valid. The product key is located on the back of the

Virtual Machine Manager product CD. Enter a

valid product key and then try installation

again.

262 %InputParameterTag; is empty or it

exceeds %MaxLimit; characters.

Enter a valid input, and then try the operation

again.

263 %InputParameterTag; exceeds

%MaxLimit; characters.

Enter a valid input, and then try the operation

again.

264 %InputParameterTag; is neither 1 nor 0. Enter either 1 or 0, and then try the operation

again.

266 The path %FileName; exceeds


Enter a shorter path name, and then try the

operation again.

267 Installation source %FolderPath; for

installing prerequisites does not exist,

cannot be accessed, or Setup cannot

find one or more prerequisite CDs at the

location.

Ensure that the prerequisite CDs are copied

correctly, and run Setup again.

268 Not all database files from a previous

installation were found at %Location;.

Delete the existing file or choose an

alternative location for your database.

269 There is not enough disk space for

%InstallItem;.

Create additional disk space on this disk, or

choose a different location, and then try the

operation again.

270 The location cannot be on removable

media or a network share.

Select a different location, and then try the

operation again.

271 The attributes of directory

%DirectoryPath; cannot be acquired.

Select a different installation location, and


272 The selected location %DirectoryPath; is

read-only, hidden, a system folder, or a

root volume.

Select a different location, and then try the

operation again.

273 The selected location %DirectoryPath; is

on a compressed volume.

Select a different location.

Troubleshooting VMM


274 The directory %DirectoryPath; is not on

an NTFS volume.

Install prerequisite software and Virtual

Machine Manager on an NTFS volume, and


275 The volume information for directory

%DirectoryPath; cannot be acquired.

Select a different installation location, and


276 The parameter

%CommandlineArgument; is not valid.

See "Installing Virtual Machine Manager" in

the Virtual Machine Manager Setup help for

information about parameter usage.

277 The parameter

%CommandlineArgument; is already

specified.


the Virtual Machine Manager setup help for

information about parameter usage.

278 The parameter

%CommandlineArgument; does not

have a value associated with it.


the Virtual Machine Manager Setup help for

information about the specific parameter.

279 The specified path %FileName; is not

valid.

Select a valid path and verify the path is

accessible. Try the operation again.

280 The passwords entered do not match. Enter the passwords again, and then try the

operation again.

281 A reboot is required to complete the

deletion of the service %ServiceName;.

Reboot the machine.

282 The evaluation copy of System Center

Virtual Machine Manager has expired.

For details about obtaining a license, go to the

System Center Virtual Machine Manager Web

site at http://go.microsoft.com/fwlink/?

LinkId="117146".

284 Setup has detected an existing

installation of Virtual Machine Manager

on this computer.

To install Virtual Machine Manager, uninstall

the existing version, and then run Setup again.

285 %InputParameterTag; must be an

integer between 0 and 65535.

Enter the port number again.

288 This program is for internal Virtual

Machine Manager use only.

To launch the Virtual Machine Manager Setup

program, run Setup.exe in the parent

directory of the product CD.

289 The .ini file is not specified in the

command line.

For more information, see "Installing Virtual

Machine Manager" in the Virtual Machine

Manager Setup help.

290 Virtual Machine Manager failed to

uninstall.

Review the error details for information on

the failure and how to remediate it. Once the

failure has been resolved, try the

uninstallation again.

292 Configuration of Virtual Machine For more information about configuration,

Troubleshooting VMM


Manager failed. see "Troubleshooting" in the Virtual Machine

Manager Setup help.

293 Setup could not remove the shortcuts to

the Virtual Machine Manager

Administrator Console from:

%CommaSeparatedShortcutLocations;.

Delete the shortcuts manually.

294 Setup was unable to remove Virtual

Machine Manager from the Windows

Firewall exceptions list.

If Windows Firewall is enabled, remove Virtual

Machine Manager from the exceptions list. In

Control Panel, click Windows Firewall, click

the Exceptions tab, and remove from the list

of exceptions.

296 Setup was unable to delete the

database %DatabaseName; from SQL

instance %SqlInstance; on server

%ServerName;.

Delete the database manually.

297 The requested action cannot be

specified by using the command line.

For more information, see "Installing Virtual

Machine Manager" in the Virtual Machine

Manager Setup help.

298 Share %ShareName; already exists. Enter a different name for the library share.

299 Share %ShareName; does not exist on

the VMM server.

Enter the name of an existing share.

300 Setup was unable to delete the SQL

login %SqlLoginName; from SQL

instance %SqlInstance; on server

%ServerName;.

Delete the login manually.

303 The folder %FolderPath; cannot be

deleted.

Delete the folder manually.

304 Administrative privileges are required to

install System Center Virtual Machine

Manager.

To run Setup as an administrator, right-click

Setup.exe, click "Run as", and then enter the

credentials for a user account with

administrative privileges.

305 Virtual Machine Manager cannot be

installed on a computer running this

operating system.

Install Virtual Machine Manager on a

computer running Windows Server 2003 R2.

306 Virtual Machine Manager has detected

an older version of Microsoft .NET

Framework.

Install Microsoft .NET Framework 2.0 or the

most current version and then run Setup

again.

307 The folder %FolderPath; cannot be

created. The folder may already exist.

Delete the folder if it exists, and then run

Setup again.

308 Virtual Machine Manager is not installed

on this computer.

For more information about installation, see

"Installing Virtual Machine Manager" in the

Troubleshooting VMM


Virtual Machine Manager Setup help.

309 Either the existing Virtual Machine

Manager database could not be

accessed, or the database is corrupted.

Restore to a valid database and ensure that

the SQL Server service is running. Run Setup

again.

310 Virtual Machine Manager is already

installed on this computer.

To uninstall Virtual Machine Manager, go to

Add or Remove Programs and select uninstall.

311 The prerequisite check was not

successful.

View the errors in the Virtual Machine

Manager Setup log file %SetupLogFile;, view

the errors and make the required changes.

Run Setup again.

312 Setup could not delete the shortcuts to

the Virtual Machine Manager

Administrator Console from:

%CommaSeparatedShortcutLocations;.

Delete the shortcuts manually.

313 Active Directory Domain Services cannot

validate user %UserName;.

Check the network connectivity to the

Domain Controller, and then run Setup again.

If the problem persists, contact your network

administrator.

314 Setup could not delete the service

%ServiceName;.

Service %ServiceName; must be manually

deleted.

316 Setup could not configure the firewall

exceptions.

If the configuration is being run from OEM

Setup, verify that Setup has the necessary

privileges to configure firewall exceptions,

and then run the configuration again.

Otherwise, uninstall the VMM server and then

install it again.

317 Setup has detected an existing database

but cannot retrieve the physical location

of the Virtual Machine Manager

database from SQL Server instance

%SqlInstance;.

Verify that SQL Server is installed properly and

that the SQL Server service %ServiceName; is

running.

319 The Virtual Machine Manager database

was not created.

The Virtual Machine Manager database was

not created. Delete %DatabaseName;.mdf

and %DatabaseName;_log.ldf if they exist at

%FolderPath; or use a unique name for the

database. Also, verify that disk quota

management is not enabled for the drive

where the database is being created. Then

run Setup again.

320 Setup could not delete the Virtual

Machine Manager database.

Manually delete %DatabaseName; from SQL

instance %SqlInstance;.

321 Database files in Delete the files manually.

Troubleshooting VMM


%DataFilesCompleteLocation; could not

be removed.

322 Cannot locate the file SqlCmd.exe. Install the SQL Client Tools and then run Setup

again.


was not created from the existing

database files.

Delete the existing files or choose another

location for the database.

325 Cannot enable the service

%ServiceName;.

Enable the service in the Services MMC snapin

by running "services.msc", find the service

%ServiceName;, and verify that the service is

enabled.

326 Cannot create service %ServiceName;. Reboot the computer, uninstall Virtual

Machine Manager, and then run Setup again.

327 Setup could not delete service

%ServiceName;.

Delete the service manually.

328 Setup was unable to configure service

%ServiceName;.



329 Could not install the necessary Setup

files from %SourceLocation; to

%InstallLocation;.

Ensure that Setup has access to the

installation location.

330 Cannot delete necessary setup files

from %InstallLocation;.

Delete the files manually.

331 Cannot mark necessary Setup files at

%FolderPath; for deletion.

Delete the files manually after Virtual

Machine Manager Setup is complete.

332 VMM cannot start Setup. Run Setup from the product CD. If you are

running it from the CD already, the CD is

corrupted. Request a new CD from your

administrator.

334 Setup could not configure the database

%DatabaseName;.

Ensure service %ServiceName; is started by

running "services.msc", find the service, and

then verify that the service is started.

336 Setup could not query the Web site

setting.

Ensure that the IIS Admin Service is running

and then try running VMM Self-Service Portal

Setup again. If you are installing the portal on

a computer that is running Windows Server

2008, also ensure that the Web Server (IIS)

role is added and that the IIS 6 Management

Compatibility role service is installed.

337 Web site %SiteName; has the same

address binding as the specified port.

Enter a different port or a custom host header

for the portal, or delete the conflicting Web

site. Then try the operation again.

Troubleshooting VMM


339 Setup cannot connect to the specified

SQL Server instance.

Ensure that the server name and instance

name are correct. If you are installing VMM

remotely, ensure that remote connections are

set up correctly, and then try Setup again.

342 %Prerequisite; installation has failed. Manually install %Prerequisite;.

343 %Prerequisite; installation has failed.

For error detail, see %SetupLogFile;.

Manually install %Prerequisite;.

344 The file %FileName; cannot be deleted. You may not have permission to delete the

file, or the file is locked by another

application. Manually delete the file after

completing the Setup program.

346 Cannot access the registry key

%RegistryKey; for the Microsoft SQL

Server instance %SqlInstance;.

Verify that the SQL 2005 instance is installed

and configured correctly.


connect to database %DatabaseName;.

Ensure that the SQL Server service

%ServiceName; can be started and that you

have permissions to query the SQL Server.

350 Setup cannot write to file %FileName;. Delete the file if it exists, and then run Setup

again.


delete database %DatabaseName;.

Manually delete %DatabaseName; from SQL

instance %SqlInstance;.

358 Setup was unable to set permissions on

folder %DirectoryPath;.

Ensure that the folder %DirectoryPath; is a

valid location and that the current user has

permission to access the location.

359 Setup cannot connect to the SQL Server

%ComputerName;.

Ensure that the server name is correct and

that it is connected to the network.

360 Setup cannot find a SQL Server instance

on %ComputerName;.

Verify that SQL Server 2005 is properly

installed and that the SQL Server service is

running.

361 The SQL database %DatabaseName;

already exists.

Either clear the "Create a new database"

check box to use the existing database, or

type a new database name and then try the

operation again.

362 The SQL database %DatabaseName;

does not exist.

Check the "Create a new database" check box

to create a new database, or use an existing

database.


could not be upgraded.

Uninstall the Virtual Machine Manager server

selecting the "Retain data" option, and then

try installing the Virtual Machine Manager

server again.

Troubleshooting VMM


364 Setup cannot find a database in the SQL

Server instance %SqlInstance;.

Select the "Create a new database" check box

to create the database, or select another SQL

Server instance.


is not preinstalled on this computer.

For more information about installing Virtual

Machine Manager go to


LinkId="117338".


requires the Windows Automated

Installation Kit (WAIK) to be installed.

To download the Windows Automated

Installation Kit, go to


LinkID="86477".


version of Windows Installer.

To install the correct version of Windows

Installer, go to


LinkId="117300".

368 To continue, your computer must be

restarted.

Cancel the Virtual Machine Manager server

setup, restart the computer, and then run the

Virtual Machine Manager server setup again.

369 Run command %FileName; with

argument %CommandlineArgument;

failed.

Verify that the command and arguments are

correct and then run Virtual Machine

Manager server setup again.

370 The VMM Self-Service Portal requires

the IIS 6 Management Compatibility role

service.

Open Server Manager, select the Web Server

(IIS) role, click "Add Role Services", and then

install the IIS 6 Management Compatibility

role service.

371 The VMM Self-Service Portal requires

Web Server (IIS) role services that are

not installed.

Open Server Manager, select the Web Server

(IIS) role, and ensure that the following role

services are installed; Static Content, Default

Document, Directory Browsing, HTTP Errors,

ASP.NET, .NET Extensibility, ISAPI Extensions,

ISAPI Filters, and Request Filtering.

455 %Value; is not a valid entry Please specify a value between 0 and 255.

456 %Value; is not a valid entry Please specify a value between 1 and 223.


Workgroup Edition cannot manage

more than five hosts.

Remove some existing hosts and then try the

operation again. To manage more than five

hosts, upgrade VMM Workgroup Edition. Find

information on upgrading at


LinkId="94662".

501 The virtual machine host

%ComputerName; cannot be removed

because one or more virtual machines

All virtual machines must be deleted from

%ComputerName; before the Host can be

deleted. Delete the virtual machines, and then

Troubleshooting VMM


are active on the virtual machine host. try again.

503 The specified virtual network

%VirtualNetworkName; does not exist.

Verify the virtual network name by refreshing

the Host Properties dialogue box, go to the

Hardware tab and click the Virtual Network

option. Then try the operation again.

508 A virtual network name must be

provided.

Enter a valid virtual network name, and then


510 A virtual network path was not selected. Select a virtual network path, and then try the

operation again.

511 The IP address is not valid. Enter a valid IP address, and then try the

operation again.

512 The network IP address must be the

base of the subnet.

Enter a valid IP address that is the base of the

subnet, and then try the operation again.

513 The IP address is not valid. The host

server reserves the first 16 IP addresses

for its own internal use.

Enter a valid IP address outside the range of

first 16 reserved addresses, and then try the

operation again.

514 The ending IP address is not in a valid

range. The last valid address of the

subnet is reserved.

Enter a valid IP Address within the range, and


515 A valid default gateway address must be

either part of same network or left

blank.

Enter a valid gateway address, and then try

the operation again.

516 The DHCP settings could not be saved.

The DHCP Server address is not in a valid

range. DHCP Server address should be

between the first valid IP address and

starting IP address.

Enter a valid DHCP server address, and then


517 The IP address lease time that has been

entered is not in a valid range. The

maximum value is 49710 days.

Enter valid lease time value, and then try the

operation again.

518 The network mask is not valid. The

network mask format should be

xxx.xxx.x.x.

Enter a valid network mask, and then try the

operation again

521 The lease renewal time must be less

than the lease rebinding time. Also, the

lease rebinding time must be less than

IP address lease time.

Enter a valid lease time, and then try the

operation again.

522 The minimum value allowed for IP lease

time is 60 seconds.


operation again.

523 The minimum value allowed for lease Enter a valid lease time, and then try the

Troubleshooting VMM


rebinding time is 45 seconds. operation again.

524 The minimum value allowed for lease

renewal time is 30 seconds.


operation again.

550 VMM cannot access registry key

%RegistryKey;.

Verify that the registry key exists, and then try


551 VMM cannot access registry key value

%RegistryKeyValueName; under

%RegistryKey;.

Verify that the registry key value exists, and


552 The registry key syntax %RegistryKey; is

incorrect.

Ensure that the key is not empty, contains

only valid characters and is less than 255

characters.

553 The type or name syntax of the registry

key value %RegistryKeyValueName;

under %RegistryKey; is incorrect.

Ensure that the type of value name is correct;

the name is not empty, contains only valid

characters and is less than 255 characters.

554 Permissions have not been granted to

access the registry key %RegistryKey;.

Verify permissions on this registry key, and


555 The operation on the registry key

%RegistryKey; was not successful. A

system error occurred, such as deletion

of the key, or an attempt to create a key

in the LocalMachine root, or the nesting

level exceeds 510.

Verify the registry key properties, and then try


556 VMM cannot delete the registry key

%RegistryKey;. The subkey does not

specify a valid registry subkey, has child

subkeys or deletion of a root hive has

been attempted.

Verify that the registry key is present, and


557 You must enter at least one virtual

machine path.

Add a default virtual machine path, and then


649 A host drive is not selected. Select a host drive or choose a different

capture mode.

650 A known image file is not selected. Select an image file or choose a different

capture mode.

651 A known floppy disk is not selected. Select a floppy disk or choose a different

capture mode.

652 The value for VM Memory is empty. Enter a value for the amount of VM Memory,


653 The value entered for VM Memory is

not valid.

Enter a valid value for the amount of memory,


Troubleshooting VMM


654 The value %MemorySize; MB specified

for virtual machine memory is not

within a valid range on the

%VMHostName; host.

Enter a value between %MinMemory; and

%MaxMemory; MB for virtual machine

memory, and then try the operation again.

655 The value entered for the MAC address

is empty.

Enter a MAC address in the format xx-xx-xx-

xx-xx-xx or choose to use a dynamic address,


656 The value entered for the MAC address

is not valid.

Enter a MAC address in the format xx-xx-xx-

xx-xx-xx or choose to use a dynamic address,


657 A virtual hard disk is not specified. Select a virtual hard disk, and then try the

operation again.

681 A destination file name is required when

creating a new disk.

Create a new file name, and then try the

operation again.

685 This job cannot be restarted until the

virtual machine %VMName; is repaired.

Run the repair action on this virtual machine

to complete the job.

686 The version of Virtual Server on host

%VMHostName; is not the supported VS

R2 SP1 version.

The selected virtual machine %VMName;

cannot run Sysprep on host %VMHostName;.

Upgrade Virtual Server on the selected host to

the R2 SP1 version, and then try the operation

again.

690 The disk size is larger than the available

space. The disk size is %DiskSize; GB and

the maximum amount allowed for bus

%BusType; is %MaxDiskSize; GB. The

maximum disk sizes are: IDE (127 GB)

and SCSI (2040 GB).

Reduce the disk size or connect it to another

bus type, and then try the operation again.

699 Virtual machine %VMName; needs to be

in a virtual machine host to share its

disks.

Deploy the virtual machine to a virtual

machine host and try the operation again.

700 Virtual hard disk %FileName; needs to

be in the SCSI bus for sharing to be

allowed.

Move the disk to a shared SCSI bus and try

again.

701 Virtual hard disk %FileName; needs to

be of fixed size type for sharing to be

allowed.

Provide a virtual hard disk that is of fixed size

and try again.

702 SCSI adapter at bus %Bus; needs to be

shared so its disk can be shared.

Share the SCSI adapter and try again.

703 Destination for the disk is %ObjectType;.

Sharing virtual hard disks is only allowed

between virtual machine objects.

Provide a virtual machine and try again.

Troubleshooting VMM


704 Virtual hard disk sharing is only allowed

within the same host.

Move both virtual machines to the same host

and try again.

705 Destination for the virtual hard disk

%FileName; is not a shared SCSI bus.

Set the SCSI adapter as destination for the

shared disk and try again.

710 Ethernet address type %MACType; is

not valid.

Ensure the parameter is valid and try again.

720 A user name must be specified. Enter a user name and then try the operation

again.

724 Unable to configure hardware because a

host disk is not specified.

Select a pass-through disk and then try the

operation again.


text file is not specified.

Enter a text file and then try the operation

again.


named pipe is not specified.

Enter a named pipe and then try the

operation again.

734 The value %MemorySize; MB specified

for virtual machine memory is not

within a valid range.

Enter a value between %MinMemory; and

%MaxMemory; MB for virtual machine

memory, and then try the operation again.

800 VMM cannot find %FilePath;. Ensure the path is valid, and then try the

operation again.

812 VMM cannot remove the disk because it

is the parent of a differencing disk.

Remove all differencing disks associated with

the parent disk, and then try the operation

again.

814 Cannot remove virtual disk because a

virtual machine is using this virtual disk.

To remove this virtual disk, first remove it

from the hardware profile of the virtual

machine using this virtual disk, then try again.

815 VMM cannot remove this library object

because a virtual machine, template,

hardware or guest operating system

profile is using it.

To remove the library object, first remove it

from all virtual machines, templates,

hardware and guest operating system profiles

that are using it, then try the operation again.

816 A valid name is required to complete

this task.

Enter a new name, and then try the operation

again.

817 VMM cannot add %FileName; as

%ObjectType;. The file extension of

%FileName; does not match the

supported file extensions for

%ObjectType;.

Select a file with a file extension that matches

%ObjectType;, and then try the operation

again.

829 The selected machine

%ComputerName; cannot be contacted.

Ensure that %ComputerName; is online,

connected to the network, and not blocked by

a firewall. Then try the operation again.

Troubleshooting VMM


845 The share path %FileName; is too long. Verify that the fully qualified path to the share

has fewer than %MaxLength; characters, then

attempt to add it again.

1247 Unable to migrate virtual machine

%VMName; because %VMHostName; is

not a suitable host for this virtual

machine.

Use the Migrate Virtual Machine Wizard to

rate all available hosts based on their

suitability for this virtual machine.

1408 Cannot locate the user role because it

no longer exists.

Close and reopen the Virtual Machine

Manager Administrator Console, and then try


1413 The requested operation would exceed

the assigned quota.

Make more resources available, and then try


1417 Virtual Machine Manager cannot find a

domain account for member

%UserName;.

A member of a user role must have an Active

Directory Domain Services account. Specify a

valid domain account, or click Browse to

select an account, and then try the operation

again.

1418 Unable to deploy the virtual machine

because no suitable host for this virtual

machine was found.

Contact your VMM administrator to gain

access to additional hosts.

1419 Unable to create the virtual machine

because no suitable host for this virtual

machine was found.

Contact the Virtual Machine Manager

administrator.

1601 VMM is unable to connect to the Virtual

Machine Manager server %ServerName;

because the specified computer name

could not be resolved.

Close and then reopen the Virtual Machine


the operation again. If the problem persists,

contact your network administrator.

1603 Unable to connect to the Virtual

Machine Manager server

%ServerName;. The attempt to connect

timed out.

1) Verify that %ServerName; is online and

accessible from your computer.\n2) If a

firewall is enabled on %ServerName;, ensure

that it is not blocking requests for TCP port

%RemoteUIPort;.

1612 The connection to the Virtual Machine

Manager server %ServerName; was lost.

1) Verify that %ServerName; is online and can

be accessed from your computer. Then try to

connect again.\n2) Verify that the Virtual

Machine Manager service on %ServerName; is

started, and then try to connect again. If the

problem persists, restart the Virtual Machine

Manager service.


Manager server %ServerName; was lost

due to insufficient credentials.

You must be logged on under an account that

is a member of a valid Administrator or

Delegated Administrator user role to open the

Administrator Console.

Troubleshooting VMM


1614 Virtual Machine Manager was unable to

start. The application requires a

computer that is joined to a domain.

Ensure connectivity between your computer

and the domain controller. If your computer is

not joined to a domain, join the machine to a

domain and restart Virtual Machine Manager.

1700 The Virtual Machine Manager service on

the %ServerName; server stopped while

this job was running. This may have

been caused by a system restart.

To restart this job, navigate to the Jobs view

and select the job in the results pane. Then, in

the Actions pane, click Restart.

1701 The job was stopped by the user

%UserName;.

To restart the job, select the job in the Jobs

view, and click Restart.

1736 Cannot connect to virtual machine

%VMName; because the Virtual Guest

Services feature is not available.

If the Administrator Console is on a computer

running Microsoft Vista without Service Pack

1, Windows XP without Service Pack 3, or

Windows Server 2003, you must install Virtual

Guest Services manually on the virtual

machine to enable connections. If Virtual

Guest Services are already installed, ensure

that the component has not been disabled.

1739 Cannot connect to virtual machine

%VMName; because the virtual machine

is not running.

Start the virtual machine, and then try the

operation again.

1758 Unable to change the host group name

because no name was specified.

Enter a name for this host group.

1782 One or more virtual machine hosts

could not be moved to the host group

%HostGroupName;.

To find out which hosts could not be moved

and why, review your failed jobs in the Jobs

window. To open Jobs, select Jobs on the

View menu.

1783 Unable to migrate multiple virtual

machines at the same time.

Select each virtual machine and migrate it

individually.

2400 Unable to resolve the path %SharePath;

to a physical path on %ComputerName;.

Ensure you have sufficient permissions on

%SharePath; and try the operation again.

2401 The specified path is not a valid share

path on %ComputerName;.

2402 VMM cannot rename %FileName;

because a file or folder with that name

already exists.

Specify a different folder name, and then try


2403 VMM cannot rename %FileName;

because the specified name is not valid.

A folder name cannot contain any of the

following characters: \ / : * ? " < > |. Specify a

valid folder name, and try the operation

again.

2404 VMM is unable to create folder Verify that the folder name is valid, and that

Troubleshooting VMM


%FileName;. you have the permissions to create the

folder.\n1) Ensure that the folder name does

not contain any of the following characters: \

/ : * ? " < > |.\n2) If you still cannot create the

folder, contact your administrator to verify

that you have the needed permissions.

2405 VMM is unable to find a domain account

for owner %UserName;.

The owner must have an Active Directory

Domain Services account. Either type an

account, or click Browse to select an account,


2407 VMM is unable to list shares on

%ComputerName; because access is

denied.

Ensure you have the required permissions to

shares on computer %ComputerName; and


2408 VMM is unable to browse volumes on

%ComputerName;, because access is

denied.

Membership in the Administrators, Power

Users, Print Operators, or Server Operators

group on %ComputerName; is required to

enumerate volumes.\nEnsure you have

sufficient permissions, and then try the

operation again.

2409 The specified path is not a valid folder

path on %ComputerName;.

Specify a valid folder path on

%ComputerName; which the virtual machine

will be saved on.

2410 When using the Join Domain feature,

the password is displayed as clear text

when creating a virtual machine on a

host. This would permit anyone with

access to the host or virtual machine

access to the password.

Use an account with limited privileges that

can only create computer accounts and join

them to the domain or use Active Directory

Services Interface (ADSI) and Windows Script

Host (WSH) to create a Visual Basic Script

(VBScript) that automates the creation of

computer accounts. A sample script is given in

the Microsoft Knowledge Base, article

Q315273

(http://support.microsoft.com/default.aspx?

scid="kb";en-us;q315273).

2413 Unable to create user role because no

name was specified for the user role.

Provide a name for this user role, and try the

operation again.

2416 Cannot install the VMware

Infrastructure Client on virtual machine

%VMName; because Internet Explorer

could not be found or accessed.

Ensure that Internet Explorer is in the system

path, or install the VMware Infrastructure

Client manually.

2417 Unable to connect to VMware virtual

machine %VMName; because Virtual

Machine Manager is waiting for an

authentication ticket for the virtual

machine.

Try the connection again later.

Troubleshooting VMM


2418 The following errors were encountered

while adding members to this user role:

%InvalidUserRoleMembers;

Select a set of valid domain accounts to add

to this user role.

2606 Unable to perform the job because one

or more of the selected objects are

locked by another job.

To find out which job is locking the object, in

the Jobs view, group by Status, and find the

running or canceling job for the object. When

the job is complete, try again.

2607 The SQL Server service account does not

have permission to access Active

Directory Domain Services (AD DS).

Ensure that the SQL Server service is running

under a domain account or a computer

account that has permission to access AD

DS.For more information, see "Some

applications and APIs require access to

authorization information on account objects"

in the Microsoft Knowledge Base at


LinkId="121054".

2944 VMM is unable to complete the

requested operation because the server

name %ServerName; could not be

resolved.

Try the operation again. If the problem

persists, contact your network administrator.

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.

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, gather system information

again by restarting the Convert Physical

Server wizard.

3148 The volume %VolumeDriveLetter;

selected for physical-to-virtual imaging

is not accessible from Windows PE. This

is usually caused by missing or incorrect

storage drivers. %ComputerName; may

now need to be manually restarted into

the original operating system using the

boot menu.

Exclude this volume from conversion. Or, if

you are performing offline physical-to-virtual

conversions, create a new folder under

%StaticDriverPath; on the VMM computer

and then copy all of the storage or networks

drivers to the new folder.

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 want to perform an

online conversion exclude the volume

%VolumeDriveLetter; in the Volume

Configuration page and choose Online

conversion in Conversion Options.

Troubleshooting VMM


3231 Unable to convert the physical server.

Virtual Machine Manager requires a

host with Hyper-V or Virtual Server 2005

R2 SP1.

Use the "Add hosts" action in the

Administrator Console to add a host and then


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.

3407 The entered URL is not valid. Enter a valid reporting server address in the

Reporting settings in the Administration pane.

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

server.

Ensure that the Microsoft Virtualization

Reports management pack is installed and the

reports are present under

Microsoft.Virtualization.Reports folder.


volume %VolumeDriveLetter; to

complete placement of the virtual

machine.

Free %BinaryDiskSpaceRequired; of disk space

on the volume %VolumeDriveLetter;, or

choose a different volume to continue with

the placement.

3511 The path %PathName; exceeds the

maximum allowed length by

%DiffFromMaxLimit; characters.

The maximum length allowed in a path is

%MaxLimit; characters. Enter a shorter path,


3517 Unable to save the virtual machine

configuration files because volume

%VolumeDriveLetter; is marked as

unavailable for placement.

Select a different save path for this virtual

machine and then try the operation again.

10201 Share name %ShareName; contains one

or more characters that are not valid or

has too many characters.

A share name cannot contain any of the

following characters: /\[]=?*+;,<>|: and

cannot be longer than 80 characters. Enter a

different library share name and then try the

operation again.

10202 The portal host header %SspHeader;

contains one or more characters that

are not valid.

A portal host header name can contain only

alphanumeric characters, and periods or

dashes. Enter a different portal host header

name and then try the operation again.

10204 Either the domain account or the

password you entered are not valid.

Please enter a valid domain name, user name,

and user password and then try the operation

again.

Troubleshooting VMM


10205 The domain account %UserName; is not

a member of the local Administrators

group.

Either add the domain account to

Administrators group, or use another domain

account that is in the local Administrators

group.

10406 Virtual Machine Manager cannot

contact %ComputerName; because the

credentials for %ComputerName; are

missing.

Provide credentials for %ComputerName; and


10607 The VHDDrive operation requires either

-VirtualHardDisk or -PassThroughDisk

parameters.

Specify the -VirtualHardDisk or -

PassThroughDisk parameter.

10634 Unable to store virtual machine

%VMName; on library server

%ServerName;. The virtual machine

contains SAN-attached disks and cannot

be stored on a highly available library

server.

Select "Transfer over the network," and then


10649 Unable to migrate the virtual machine

%VMName; because the processor is

not compatible with the host

%VMHostName;.

To select the most suitable host for virtual

machine %VMName;, use the Migrate Virtual

Machine Wizard. The wizard rates all available

hosts based on their suitability for this virtual

machine.

10650 Unable to migrate the virtual machine

%VMName; because the version of

virtualization software on the host

%VMHostName;

(%TargetHostVSVersion;) does not

match the version of virtualization

software on the source host

(%SourceHostVSVersion;). To be

migrated, the virtual machine must be

stopped and should not contain any

saved state.

To select the most suitable host for virtual

machine %VMName;, use the Migrate Virtual

Machine Wizard. The wizard rates all available

hosts based on their suitability for this virtual

machine.

10683 Unable to contact cluster service on

%ComputerName;.

Ensure that the cluster service is properly

installed and running.

10811 The VMM server was unable to

impersonate the supplied credentials.

Add the library server without adding any

library shares.Once that task has completed

successfully add the library shares.

11000 The number of processors requested on

the virtual machine %VMName;

(%Count;) exceeds the maximum

supported by the host virtualization

software (%MaxLimit;).

Select a different host or reduce the number

of processors on the virtual machine and then


11001 The number of network adapters Select a different host or reduce the number

Troubleshooting VMM


requested on the virtual machine

%VMName; (%Count;) exceeds the

maximum supported by the host

virtualization software (%MaxLimit;).

of network adapters on the virtual machine


11002 The memory requested for the virtual

machine %VMName; (%MemorySize;

MB) is not within the range that the

host virtualization software supports.

Select a different host or change the

requested memory for the virtual machine to

a value within the supported range

(%MemorySizeMinLimit; -

%MemorySizeMinLimit;), and then try the

operation again.

11003 A DVD drive is attached to the SCSI bus

on the virtual machine %VMName;. The

virtualization software on the host only

supports devices attached to the IDE

bus.

Select a different host or attach the DVD to

the IDE bus and then try the operation again.

11004 The number of devices attached to the

SCSI bus on the virtual machine

%VMName; exceeds the maximum

number supported by the host

virtualization software (%MaxLimit;).

Reduce the number of SCSI devices to

%MaxLimit; or fewer and then try the

operation again.

11005 The number of processors on the virtual

machine %VMName; (%Count;) is

greater than the number of processors

on the target host (%MaxLimit;). The

host must have an equal or greater

number of processors than the virtual

machine.


of processors on the virtual machine to

%MaxLimit; or fewer. Try the operation again.

11006 The virtual machine %VMName; is

configured as highly available but the

selected host is not a highly available

host.

Select a highly available host for the virtual


11007 Host cluster %HostClusterName; is

overcommitted.

Select a different highly available host and


11008 This configuration causes the host

cluster to become overcommitted.

Select a different highly available host and


11009 The number of LUNs requested on the

virtual machine %VMName; (%Count;)

exceeds the number of LUNs available

on the host (%MaxLimit;).


of LUNs on the virtual machine, and then try


11010 The Network location

%NetworkLocation; associated with the

virtual machine %VMName; does not

exist on host %VMHostName;.

Select a different host and then try operation

again.

Troubleshooting VMM


11011 The Network location

%NetworkLocation; and tag

%NetworkTag; associated with the

virtual machine %VMName; does not

exist on host %VMHostName;.

Select a different host and then try operation

again.

11012 The virtual machine %VMName; is not

configured as highly available but the

selected host is highly available.

Select a non-highly available host for the

virtual machine and then try the operation

again.

11013 Unable to place virtual machine

%VMName; on host %VMHostName;

because the host's virtualization

software does not support this virtual

machine.

Select a different host and then try the

operation again.

11014 The projected CPU utilization will

exceed the available CPU on the host.


operation again.

11017 The number of %NICType; network

adapters requested on the virtual

machine %VMName; (%Count;) exceeds

the maximum number of %NICType;

network adapters that the host

virtualization software supports

(%MaxLimit;).


of %NICType; network adapters on the virtual


11018 All of the volumes on %VMHostName;

are marked as not available for

placement.

Select a different host or add more storage


11019 There are no volumes available for

placement. For clustered hosts, all

shared storage is currently in use or not

available. In addition, some of the

volumes may be marked as unavailable

for placement.

Select a different host or add more storage


11032 Virtual machine %VMName; cannot be

placed on Hyper-V host %VMHostName;

because it has checkpoints in a format

incompatible with Hyper-V virtualization

platform.


operation again.

11033 The network adapter associated with

network location %NetworkLocation;

and tag %NetworkTag; on host

%VMHostName; is not connected.

Ensure that the network adapter is enabled

and connected, and then try the operation

again.

11034 The network adapter associated with

network location %NetworkLocation; on

host %VMHostName; is not connected.

Ensure that the network adapter is enabled

and connected, and then try the operation

again.

Troubleshooting VMM


11035 There is no suitable network location for

virtual machine %VMName; on host

%VMHostName;. Ensure that at least

one network adapter is enabled and

connected.

Ensure that at least one network adapter is

enabled and connected, and then try the

operation again.


placed on host %VMHostName; because

the host is a node in a host cluster that

is managed by Virtual Machine

Manager. Virtual Machine Manager

does not support performing a physical-

to-virtual conversion (P2V) or a virtual-

to-virtual conversion (V2V) to a target

host that is in a host cluster.

Try the operation again, and select a host that

is not in a host cluster.

11200 There is no disk selected to pass through

to a physical host drive.

Select a disk and then try the operation again.

11201 Disk %DiskName; is selected multiple

times for pass though to a physical host

drive.

Select a different disk and then try the

operation again.

11202 This virtual machine is currently paused.

You must stop a virtual machine before

it can be migrated.

Stop the virtual machine, and then perform

the migration.

11400 User role %FriendlyName; already

exists.

Enter a different name for the user role and


11410 The user role no longer exists. Close and reopen the Virtual Machine



11411 Cannot use Set-VMMUserRole with an

Administrator profile. There can be only

one Administrator user role.

Modify the existing Administrator UserRole or

create a new UserRole from DelegatedAdmin

profile to delegate administration.

11415 The -ParentUserRole parameter is

required for Set-VMMUserRole with a

Delegated Administrator profile.

Select the ParentUserRole parameter for the

new user role

11416 The -ParentUserRole specified must be a

Delegated Administrator user role.

Select UserRole for the DelegatedAdmin

profile as the ParentUserRole and then try the

operation again.

11424 As a delegated administrator, you

cannot view or edit user roles that are

at a higher level.

Select a user role that is at a lower level.

11425 The user role specified is not valid. Provide a valid value for User Profile. Valid

values are: Administrator, DelegatedAdmin or

SelfServiceUser.

Troubleshooting VMM


11426 This virtual machine could not be

deployed because it is not associated

with any Self-Service user role.

Contact your Virtual Machine Manager

administrator to have this virtual machine

associated with a user role that you are a

member of.

11427 The ownership for this virtual machine

cannot be changed because the new

owner is not a member of a user role

that has access to this virtual machine.

Either change the new owner to a user who

has access to this virtual machine, or contact

your Virtual Machine Manager administrator

to request access for the user you want to

own this virtual machine and then try the

operation again.

11429 The specified user role is not valid

because owner %UserName; of this

virtual machine is not a member of the

specified user role.

The User Role provided is invalid because the

Owner ( %UserName; ) of this virtual machine

is not a member of the specified user role.

Changing User Role only

11430 Either the specified user role or the

specified owner (%UserName;) for this

virtual machine is not valid.

Add %UserName; as a member of the user

role and try again or provide a different user

role or a different owner.

11431 The user role specified cannot be

applied to this virtual machine because

no owner has been set for this virtual

machine.

Attempt to set the user role again,

additionally providing an owner who is a

member of the user role.

11432 The specified parent user role is not a

top-level user role.

Specify a top level user role as the parent.

11433 This operation could not be completed

because the virtual machine is not

associated with any Self-Service user

role.


administrator to associate this virtual machine

to a Self-Service user role of which you are a

member.

11434 The virtual machine cannot be created

because a virtual machine name was not

specified.

Enter a valid virtual machine name and then


11435 A library share path is required for users

to store virtual machines to the library.

Select a library server and library share, or

clear the "Allow users to store virtual

machines in a library" check box.

11436 The Virtual Machine Manager server

could not validate user %UserName;.


administrator to verify that there is a two-way

trust relationship between the user domain

and the domain of the Virtual Machine

Manager server.

11437 The Virtual Machine Manager server

could not copy a required Hyper-V

authorization file to %ServerName;.


administrator to verify that %ServerName; is

running and connected to the network.

11600 A VMware ESX Server host cannot be ESX hosts must be in a host group that maps

Troubleshooting VMM


moved to the root host group. to a Datacenter node in VMware

VirtualCenter. The root host group does not

map to a Datacenter node.

11800 Cannot implement PRO tip because it is

not active.

To be implemented, a PRO tip must have

Active status. Do not attempt to implement a

PRO tip that has %PROTipState; status.

11801 Cannot dismiss PRO tip because it has

been implemented or implementation is

in progress.

Do not attempt to dismiss a PRO tip that has

%PROTipState; status.

11802 Unable to find the specified PRO tip. Verify that the specified PRO tip has not been

deleted.

11803 Unable to connect to the Operations

Manager root server,

%OperationsManagerServer;.

Ensure that the server exists and that System

Center Operations Manager 2007 is installed,


11804 The Virtual Machine Manager service

does not have required credentials to

access the Operations Manager SDK

service on %OperationsManagerServer;.

Add the VMM service account as an

Administrator on the Operations Manager

server, and then try the operation again.

11805 Unable to verify the connection to the

Operations Manager root server,


Ensure that the server exists, that System

Center Operations Manager 2007 is installed

on the server, and that Virtual Machine

Manager has the appropriate rights to

perform this action.

11806 Discovery of PRO performance and

usage data was terminated because the

VMM 2008 Management Pack has not

been imported into System Center

Operations Manager 2007.

Deploy the VMM 2008 Management Pack in

System Center Operations Manager 2007.

11811 Cannot implement PRO tip because no

automatic recovery action is defined for

the Operations Manager monitor that

generated the tip.

Review knowledge for the PRO tip for

recommended actions to resolve the issue.

12400 Unable to open Windows PowerShell

because the path to PowerShell.exe

could not be found.

Add the path to PowerShell.exe to the Path

environment variable on the Advanced tab in

Windows System Properties.

12401 Unable to display Windows PowerShell

script because Notepad could not be

found.

Add the path to Notepad.exe to the Path

environment variable on the Advanced tab in

Windows System Properties.

12404 Unable to import templates because no

library path was selected.

Select a library path and then try the

operation again.

12407 You cannot open the VMM Ask your VMM administrator to assign the

Troubleshooting VMM


Administrator Console because your

user role in Virtual Machine Manager

does not have access to any host

groups. \n\nThis happens when an

administrator is given a Delegated

Administrator profile but is not assigned

any host groups to administer.

host groups that you will administer to your

user role.

12408 You cannot add hosts to Virtual Machine

Manager because your user role does

not have access to any host

groups.\n\nThis happens when an

administrator is given a Delegated

Administrator profile but is not assigned

any host groups to administer.

Ask your VMM administrator to assign the

host groups that you will administer to your

user role.

12412 This action does not allow an empty

password.

Enter the password.

12416 VMM is unable to process one of the

provided parameters for

%CmdletName;. The parameter -

%ParameterName; was passed in with

the following value

"%ParameterValue;".

Try the operation again. If the issue persists,

contact Microsoft Help and Support.

12418 Invalid port number for

%InputParameterTag;.

Enter an integer from 1 through 65535 for the

port.

12419 Unable to display Diagram view because

the Operations Console for System

Center Operations Manager 2007

cannot be opened.

Install an Operations Console for Operations

Manager 2007 on the Virtual Machine

Manager server.

12422 Cannot add VMware ESX host

%VMHostName; to Virtual Machine

Manager because the host already is

associated with a VMware VirtualCenter

server (%VCSName;) that is managed by

VMM.

To associate the VMware ESX host with a

different VMware VirtualCenter server, first

remove the host from VMM, and then add the

host to VMM again, this time specifying the

new VirtualCenter server.

12423 The specified network address is not

valid.

Specify a valid IPv6 network address.

12424 Cannot add VMware ESX host

%VMHostName; to host group

%HostGroupName; because the host

group is not in a VMware VirtualCenter

datacenter.

To add a VMware ESX host, you must add it

within a VMware VirtualCenter datacenter.

Select a host group that represents its

VMware VirtualCenter datacenter or a child of

that host group.

12708 The specified pass-through disk

%FilePath; does not exist on host

%ServerName;.

Select an offline pass-through disk and then

try the operation again. If you have recently

changed your disk configuration, wait

Troubleshooting VMM


approximately 30 minutes or you can

manually refresh the properties selecting the

host %ServerName; in the Hosts pane and run

the refresh action.

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


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.

13244 The volume %VolumeDriveLetter;

selected for physical-to-virtual

conversion is not accessible from

Windows PE. This is usually caused by

missing or incorrect storage drivers in

Windows PE. %ComputerName; may

now need to be manually restarted into

the original operating system using the

boot menu.

Exclude this volume from conversion. Or, if

you are performing an offline physical-to-

virtual conversion, create a new folder under

%StaticDriverPath; on the VMM computer

and then copy all of the storage or networks

drivers to the to the new folder.

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



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.

13618 A network location is required when

overriding the network location.

Specify a network location and then try the

operation again.

13626 The specified virtual network does not

exist.

Verify the virtual network name by refreshing

the Host Properties dialogue box, go to the

Hardware tab and click the Virtual Network

option. Then try the operation again.

13804 Access to the cluster %ComputerName;

was denied.

Ensure that the specified credentials have

access to query cluster resources and then try


Troubleshooting VMM

VMM 2008 Error Codes / Command-Line Interface Error Messages Page 42

13805 Unable to contact cluster service on

%ComputerName;.

Ensure that the provided name is a cluster

name or the computer name of a node in the

cluster, and that the cluster is listed in Active

Directory Domain Services. For a newly

created cluster, you might need to wait for

the cluster name to be added to Active

Directory Domain Services.

13809 Unable to run WMI query on cluster

%ComputerName;.

Ensure that the specified computer name is a

cluster name and that the cluster service is

properly installed and running.

Command-Line Interface Error Messages

The following table contains error messages that you might encounter when using the Windows

PowerShell – Virtual Machine Manager command shell.

Error Messages

Code Message Recommended Action

261 The parameter %InputParameterTag; is

missing.

Select a value for the parameter.

400 The server %ComputerName; is already

associated with this Virtual Machine Manager

server.

Check the remote server name, and try


401 Virtual machine host %ComputerName; is not


server.

Check the virtual machine host name


402 Library server %ComputerName; is not


server.

Check the library server name, and try


403 %ComputerName; is not a valid network

computer name.

Only fully qualified domain names and

NETBIOS computer names are valid. An

IP address is valid only for hosts on a

perimeter network, ESX hosts, and

hosts joined to the domain by using an

IPv6 address. Check the computer

name, and try the operation again.

404 %ComputerName; cannot resolve with DNS. Ensure there is network communication

with the DNS server. If the problem

persists, contact your network

administrator.

Troubleshooting VMM


405 The credentials provided do not indicate a

valid domain user account.

1. Verify that the correct user name, a

valid password, and the correct domain

are entered and then try the operation

again.\n2. Verify that the domain

controller is operational and

responding.

406 Access has been denied while contacting the

server %ComputerName;.

1. Verify that the specified user account

has administrative privileges on

%ComputerName;.\n2. Verify that

DCOM access, launch, and activation

permissions are enabled on

%ComputerName; for the

Administrators group. Use

dcomcnfg.exe to modify permissions,


407 The agent operation with server

%ComputerName; was not successful.


persists, ensure that the VMM server is

able to communicate with the managed

computer.

408 %ComputerName; has an unsupported version

of the Virtual Machine Manager agent

installed.

Uninstall the Virtual Machine Manager

agent using Add or Remove Programs

on %ComputerName;, and then try the

operation again.

409 %ComputerName; is already associated with a

different Virtual Machine Manager server. A

computer can only be associated with one

Virtual Machine Manager server at a time.

Remove the association of

%ComputerName; from its current

Virtual Machine Manager server or

uninstall the Virtual Machine Manager


on %ComputerName; and try the

operation again.

410 Agent installation failed on %ComputerName;. Try the operation again. If the problem

persists, install the agent locally and

then add the managed computer.

411 Agent installation failed because an

installation is already in progress on server

%ComputerName;.

Wait for the installation to complete,


412 SCVMM cannot configure Virtual Machine

Remote Client (VMRC) on host server

%ComputerName;.

Try the operation again.

413 The files needed to install agent, version

%SoftwareVersion;, are missing from the

Virtual Machine Manager server

%ServerName;.

Reinstall the missing files by running

Virtual Machine Manager Server Setup.

414 Agent installation could not access the 1. Verify that the selected user account

Troubleshooting VMM


ADMIN$ share on server %ComputerName;. has administrative privileges on

%ComputerName;.\n2. Verify the

permissions on the ADMIN$ share of

%ComputerName;. The ADMIN$ share

must allow write access to the

Administrator group.\n3. Verify that the

system time on the Virtual Machine

Manager server and the server

%ComputerName; is synchronized with

the system time on the domain

controller.

415 Agent installation failed copying

%SourceLocation; to %InstallLocation;.

1. Ensure %ComputerName; is online

and not blocked by a firewall.\n2.

Ensure that there is sufficient free space

on the system volume.\n3. Verify that

the ADMIN$ share on

%ComputerName; exists. If the ADMIN$

share does not exist, reboot

%ComputerName; and then try the

operation again.

416 Agent installation timed out while waiting on

service %ServiceName; on %ComputerName;.

Ensure that the Windows Installer

service is running on %ComputerName;

and try the operation again.

417 There is a Virtual Machine Manager agent that

is not responding or not compatible on

%ComputerName;.

Uninstall the existing agent and then try


418 Agent installation failed on %ComputerName;

because WS-Management is not installed or it

is disabled.

Ensure that the Windows Remote

Management service is enabled and

running on the server

%ComputerName;. If necessary, install

the WinRM component from


LinkId="84599". For more information,

see the installation instructions in the

VMM Planning and Deployment Guide.

419 Agent uninstallation failed on

%ComputerName; because Agent is not

installed.

Verify that Agent is installed on the

computer.


because of an incompatible operating system

version.

Verify that %ComputerName; is running

either Windows Server 2003 SP2 or

Windows Server 2003 R2 operating

system.


because of a WS-Management configuration

error.

In the Local Group Policy Editor

(gpedit.msc), navigate to Computer

Configuration\Administrative

Troubleshooting VMM


Templates\Windows

Components\Windows Remote

Management (WinRM), and then

ensure that there are no policy settings

configured for WinRM Client or WinRM

Service.

422 Machine %ComputerName; is not associated

with this Virtual Machine Manager server.

Check the machine name, and then try


423 Source machine is not associated with this

Virtual Machine Manager server.

Check the source machine name, and


424 The file %FileName; that the parameter -

%Parameter; points to was not found.

Ensure that the required file exists and

is accessible.

425 VMM was unable to import the user

credentials from the security file.

Ensure that the security file is valid and

the key used for encrypting the security

file is correct, and then try the

operation again.

426 The agent is not responding on the perimeter

network machine %ComputerName; because

either the agent is not installed; or

%ComputerName; is not accessible from


Verify that the agent is installed on the

computer, %ComputerName; is

accessible from the Virtual Machine

Manager server, and then try the

operation again.

427 Certificate path not specified during addition

of host %ComputerName; on a perimeter

network.

Specify the location of the certificate

obtained during local agent install on

the host.

428 The agent cannot be uninstalled remotely

from %ComputerName; without specifying

administrator privileges for the machine.

Specify the administrator privileges, and


431 The servers in domain %FriendlyName; cannot

be enumerated.

Check the name, and then try the

operation again.

432 Virtual Server installation was not successful

on %ComputerName;.

Verify that an incompatible version of

Virtual Server is not already installed. If

the error persists, restart

%ComputerName;, and then try the

operation again.

433 The files needed to install Virtual Server are

missing from Virtual Machine Manager server

%ServerName;.

To install the missing files, run Virtual

Machine Manager Server Setup again.

437 Service %ServiceName; could not be stopped

on %ComputerName;.

Stop the service locally in the Services

MMC snapin by running services.msc on

%ComputerName;, choose the service

%ServiceName;, right-click and then

select Stop.

Troubleshooting VMM


438 Service %ServiceName; is not present on

%ComputerName;.

Check that the service exists in the

Services MMC snapin on

%ComputerName; by running

services.msc.

439 VMM is unable to add the server

%ComputerName; as a managed computer

because the server is not listed in Active


Verify that the server name and the

domain name are correct, and then try


440 Virtual Machine Manager is unable to add the

server %ComputerName; as a managed

computer because the operating system is not

supported. Managed computers must be

running Windows Server 2003 SP2 or later.

Ensure that the host is running

Windows Server 2003 SP2 or later. If

the operating system was updated

recently, Active Directory Domain

Services updates might still be pending.

Wait until Active Directory Domain

Services updates run, and then add the

host again.

441 Agent communication is blocked. On

%ComputerName; the version of virtualization

software or the VMM agent is unsupported.

Update the agent and virtualization

software, and then try the operation

again.

444 %ComputerName; is a Virtual Machine

Manager server. A Virtual Machine Manager

server cannot be associated with another



server from %ComputerName; using

Add or Remove Programs on

%ComputerName; and try the

operation again.

445 Service %ServiceName; could not be started

on %ComputerName;.

Start the service locally in the Services

MMC snapin by running services.msc on

%ComputerName;, choose the service

%ServiceName;, right-click and then

select Start.

446 %ComputerName; is not a fully qualified

domain name.

Ensure that %ComputerName; is a fully

qualified domain name, and try the

operation again.


because the supported version of Windows

Remote Management (WinRM) is not

installed.

Download WinRM from


LinkId="84599".

448 The files needed to install Microsoft Core XML

Services (MSXML) 6.0 are missing from Virtual

Machine Manager server %ServerName;.

To install the missing files, run Virtual

Machine Manager Server Setup again.

449 Microsoft Core XML Services (MSXML) 6.0

installation was not successful on

%ComputerName;.


MSXML is not already installed. If the

error persists, restart


operation again.

Troubleshooting VMM


450 The specified host name %FriendlyName; does

not match the name in the security file. The

name in the security file is %ComputerName;.

Ensure that the host name is correct in

the security file and try the operation

again.

451 The Virtual Machine Remote Console (VMRC)

certificate request could not be saved to

%FileName;, since a file with that name

already exists on the specified path.

Delete the existing file, or specify a

different path.

452 Virtual Machine Remote Console (VMRC)

certificate request could not be saved to

%FileName;.

1. Ensure that you have sufficient

permissions to create %FileName;. 2.

Ensure that the specified path is valid.

3. Ensure that the path does not include

an incorrect value for file name,

directory name, or volume label syntax.

453 No Virtual Machine Remote Console (VMRC)

certificate file %FileName; was found on the

Virtual Machine Manager client.

Ensure that you typed the path name

correctly and that a certificate file exists

on the specified path. Then try the

operation again.

454 Virtual Machine Remote Console (VMRC)

certificate file %FileName; is not valid.

Ensure that the file is a valid certificate


458 The Virtual Machine Manager agent could not

be removed from %ComputerName;.



on %ComputerName;.

459 Agent update failed on %ComputerName;. Try the operation again. If the error

persists, reboot %ComputerName; and


460 The file %FileName; that the parameter -

%Parameter; points to exceeds the maximum

size of %MaxLimit; characters.

Ensure that the required file is valid and


461 Virtual Server installation was not successful

on %ComputerName; because of the error:

%DetailedErrorMessage;


Virtual Server is not already installed. If

the error persists, restart


operation again.

462 Microsoft Core XML Services (MSXML) 6.0

installation was not successful on

%ComputerName; because of the error:

%DetailedErrorMessage;


MSXML is not already installed. If the

error persists, restart


operation again.

463 Agent installation failed on %ComputerName;. Ensure that %ComputerName; has

Windows Installer version 3.1 or later

installed, and then try the operation

again.

Troubleshooting VMM


464 Virtual Server cannot be installed because the

driver for mounting virtual hard disks

(vhdstor) is present on %ComputerName;.

Restart %ComputerName; and then try

to install Virtual Server again.

465 The virtual machine configuration could not be

added to %ComputerName; because the

configuration file %FileName; could not be

parsed correctly. It may be damaged.

Ensure that the configuration file is

valid and then try to register the virtual

machine again.


Workgroup Edition cannot manage more than

five hosts.

To manage more than five hosts, you

must upgrade System Center Virtual

Manage Manager. For information

about upgrading, go to


LinkId="117133"


Workgroup Edition cannot manage more than

five hosts.

Remove some of the hosts that you are

trying to add and then try the operation

again. To manage more than five hosts,

you must upgrade System Center

Virtual Manage Manager. For

information about upgrading, go to


LinkId="117133".

468 The specified computer %ComputerName; is a

Windows host cluster, which cannot be added

if the domain of the host does not have a two-

way trust relationship with the domain of the

VMM server or if the host is on a perimeter

network.

Add the cluster as a trusted domain

host.

500 Could not retrieve configuration data from the

virtual machine host %ComputerName;.

Verify that Windows Management

Instrumentation, Windows Remote

Management (WS-Management),

virtualization software, and Virtual

Machine Manager Agent services are

running on %ComputerName;. Then try


501 The virtual machine host %ComputerName;

cannot be removed because one or more

virtual machines are active on the virtual

machine host.

Remove all virtual machines from

virtual machine host %ComputerName;

using Remove-VM, and then try the

operation again.

502 The selected network adapter does not exist

on the virtual machine host.

Verify that the adapter is in the list

obtained by running Get-

VMHostNetworkAdapter -VMHost (Get-

VMHost -ComputerName

%ComputerName;).

503 The specified virtual network Run Get-VirtualNetwork and ensure

Troubleshooting VMM


%VirtualNetworkName; does not exist. that the virtual network is on the list.

504 The virtual network %FriendlyName; already

exists on the virtual machine host.

Check the virtual network name, and


505 Virtual Machine Manager was unable to

create a new virtual network %FriendlyName;.

Check the virtual network name, and


506 The virtual network name

%VirtualNetworkName; contains a character

that is not valid.

Check the virtual network name and

then try the operation again. For a host

that is running Virtual Server, a virtual

network name cannot contain any of

the following characters: *?:<>/|\"

521 The lease renewal time must be less than the

lease rebinding time. Also, the lease rebinding

time must be less than IP address lease time.

Enter a valid lease time, and then try


522 The minimum value allowed for IP lease time

is 60 seconds.



523 The minimum value allowed for lease

rebinding time is 45 seconds.



524 The minimum value allowed for lease renewal

time is 30 seconds.




because of an incompatible operating system

version.

Ensure that %ComputerName; is

running either Microsoft Windows XP or

Windows Server 2003 operating

system.

526 Host configuration failed on

%ComputerName; because no virtual machine

paths are specified.

Ensure that at least one virtual machine

path is specified.

550 VMM cannot access registry key

%RegistryKey;.

Verify that the registry key exists, and


551 VMM cannot access registry key value

%RegistryKeyValueName; under

%RegistryKey;.

Verify that the registry key value exists,


552 The registry key syntax %RegistryKey; is

incorrect.

Ensure that the key is not empty,

contains only valid characters and is less

than 255 characters.

553 The type or name syntax of the registry key

value %RegistryKeyValueName; under

%RegistryKey; is incorrect.

Ensure that the type of value name is

correct; the name is not empty,

contains only valid characters and is less

than 255 characters.

554 Permissions have not been granted to access

the registry key %RegistryKey;.

Verify permissions on this registry key,


Troubleshooting VMM


555 The operation on the registry key

%RegistryKey; was not successful. A system

error occurred, such as deletion of the key, or

an attempt to create a key in the

LocalMachine root, or the nesting level

exceeds 510.

Verify the registry key properties, and


556 VMM cannot delete the registry key

%RegistryKey;. The subkey does not specify a

valid registry subkey, has child subkeys or

deletion of a root hive has been attempted.

Verify that the registry key is present,


606 Virtual Machine Manager cannot locate the

specified answer file %SourceSysprepInfFile;.

Ensure the specified answer file path is

valid, and then try the operation again.

608 Virtual Machine Manager cannot write to the

Sysprep.inf file.

Verify that there is sufficient disk space

on the Virtual Machine Manager server,


609 Virtual Machine Manager cannot detect a

heartbeat from the specified virtual machine.

Either the virtual machine is not running or

Virtual Machine Additions is not installed.

Verify the status of the virtual machine

by connecting to it using Virtual

Machine Remote Client (VMRC), and


610 Virtual Machine Manager was unable to find a

value for the required Sysprep parameter

%SysPrepEntry;.

Add the missing Sysprep parameter

either to the answer file or to the

operating system configuration, and


611 Virtual Machine Manager cannot create the


Ensure that you have specified a valid

path, and then try the operation again.

612 Virtual Machine Manager cannot delete the


You need to delete the folder manually.

613 Virtual Machine Manager cannot delete the

file %FileName;.

You need to delete the file manually.

616 Specify the location of the virtual machine by

its path. You cannot use a UNC name.

Enter the location of the virtual

machine by its path, and then try the

operation again.

617 Virtual Machine Manager cannot find or

cannot access the location %FolderPath;

specified for the virtual machine.

Ensure that the path is valid, and then


619 The -ISO and -HostDrive parameters are

mutually exclusive. You can specify a value for

either the -ISO parameter or the -HostDrive

parameter, but you cannot specify a value for

both parameters in the same operation.

Review the command, and then try the

operation again.

620 The DVD drive must be specified by the drive Review the parameter, and then try the

Troubleshooting VMM


letter, followed by a colon. operation again.

621 The -VirtualFloppyDisk and -HostDrive

parameters are mutually exclusive. You can

specify a value for either the -

VirtualFloppyDisk parameter or the -HostDrive

parameter, but you cannot specify a value for

both parameters in the same operation.


operation again.

622 The floppy drive must be specified by the drive

letter, followed by a colon.

Review the parameter, and then try the

operation again.

623 When the value for the -PhysicalAddressType

Static parameter is specified, a Media Access

Control (MAC) address for the -

PhysicalAddress parameter must also be

specified.

Enter a MAC address for the missing

parameter, and then try the operation

again.

624 If the value for the -PhysicalAddressType

Dynamic parameter is specified, you cannot

specify a value for the -PhysicalAddress

parameter.


operation again.

625 The specified MAC address format is incorrect.

The MAC address format is 00-00-00-00-00-

00.

Enter a valid MAC address, and then try


626 Channels are not available on the IDE bus for

the addition of a new device.

If you are trying to add a virtual hard

disk, add the disk to a SCSI bus, and


627 An additional virtual hard disk (VHD) can be

attached to only one virtual machine at a

time. The VHD %FilePath; cannot be attached

to the new virtual machine because it is

already attached to the virtual machine

%VMName;, which is located on the host

%VMHostName;.

Specify an additional virtual hard disk

that is not attached to any other virtual

machine, and then try the operation

again.

628 There are no available slots on the SCSI bus to

add new devices.

The SCSI bus cannot support the

addition of new devices.

629 The virtual machine must be stopped before a

virtual hard disk can be added.

Stop the virtual machine, and then try


630 The computer name must be a valid IP address

or a name containing letters and numbers.

The computer name cannot contain spaces or

any of the following characters

`~!@#$%%^&*()=+[]{}\|;:'",<>/? .

Specify a valid computer name, and


631 The product identification number must use

the format xxxxx-xxxxx-xxxxx-xxxxx-xxxxx.

Specify a valid product identification

number, and then try the operation

Troubleshooting VMM


again.

632 The passwords you have entered do not

match.

Enter the password again.

633 You must enter valid values for the domain

name, domain user, and domain password

entries to join a domain. One or more of the

values you have entered for joining the

domain are not valid.

Verify the values for the domain name,

domain user, and domain password

entries, and then try the operation

again.

634 The workgroup name cannot contain more

than 15 letters or numbers. The value you

have entered is not valid.

To join a workgroup, enter a valid value

for the workgroup name, and then try


635 Virtual Machine Manager is unable to securely

store the password information on this

machine.

Ensure that the Microsoft Cryptographic

Service has been installed on the Virtual

Machine Manager server and try the

operation again.

636 Virtual Machine Manager is unable to retrieve

previously stored password information.

Either restore the key data from a

previous backup or enter the

information again.

637 Virtual Machine Manager is unable to find a

value for one or more required Sysprep

parameters, such as FullName,

ComputerName, or ProductKey.

Ensure that all required values are

specified, and then try the operation

again.

638 Virtual Machine Manager is unable to find a

value for one or more required Sysprep

parameters, such as FullName,

ComputerName, or ProductKey.

Verify the values are specified in the

Sysprep script, and then try the

operation again.

639 Virtual Machine Manager does not support

the specified processor type.

Select a supported processor, and then


640 The virtual machine must be in either the

Poweroff or Stored state before SCVMM can

perform the specified hardware changes.

Turn off the virtual machine or store it

to the library, and then try the

operation again.

641 VMM cannot perform the specified media

change because the virtual machine is

currently in an error, transitional, or a failed

state.

Change the state, and then try the

operation again.

642 The virtual machine must be turned off before

Virtual Machine Manager can update the

network configuration changes.

Turn off the virtual machine, and then


643 Unable to set virtual machine memory to

%MemorySize; MB.

Ensure the virtual machine host has

specified available memory, and then


Troubleshooting VMM


644 The specified host drive %DriveName; does

not exist on the host machine.

Modify the virtual DVD drive property

to connect to an existing host drive.

645 The specified host drive %DriveName; does

not exist on the host machine.

Modify the virtual floppy drive property

to connect to an existing host drive.

646 Slots are not available on the network

adapters bus for the addition of new devices.

The network bus cannot support the

addition of new devices.

647 The timezone is not valid. Refer to the Sysprep documentation for

valid values for timezone, and then try


658 The bus location for the object

%FriendlyName; at (%BusType;, %Bus;, %Lun;)

is not valid.

Ensure the bus location values are valid,


659 Another device is already at the location

(%BusType;, %Bus;, %Lun;).

Select another destination for the disk,


660 LUN ID 7 is reserved for SCSI adapters and is

not available for use.

Select another destination for the disk,


661 This operation cannot be completed because

the virtual machine must be turned off.

Shutdown the virtual machine and try


662 The library virtual hard disk does not support

SCSI, IDE, bus or LUN switches.

Verify that you are using the correct

command, and then try the operation

again.

663 The -Name parameter cannot be empty or

contain spaces for object %ObjectType;.

Provide a valid name for the object, and


664 A virtual hard disk %FileName; cannot be

attached to the same virtual machine or

template more than once directly or via

differencing disk.

Attachment of a virtual hard disk to a

virtual machine or template multiple

times is not supported.

665 The swap operation requires a disk to be

connected to a virtual machine or template.

Verify that there is a valid connection,


666 To perform a swap operation both disks need

to be connected to the same object.

Verify that both disks are connected to

the same object, and then try the

operation again.

667 The swap operation is not supported on

virtual hard disks stored in the library.

Verify that the virtual hard disks are

stored in a valid location, and then try


668 A SCSI adapter does not exist on bus %Bus;. Verify the contents of bus %Bus;, and


669 The virtual machine must be run under a user

account in order to use the -StartAction and -

Use the -RunAsUserCredential to

specify the user account, and then try

Troubleshooting VMM


DelayStart parameters. the operation again.

670 The -RunAsUserCredential command requires

a valid account and password.

Enter a valid account and password, and


671 The -RunAsSystem and -RunAsUserCredential

command cannot be specified at the same

time.

Run each command separately.

672 The template being created should contain at

least one virtual hard disk.

Specify at least one virtual hard disk,


673 The Boot.ini file is not on specified boot virtual

hard disk that Sysprep need to be run on.

Specify a valid boot virtual hard disk,

and then run Sysprep.

674 The Boot.ini file does not contain the value for

the entry Section = %SysprepSection; Key =

%SysprepKey;.

Specify a valid boot virtual hard disk,

and then run Sysprep.

675 Unable to run Sysprep because the boot

virtual hard disk does not contain any

volumes.

Specify a valid boot virtual hard disk.

676 The Windows and System partitions are

different. Sysprep is not supported.

Specify a virtual machine that has the

same boot and windows partition, and


677 This operating system %SoftwareVersion; is

not supported when creating a template.

Select another virtual machine to create

the template from, and then try the

operation again.

678 Sysprep binary %FileName; does not exist for

Windows version %SoftwareVersion; in Folder

%FilePath;.

Add the missing Sysprep binaries for the

specified Windows version in the

specified folder, and then try the

operation again.

680 Timeout occurred while waiting for Sysprep to

finish processing on the virtual machine.

Ensure you are using the version of

Sysprep binaries that match with virtual

machine's Windows version, and then


682 A template cannot be created from virtual

machine %VMName;.

Stop or shut down the virtual machine,


685 This job cannot be restarted until the virtual

machine %VMName; is repaired.

Run Repair-VM to complete the job.

686 The version of Virtual Server on host

%VMHostName; is not the supported VS R2

SP1 version.

The selected virtual machine cannot run

sysprep. Upgrade Virtual Server, and


687 Virtual machine %VMName; creation cannot

restart. To restart a virtual machine must be in

the Creation Failed or Customization Failed

Provide a valid virtual machine to

restart the creation process.

Troubleshooting VMM


state.

688 To join a domain both parameters; -

JoinDomain and -JoinDomainCredential must

be specified.

Verify that both parameters are

included, and then try the operation

again.

689 The -JoinWorkgroup and -JoinDomain

parameters cannot be used together.

Specify either -JoinWorkgroup or -

JoinDomain parameters, and then try


691 Virtual machine %VMName; cannot be cloned.

A virtual machine must be in Poweroff or

Stored state in order to be cloned.



operation again.

692 Virtual Machine Manager cannot join

%ObjectType; %FriendlyName; to the domain

without a network adapter.

Add at least one network adapter to the

virtual machine or template, and then


694 If you specify parameter -NoConnection, you

cannot provide -VirtualNetwork.

Specify either -NoConnection or -

VirtualNetwork parameter.

695 Either user credentials are required to

perform this operation or virtual machine has

to be set to run as system.

Either use the -RunAsUserCredential to

specify the user account or -

RunAsSystem to specify system

account, and then try the operation

again.

696 A virtual SCSI adapter can only be attached to

Lun ID 6 or 7.

Review your command parameters and


697 Source template %FriendlyName; is not in a

valid state.

Select a template in that is in a valid

state.

698 An ISO %FileName; cannot be attached to the

same virtual machine, template or hardware

profile more than once.

Attach an ISO image to a virtual

machine, template or hardware profile

only once. Attachment of an ISO image

to a virtual machine, template or

hardware profile via multiple DVD

drives is not supported.

706 Sysprep failed for virtual machine %VMName;. Try the operation again.

707 Cannot dismiss sysprep failure for virtual

machine %VMName; as virtual machine is not

recoverable.

Retry sysprep or remove virtual

machine.

708 Can only convert virtual hard disks belonging

to a virtual Machine that is present on a

virtual machine host.

Select a virtual hard disk attached to a

virtual machine on the host, and then


709 Virtual hard disk conversion is supported only

for virtual hard disks that are fixed or

dynamically expanding.

Select a virtual hard disk that is either

fixed or dynamically expanding, and


Troubleshooting VMM


711 SCVMM cannot change the name of the virtual

machine because the virtual machine is not in

either a Poweroff or Stored state.



operation again.

712 A virtual machine must be in either the

Poweroff, Saved, or Stored state to change the

RunGuestCredential virtual machine property.

Turn off the virtual machine, save the

virtual machine state, or store the

virtual machine in the library, and then


713 SCVMM cannot modify StopAction property of

the virtual machine because it is in either an

unsupported, transitional, or a failed state.

If the virtual machine is in a transitional

state, wait for the operation to

complete, and then try the command

again. If the virtual machine is in a failed

or unsupported state, repair the failure,


714 SCVMM cannot modify the virtual machine

because it is in either an unsupported,

transitional, or a failed state.

If the virtual machine is in a transitional

state, wait for the operation to

complete, and then try the command

again. If the virtual machine is in a failed

or unsupported state, repair the failure,


715 The option %RepairOption; is not supported

for repairing the virtual machine %VMName;

in state %FromState;.

>Use an option supported by the state

%FromState;, and then try the

operation again.

716 CPUReserve value (%CPUReserve;) cannot be

greater than CPUMax value (%CPUMax;).

Please review your parameters and run

the command again.

717 The compact virtual hard disk %FileName;

operation timed out after waiting for

%VHDActionTimeoutInHours; hours.


718 The convert virtual hard disk %FileName;




719 The create virtual hard disk %FileName;




722 The virtual machine cannot be repaired

because the last job that ran on the virtual

machine is no longer available.

Repair the virtual machine, using the

dismiss option if it is available.

Otherwise, copy the files of the virtual

machine to a new location and recreate

the VM. To find the associated files, use

the Get-VM cmdlet from the command

line to retrieve the VM object. View the

properties of the VM object to retrieve

the location of the files.

723 Unable to restart the specified job. Only the Use the Repair VM action to repair the

Troubleshooting VMM


most recent job that ran on the virtual

machine %VMName; can be restarted.

virtual machine.

728 The operation to expand virtual hard disk

%FileName; timed out after


Retry the operation again.

729 The specified size for virtual hard disk

%FileName; must be larger than its current

size and less than the maximum size

supported by Hyper-V.

Specify a valid size and then try the

operation again.

730 Parameters cannot be specified for the guest

operating system because the selected

template was created as a non-customizable

template (-NoCustomization parameter).

Please retry the operation without

specifying guest operating system

parameters.

733 File %FileName; was removed from Virtual

Machine Manager, but it could not be deleted

from host %VMHostName; because VMM

does not have sufficient rights to delete this

file.

If the fileis no longer needed, manually

delete it from the host.

735 Parameters cannot be specified for the guest

operating system when creating a non-

customizable template.

Review the command, and try the

operation again.

800 VMM cannot find %FilePath;. Ensure the path parameter value is


801 VMM cannot find %ObjectType; object

%FriendlyName;.

Ensure the library object is valid, and


802 The %ObjectType; file %FilePath; is already in

use by another %ObjectType;.

Wait for the object to become available,


803 Virtual machine %FriendlyName; already

exists on the virtual machine host

%VMHostName;

Specify a new name for the virtual

machine, and then try the operation

again.

804 The template %FriendlyName; already exists. Specify a unique name for the template,


807 The file location path must be a shared path. Specify the shared path as

\\servername\sharename, and then try


808 VMM cannot access the specified file because

access is denied. VMM must have the proper

permissions to the file for access.

Change the file access permissions, and


809 VMM cannot remove the virtual machine

because it is in the %FromState; state.

Change the virtual machine's state, and


Troubleshooting VMM


811 VMM cannot add a virtual hard disk that is

associated with a virtual machine.

Specify a virtual hard disk that is not

associated with a virtual machine, and


812 VMM cannot remove the disk because it is the

parent of a differencing disk.

Remove all differencing disks associated

with the parent disk, and then try the

operation again.

813 The specified owner is not a valid Active

Directory Domain Services account.

Specify a valid Active Directory Domain

Services account, and then try the

operation again.

814 Cannot remove virtual disk because a virtual

machine is using this virtual disk.

To remove this virtual disk, remove this

virtual disk object from the virtual

machine using this virtual disk.

815 VMM cannot remove this library object

because a virtual machine, template,

hardware or guest operating system profile is

using it.

To remove the library object, remove it

from all virtual machines, templates,

hardware and guest operating system

profiles that are using it.

816 A valid name is required to complete this task. Specify a valid name.

817 VMM cannot add %FileName; as

%ObjectType;. The file extension of

%FileName; does not match the supported file

extensions for %ObjectType;.

Specify a file with a file extension that

matches %ObjectType;, and then try the

operation again.

818 VMM cannot find the library share. Specify a valid library share, and then


819 Library share %FriendlyName; already exists. Specify a unique library share name,


820 The path %SharePath; is not a share. Specify a valid path for the share, and


823 VMM cannot compact a virtual hard disk in

the Library.

Compact the virtual hard disk on the

virtual machine host instead.

824 VMM cannot link to this ISO because it is not a

standalone ISO stored in a library.

Store the ISO image in the library or link

to an ISO image in the library, and then


825 VMM cannot remove this library share since

%ObjectType; %FriendlyName; is referenced

in both this library share and another library

share.

Remove %ObjectType; %FriendlyName;


826 Unable to add library share %SharePath;

because the library share's local path,

%FilePath;, is the parent or child folder of an

existing library share.

Use an independent share, and then try


Troubleshooting VMM


827 Unable to perform this operation because the

destination share, %SharePath;, either is not a

library share in Virtual Machine Manager or is

not present on library server %ServerName;.

Ensure the share path is on a library

share on the specified library server,

add the share to Virtual Machine

Manager as a library share, or select a

different library share.

828 The %ObjectType; "%FriendlyName;" already

exists.

Specify a different name for the

%ObjectType; being edited

834 The path %FileName; is not a registered share

path on the library server %ComputerName;.

Specify a valid share path on

%ComputerName;.

835 SCVMM does not have permissions to access

the share %ShareName; on the library server

%ComputerName;.

Ensure that both Local System and

Virtual Machine Manager Servers

groups have full access to the share on

%ComputerName;.

842 VMM cannot expand a virtual hard disk in the

Library.

Expand the virtual hard disk on the

virtual machine host instead.


transferred. To be transferred, a virtual

machine must be stopped, shut down, in a

saved state or stored in the library. A virtual

machine in a failed state cannot be

transferred

Stop, shut down, or save the virtual

machine. If the virtual machine is in a

failed state, use "Repair virtual

machine" to repair the virtual machine.

Then try the operation again.

1202 You cannot migrate a virtual machine to the

location where it currently resides.

Specify a new location to transfer the

virtual machine, and then try the

operation again.

1204 The server %VMHostName; does not contain

any host bus adapter (HBA) ports. Fibre

Channel SAN transfer cannot be used.

Transfer the virtual machine over the

LAN.

1205 Virtual Machine Manager cannot transfer

virtual machine %VMName; over the SAN

because the host %VMHostName; does not

have a Virtual Disk Service (VDS) hardware

provider installed.

Instead, transfer the virtual machine

over the LAN or install a VDS hardware

provider on the host.

1206 A Virtual Disk Service (VDS) error occurred on

server %VMHostName;.


1207 Virtual Machine Manager cannot transfer the

virtual machine %VMName; over the SAN

because the virtual machine resides on a

volume that maps to a dynamic disk.


LAN, or see the Virtual Machine

Manager Planning and Deployment

Guide for information about using a

SAN.

1208 Virtual Machine %VMName; is on a volume

which maps to multiple disks. SAN transfer

cannot be used.




Troubleshooting VMM



SAN.

1209 Virtual Machine %VMName; resides on a non

SAN disk. SAN transfer cannot be used.





SAN.

1210 The Virtual Machine %VMName; is placed on a

SAN which does not support globally unique

identifiers for LUNs. SAN transfer cannot be

used.


over the LAN.

1211 Unable to access Virtual Disk Service (VDS) 1.1

interface on server %VMHostName;.

To finish installing VDS 1.1, restart

%VMHostName; to complete the

installation.

1212 Virtual Machine %VMName; is placed on a

basic disk which contains other volumes. SAN

transfer cannot be used.


over the LAN, or see Virtual Machine

Manager Help for information about

using a SAN.

1213 Unable to mount volume at %FolderPath; on


Ensure that the path %FolderPath;

exists and that the folder is empty.

Ensure that another volume is not

mounted at this path, and then try the

operation again.

1214 Virtual Machine %VMName; resides on a LUN,

which cannot be found.

Ensure that the LUN, which contains

virtual machine %VMName;, is

unmasked to virtual machine host

%VMHostName;. Then try the operation

again.

1215 An error has occurred while dismounting the

volume at location %FolderPath;.

For more information, check the event

log of the virtual machine host, and


1216 The required version of Virtual Disk Service

(VDS) is not installed on server

%VMHostName;.

Install VDS 1.1 on the virtual machine

host %VMHostName;, and then try the

operation again.

1217 The files of virtual machine %VMName; reside

on different LUNs. SAN transfer cannot be

used.


over the LAN, or see Virtual Machine

Manager Help for information about

using a SAN.

1219 The file system path %FolderPath; associated

with virtual machine %VMName; is not valid.

Ensure the virtual machine %VMName;

exists and the path %FolderPath; is


1220 The file %FileName; was not transferred Try the operation again.

Troubleshooting VMM


correctly.

1221 Virtual Machine %VMName; cannot be

transferred over the SAN because it contains

virtual disks that are shared with other virtual

machines.

Verify that the virtual machine does not

contain differencing disks that are

shared with other virtual machines or

transfer the virtual machine over the

LAN.

1222 There is insufficient disk space on the volume

%SystemVolumeDriveLetter; on server

%VMHostName; to complete the transfer.

Free %BinaryDiskSpaceRequired; MB of

disk space on the volume


%VMHostName; to transfer virtual

machine %VMName; to %FolderPath;.

1223 Virtual machine %VMName; already exists on

virtual machine host %VMHostName;.

Transfer virtual machine %VMName; to

a different host, and then try the

operation again.


transferred because it is associated with two

files with identical names - %SourceFile1;,

%SourceFile2;.

Disassociate one of the files from the

virtual machine %VMName; or rename

the file by performing the following

steps: 1. Disassociate the file from the

virtual machine 2. Rename the file 3.

Associate the file with the virtual

machine.

1227 The target location for a SAN transfer

%FolderPath; cannot be on a FAT volume.

Specify a different target location on an

NTFS volume, and then try the

operation again.

1228 The server %VMHostName; cannot recognize

the LUN that virtual machine %VMName; is

placed on.

Check your Fibre Channel zoning policy

to ensure that the server

%VMHostName; can recognize the LUN

virtual machine %VMName; is placed

on. If you have recently changed your

Fibre Channel configuration wait

approximately 30 minutes and try the

operation again. If server

%VMHostName; is a virtual machine

host you can manually refresh the

properties by using the Refresh-VMHost

cmdlet.

1229 The server %VMHostName; cannot recognize

the LUN that virtual machine %VMName; is

placed on.

Check your iSCSI configuration to

Ensure that the server %VMHostName;

can connect to the iSCSI target Virtual

machine %VMName; is placed on. If you

have recently changed your iSCSI

configuration, wait approximately 30

minutes and try the operation again. If

server %VMHostName; is a virtual

machine host you can manually refresh

Troubleshooting VMM


the properties by using the Refresh-

VMHost cmdlet.

1230 There are multiple virtual machines

%NameList; on the LUN that virtual machine

%VMName; is placed on. SAN transfer cannot

be used.


LAN.

1231 The server %VMHostName; does not have the

Microsoft iSCSI Initiator installed. iSCSI SAN

transfer cannot be used.


LAN.

1232 An error occurred while logging off the iSCSI

initiator on server %VMHostName; from

target %IscsiTargetName;.

Check the event log of server

%VMHostName; for more information.

Verify that all open file handles on any

of the disks of iSCSI target

%IscsiTargetName; are closed, and try


1233 The iSCSI initiator on server %VMHostName; is

unable to log on to target %IscsiTargetName;.

For more information, check the event

log of server %VMHostName;, and then


1234 The virtual machine %VMName; is exposed to

a target which contains other LUNs. iSCSI

transfer is not possible.


LAN.

1235 The iSCSI target %IscsiTargetName; is not

visible to machine %VMHostName;.

Check your iSCSI configuration and then


1236 The iSCSI subsystem %FriendlyName; is not

visible to machine %VMHostName;.

Check your iSCSI configuration and

verify that iSCSI subsystem

%FriendlyName; is visible to virtual

machine host %VMHostName;, and


1238 The virtual machine %VMName; cannot be

transferred because it is located in a

perimeter network.

Ensure that the selected virtual

machine is not in a perimeter network,


1240 The file %FileName; is already present on


Move the file %FileName; to a different

location, and then try the operation

again.

1242 The specified target path %SharePath; is not

on a VMM library share on server

%VMHostName;.

Specify a location that is on a library

share, and then try the operation again.


which is not visible to the Virtual Disk Service

(VDS) hardware provider on machine

%VMHostName;.

Ensure that the Virtual Disk Service

(VDS) Hardware provider is installed

and running on machine

%VMHostName;. Then try the operation

again.

Troubleshooting VMM


1248 VMM cannot access the file or folder

%FileName; because it is encrypted.

Remove the encryption from file or

folder %FileName; and retry the

operation.

1249 The server name specified in the target path

%SharePath; does not match the fully

qualified domain name of the selected VMM

library server - %VMHostName;.

Specify the FQDN of the library server in

the target path, and then try the

operation again.

1250 Virtual Machine %VMName; cannot be

transferred over the SAN because it contains

an ISO - %FileName; that is shared with other

virtual machines.

Ensure the virtual machine does not

contain an ISO that is shared with other

virtual machines, or transfer the virtual

machine over the LAN.


which does not have a volume on machine

%VMHostName;.

If the LUN was recently moved, wait for

the volume on the LUN to arrive and


1252 The server %VMHostName; does not have an

HBA which supports NPIV.

If server %VMHostName; contains an

HBA that supports NPIV, ensure that the

right version of firmware and driver are

installed, or transfer the virtual machine

over the LAN.

1253 NPIV transfer cannot be used because the

server %VMHostName; does not have a

Microsoft MPIO solution installed.


LAN.


virtual machine %VMName; is not stored on a

LUN that is unmasked to a Virtual Port.


LAN.

1255 An unknown error occurred performing an

NPIV operation on server %VMHostName;.


1256 The physical port %PhysicalWWPN; on server

%VMHostName; already has the maximum

%MaxLimit; virtual ports.

Select a different server and try the

operation again


physical port %PhysicalWWPN; on server

%VMHostName; is connected to a fabric that

does not support NPIV.


operation again

1258 The creation of virtual port %VirtualWWPN;

on server %VMHostName; failed due to lack of

resources.

Ensure that server %VMHostName; has

enough memory and try the operation

again

1259 A virtual port with WWPN %VirtualWWPN;

already exists on server %VMHostName;.


operation again.

1260 The format of the WWPN of virtual port

%VirtualWWPN; is not valid.

Specify a valid WWPN and then try the

operation again.

Troubleshooting VMM


1261 An NPIV operation failed on server

%VMHostName; because the SAN link is not

operational.

Ensure that the server %VMHostName;

is connected to the SAN and then try


1262 The virtual port %VirtualWWPN; does not

exist on server %VMHostName;.

Ensure that the virtual port

%VirtualWWPN; exists on server

%VMHostName; and then try the

operation again.

1263 The format of the tag of the virtual port

%VirtualWWPN; - %VirtualTag; is not valid.

Specify a valid tag and then try the

operation again.

1264 The format of the symbolic name of the virtual

port %VirtualWWPN; -

%VirtualSymbolicName; is not valid.

Specify a valid symbolic name and then


1265 The format of the WWNN - %VirtualWWNN;

of the virtual port %VirtualWWPN; is not valid.

Specify a valid WWNN and then try the

operation again.

1266 The format of the WWPN of the physical port -

%PhysicalWWPN; of virtual port

%VirtualWWPN; is not valid.

Specify a valid WWPN and then try the

operation again.

1267 The HBA %AdapterPNPInstanceName; was not

found on server %VMHostName;.

Ensure that the adapter exists and then


1268 Virtual machine %VMName; could not be

moved to virtual machine host

%VMHostName; using this cluster

configuration.

Check the cluster configuration and


1269 Unable to move virtual machine %VMName;

over LAN because pass-through disks are

attached.

Convert the pass-through disks to

virtual hard disks. Otherwise, remove

the pass-through disks and then try the

operation again.

1270 %DetailedErrorMessage; Try the operation again.

1271 %DetailedErrorMessage; Try the operation again.


moved to virtual machine host

%VMHostName; because the target path was

not specified.

Specify a valid target path and then try



moved because it has checkpoints.

Remove all of the checkpoints and then


1274 Saved Virtual machine %VMName; cannot be

transferred over the SAN because it has pass-

through disks.

Delete the saved state and then try the

operation again.


moved to Hyper-V host %VMHostName;



Troubleshooting VMM


because it has checkpoints.


transferred. Volume


%VMHostName; is unavailable for placement.

Select a volume that is available for

placement.

1278 Virtual machine %VMName; cannot be moved

to host %VMHostName;. The source and

destination hosts have incompatible

virtualization software.

Use a different destination host.


moved because it has snapshot virtual hard

disks.

Remove all of the checkpoints, merge

the snapshot virtual hard disks (.avhd),


1281 %VMName; could not be migrated because it

is a VMware template.

Select a virtual machine instead of a

template and try the operation again.


moved because it has checkpoints.

Checkpoints are not supported for VMware

virtual machines.



1283 VMM cannot transfer the virtual machine

%VMName; over the SAN because this virtual

machine is placed on multiple LUNs of

different SAN types.

Ensure that virtual machine is placed on

single type of SAN LUN or transfer the

virtual machine over the LAN.

1284 Unable to migrate virtual machine %VMName;

to host %VMHostName; over the SAN because

SAN transfers between clustered and non-

clustered hosts are not supported.


LAN.

1285 Virtual Machine Manager cannot perform

hardware configuration changes on virtual

machine %VMName; because it has snapshots

or saved state. This functionality is not

supported in the VMM library for Hyper-V

virtual machines with saved state or

snapshots.

Deploy the virtual machine to a Hyper-V

host and then try the operation again.

1286 Virtual machine %VMName; on

%VMHostName; could not be stored because

it is in saved state.

Discard the saved state and then try the

operation again.

1287 Virtual machine %VMName; on

%VMHostName; could not be stored because

it has multiple virtual hard disks with the same

name %FileName;.

Rename the virtual hard disks to have

unique names and then try the

operation again.


migrated to or from VMware ESX Server host

Retry the operation after the host is out

of maintenance mode. To end

Troubleshooting VMM


%VMHostName; because the host is in

maintenance mode.

maintenance mode, use VMware

VirtualCenter.

1401 You do not have the permission required to

perform this operation.


administrator to obtain the appropriate

permissions.

1408 Cannot locate the user role because it no

longer exists.

Close and reopen Windows PowerShell,


1410 The template %FriendlyName; has already

been added to this user role.

Select a different template, and then try


1417 Virtual Machine Manager cannot find a

domain account for member %UserName;.

The user role member must have an

Active Directory Domain Services

account. Try the operation again with a

valid domain account.

1600 VMM is unable to process one or more of the

provided cmdlet parameters.

Type Get-Help %CmdletName; -full to

view a list of defined parameters and

complete descriptions. Then try the

operation again.

1601 VMM is unable to connect to the Virtual

Machine Manager server %ServerName;

because the specified computer name could

not be resolved.

Ensure that the computer name is

correct, and then try the operation

again. If the problem persists, contact

your network administrator.

1602 Unable to connect to the Virtual Machine

Manager server %ServerName;. The Virtual

Machine Manager service on that server did

not respond.

Verify that Virtual Machine Manager

has been installed on the server and

that the Virtual Machine Manager

service is running. Then try to connect

again. If the problem persists, restart

the Virtual Machine Manager service.

1603 Unable to connect to the Virtual Machine

Manager server %ServerName;. The attempt

to connect timed out.

1) Verify that %ServerName; is online

and can be accessed from your

computer.\n2) If a firewall is enabled on

%ServerName;, ensure that it is not

blocking requests for TCP port

%RemoteUIPort;.

1604 You cannot access Virtual Machine Manager

server %ServerName;.


administrator to verify that your

account is a member of a valid user role


1605 You cannot contact the Virtual Machine

Manager server. The credentials provided

have insufficient privileges on %ServerName;.

Ensure that your account has access to

the Virtual Machine Manager server

%ServerName;, and then try the

operation again.

1606 Unable to connect to the Virtual Machine Verify that the server name and port

Troubleshooting VMM


Manager server %ServerName; on port

%RemoteUIPort;.

number are correct.

1607 You cannot contact the Virtual Machine

Manager server. The credentials provided

have administrator privileges instead of Self-

Service only privileges on %ServerName;.

Use the troubleshooting mode of the

Self-Service portal, and then try the

operation again.


Manager server %ServerName; was lost.

Ensure that %ServerName; is online and

that you can access the server remotely

from your computer. Then connect to

%ServerName; and try the command

again using the new connection. Or, you

can ensure that the Virtual Machine

Manager service is started on

%ServerName;. Then connect to

%ServerName; and try the command

again using the new connection. If the

command fails again because of a

connection failure, restart the Virtual

Manager service and then try the

operation again.

1611 Unable to retrieve the result of the job

because the connection to the Virtual

Machine Manager server %ServerName; was

lost. The job will continue running on

%ServerName; until it completes.

1) Verify that %ServerName; is online

and can be remotely accessed from

your computer.\n2) Verify that the

Virtual Machine Manager service is

started on %ServerName;. If the

problem persists, restart the Virtual

Machine Manager service.\n\nTo find

out the result of the job, re-connect to

the server, and run the following

cmdlet:\nPS> Get-VMMServer

%ServerName; | Get-Job | where {

$_.ID -eq "%TaskID;"}

1615 VMM is unable to perform this operation

without a connection to a Virtual Machine

Manager server.

Use the Get-VMMServer cmdlet or the -

VMMServer parameter to connect to a

Virtual Machine Manager server. For

more information, type at the

command prompt: Get-Help Get-

VMMServer -detailed.

1616 Unable to start VMMService because the

VMM database has more than five hosts.

VMM Workgroup Edition can manage a

maximum of five hosts. Uninstall the

Virtual Machine Manager server using

the "Remove data" option, or upgrade

VMM Workgroup Edition to manage

more than five hosts. Find information

on upgrading at


LinkId="94662".

Troubleshooting VMM


1617 Unable to log on by using the specified

credentials.

Verify that the credentials specified are

correct and then try logging on again.

1618 Unable to log on because a connection could

not be established.


administrator to verify that the user

account is still active and then try

logging on again.

1619 Unable to log on because access was denied. Contact the Virtual Machine Manager

administrator to verify that the Self-

Service Portal Web site is running under

the NETWORK SERVICE identity and that

no restrictions have been placed on this

account that would prevent

impersonation.

1700 The Virtual Machine Manager service on the

%ServerName; server stopped while this job

was running. This may have been caused by a

system restart.

Restart the job by running the following

command:\n\nPS> Restart-Job -Job

(Get-VMMServer %ServerName; | Get-

Job | where { $_.ID -eq "%TaskID;"})

1701 The job was stopped by the user %UserName;. Restart the job by running the following

command:\n\nPS> Restart-Job -Job

(Get-VMMServer %ServerName; | Get-

Job | where { $_.ID -eq "%TaskID;"})

1703 Unable to start the cmdlet %CmdletName; for

JobGroup %TaskID;. One or more of the

cmdlets is not valid for inclusion in that

JobGroup.

For a description of the cmdlets in this

type of JobGroup, see the help for

cmdlet %CmdletName;.

1708 The %JobName; job cannot be restarted. Wait for the object to be updated

automatically by the next periodic

%JobName; job.

1709 The %JobName; job cannot be canceled. Wait for the job to finish.

1710 The %JobName; job requires alternate user

credentials before it can be restarted.

Restart the job by supplying the

credential parameter to the Restart-job

cmdlet.

1730 The selected action could not be completed

because the virtual machine is not in a state in

which the action is valid.

Check the state of the virtual machine,

and verify that the selected job can be

run on a virtual machine in that state.

1732 The specified action could not be performed

on virtual machine %VMName;. The request

to change the state timed out.

Verify that the virtual machine is online,

and then run the command again.

1733 Could not refresh virtual machine %VMName;. Ensure that the virtual machine exists

and that the WMI service is running on

virtual machine host %VMHostName;,


Troubleshooting VMM


1735 The virtual machines cannot be shut down

because Virtual Guest Services is not installed

on the guest operating system: %ObjectList;,

or because the installed Virtual Guest Services

does not support shutting down of the guest

operating system that is running on the virtual

machine.

To shut down, you must install Virtual

Guest Services that support the shutting

down of the guest operating system.


stored to a library server because its host is on

a perimeter network.

Virtual machines cannot be transferred

from hosts on perimeter networks

because of security concerns. For more

information about how to add a host in

the perimeter network go to Virtual

Machine Manager Help.


migrated to a different host because its

current host is on a perimeter network.

Virtual machines cannot be transferred

from hosts on perimeter networks

because of security concerns. For more

information about how to add a host in

the perimeter network go to Virtual

Machine Manager Help.

1749 The host group name contains a character that

is not allowed (*?:<>/|\").

Specify a valid host group name.

1750 Unable to find the specified host group. The

host group name may be incorrect, or the host

group may have been moved or deleted.

Verify that the host group name is

correct, that the host group exists on

the Virtual Machine Manager server,

and that the host group is in the

specified host path.

1751 Unable to assign the name %VMHostName; to

this host because this name is already in use.

Specify a unique name for the host, and


1752 Unable to assign the host group the name

%HostGroupName; in the specified path

because another host group at the same level

already has that name.

Specify a unique name or location for

the host group, and then try the

operation again.

1753 Unable to modify host group

%HostGroupName; because the host group

has been deleted.

To update the list of host groups,

restart the Virtual Machine Manager

service, or wait until the host groups list

is automatically refreshed.

1755 Unable to delete host group

%HostGroupName; because the host group is

not empty. The host group may have hosts

assigned to it, or hosts may be assigned to

child host groups of this host group.

Remove all hosts from this host group

and from any child host groups that the

host group contains. Then retry this

command.

1756 Unable to move a host group to itself. Specify a different parent host group for

the host group %HostGroupName;.

Troubleshooting VMM


1757 Unable to move this host group to the

%HostGroupName; host group because the

specified host group is a child of this host

group.

Choose a different host group to be the

new parent of the %HostGroupName;

host group.

1777 Virtual machine %VMName; cannot be cloned

or migrated. To be cloned or migrated, a

virtual machine must be stored in the library

or turned off.

Stop or shut down the virtual machine,


1778 To be stored in the library, the virtual machine

must be stopped or in a saved state.

Save state, stop or shut down the

virtual machine, and then try the

operation again.

2200 Could not find the specified virtual machine

checkpoint.

Ensure the specified virtual machine

checkpoint exists and try the operation

again.

2206 Virtual machine %VMName; cannot be used

for any checkpoint actions. For checkpoint

actions, a virtual machine must be running,

stopped, paused or in a saved state.

Ensure that the virtual machine is

running, stopped, paused or in a saved

state, and then try the command again.

2207 A new checkpoint for virtual machine

%VMName; cannot be created because it

exceeds the maximum of %Count; checkpoints

allowed.

To create a new checkpoint for virtual

machine %VMName;, remove an older

checkpoint.


%DatabaseName; could not be backed up at

%FolderPath;.

Ensure that the specified folder exists, is

not a root directory and is accessible to

the SQL server.

2209 Failed to recover database %DatabaseName;

from location %FileName; to SQL server. The

SQL error is:\n%DetailedErrorMessage;

Ensure that the specified file is a valid

VMM database backup.

2210 The path %FileName; specified for Virtual

Machine Manager database backup file is not

valid.

Ensure that the specified path is valid

and that the Virtual Machine Manager

database backup file exists on that path.

2211 An error has occurred while trying to remove

all connections to database %DatabaseName;.

Ensure that the SQL Server service can

be started and that you have

permissions to query the SQL Server.

2212 The command is not valid. Check the specified parameters and try

the command again.

2213 There are no virtual hard disks attached to

%VMName;.

To create a checkpoint, add a virtual

hard disk to the virtual machine, and


2214 Checkpoint actions on virtual machine

%VMName; are unsupported because one or

Ensure that the virtual machine doesn't

share any hard disks with other virtual

Troubleshooting VMM


more hard disks are shared with other virtual

machines. The shared hard disks are:

%ObjectList;.

machines.

2216 Checkpoint creation on virtual machine

%VMName; is unsupported because the

virtual machine contains virtual hard disk

%FileName;, and the path length of the

checkpoint disk for this hard disk will exceed


Transfer the virtual machine to a

location where the path is shorter, or

reduce the length of the virtual hard

disk's filename and try the operation

again.

2217 Checkpoint actions can be performed only for

virtual machines that are on a host. Virtual

machine %VMName; is in the library.

Place the virtual machine on a host and


2219 A new checkpoint cannot be created for

virtual machine %VMName; because it is

attached to one or more pass-through disks

Ensure that the virtual machine is not

attached to any pass-through disks and

then try the command again.


virtual machine %VMName;. The virtualization

software on host %VMHostName; does not

allow a new checkpoint to be created for a

virtual machine that is paused.

Ensure that the virtual machine is

running, stopped, or in a saved state



virtual machine %VMName;. The virtualization

software on host %VMHostName; does not

allow a checkpoint name that exceeds

%MaxLength; characters.

Specify a shorter checkpoint name and



virtual machine %VMName; on host

%VMHostName; because virtual machine

%VMName; has one or more virtual hard disks

attached to a shared SCSI adapter.

Ensure that virtual machine does not

have any virtual hard disks attached to

shared SCSI adapters and then try the

operation again.

2401 The specified path is not a valid share path on

%ComputerName;.

Specify a valid share path on

%ComputerName; to the virtual

machine to be saved, and then try the

operation again.

2406 VMM is unable to add host %ComputerName;. 1) Verify that the server name and the

domain name are correct.\n2) Verify

that the host is running Windows Server

2003 SP2 or a later version. If the

operating system was updated recently,

Active Directory Domain Services

updates may still be pending. In that

case, wait until Active Directory Domain

Services updates run, and then add the

host again. The update interval is

Troubleshooting VMM


determined by the Active Directory

replication policy for the domain.

2411 Virtual Machine Manager is unable to find

host %ComputerName;. The specified

computer name contains characters that are

not valid.

Verify that computer name does not

contain * / \ ( or ), and then try the

operation again.

2412 Virtual hard disks assigned to the IDE channel

cannot be bigger than 127 GB.

If a larger drive is required, use the SCSI

bus, and then try the operation again.

2600 Unable to connect to the database because of

a fatal database error. It is unlikely that the

database itself has been damaged.

Review the event log and take

appropriate action. Ensure that SQL

Server is running.

2601 Unable to connect to the VMM database. Ensure that the SQL Server is running

and configured correctly.

2602 Database integrity is in question because of a

hardware or software problem.

Contact an experienced SQL

administrator whenever this error

occurs. Look at Windows Event Log for

troubleshooting. Run DBCC CHECKDB to

determine the extent of the damage. It

is possible that the problem is in the

cache only and not on the disk itself. If

so, restarting SQL Server corrects the

problem. Otherwise, use DBCC to repair

the problem. In some cases, it may be

necessary to restore the VMM

database.

2603 Unable to connect to the VMM database

because the database is in an inconsistent

state.

Contact an experienced SQL

administrator whenever this error

occurs. In some cases, it may be

necessary to restore the VMM

database. If the problem persists,

contact Microsoft Help and Support.

2604 Database operation failed. Ensure that the SQL Server is running

and configured correctly, and try the

operation again.

2605 Unable to connect to the VMM database

because of a general database failure.

Ensure that the SQL Server is running

and configured correctly, then try the

operation again.

2606 Unable to perform the job because one or

more of the selected objects are locked by

another job.

Either cancel those running jobs, or wait

for them to complete, before trying this

action again.

2818 The virtual machine name contains a character

that is not allowed (*?:<>/|\").

Specify a valid virtual machine name.

Troubleshooting VMM


2838 An unknown error occurred attempting to

access a virtual hard disk image %FileName;

on the %ServerName; server.

Ensure the file %FileName; is actually a

virtual hard disk image.

2839 The virtual hard disk image %FileName; is not

valid on the %ServerName; server.

Ensure that the file has the ".vhd"

virtual hard disk image extension and

that the file is actually a virtual hard

disk image. If you are attaching it to an

IDE bus, the maximum disk size is

127GB.

2845 A virtual network with the given ID could not

be found on the %ServerName; server. This

virtual network might be required as part of

another object.

Ensure that the virtual network has not

been removed or deleted, and then try


2871 The value provided for the MAC address is not

valid or is an incorrectly formatted address for

the VM %VMName; on the %ServerName;

server.

Enter a valid unicast MAC address in the

format xx-xx-xx-xx-xx-xx.

2890 VMM cannot complete the Virtual Server

operation on the %ServerName; server.

Check the Windows Event Log on the

%ServerName; server to determine the

cause of the error and make

corrections. Then try the operation

again.

2891 VMM cannot complete the Virtual Server

operation on the %ServerName; server

because of the error:

%VMAsyncTaskErrorMessage;

Resolve the issue in Virtual Server and


2900 An internal error has occurred. Restart the agent on the machine

%ServerName;, and then try the

operation again.

2901 The operation did not complete successfully

because of a parameter or call sequence that

is not valid.

Ensure that the parameters are valid,


2902 There is not enough space on the disk to

create %FileName; on the %ServerName;

server.

Create additional disk space on the

volume containing %FileName;, and


2903 VMM could not locate the specified file

%FileName; on the %ServerName; server. This

file might be required as part of another

object.


path parameter, and that all necessary

files are present. Try the operation

again.

2904 VMM could not find the specified path

%FileName; on the %ServerName; server.


file name parameter, and then try the

operation again.

Troubleshooting VMM


2905 The file name, folder name, or volume label

syntax %FileName; is incorrect on the

%ServerName; server.

Ensure that the path name does not

contain the characters (\ / : * ? " < > | ),


2906 The specified path %FileName; is not valid on

the %ServerName; server.



2907 The file name of file %FileName; exceeds the

maximum path length of 260 characters on

%ServerName;.

Specify a valid path, and then try the

operation again.

2908 The file %FileName; cannot be accessed

because it is in use by another process on the


Wait until the other process is

completed, and then try the operation

again.

2909 VMM cannot create the file %FileName;

because the file name already exists on the


Specify a unique file name, and then try


2910 VMM does not have appropriate permissions

to access the resource %FileName; on the


Ensure that Virtual Machine Manager

has the appropriate rights to perform

this action.

2911 Insufficient resources are available to

complete this operation on the %ServerName;

server.

Ensure that the virtual machine host

has sufficient memory and disk space to

perform this action. Try the operation

again.

2912 An internal error has occurred trying to

contact an agent on the %ServerName; server.

Ensure the agent is installed and

running. Ensure the WS-Management

service is installed and running, then

restart the agent.

2913 A generic Virtual Server exception has

occurred on the %ServerName; server.


2914 The connection to the %ServerName; server

cannot be established.

Ensure the server is up and running

along with the virtualization service.

2915 The WS-Management service cannot process

the request. Object not found on the


Ensure that the agent is installed and

running. If the error persists, reboot

%ServerName; and then try the

operation again.

2916 VMM is unable to complete the request. The

connection to the agent %ServerName; was

lost.

Ensure that the WS-Management

service and the agent are installed and

running and that a firewall is not

blocking HTTP traffic. If the error

persists, reboot %ServerName; and


2917 Virtual Machine Manager cannot process the

request because an error occurred while

Log in by using an account on the same

domain as the VMM server, or by using

Troubleshooting VMM


authenticating %ServerName;. Possible causes

are:\n1) The specified user name or password

are not valid.\n2) The Service Principal Name

(SPN) for the remote computer name and port

does not exist.\n3) The client and remote

computers are in different domains and there

is not a two-way full trust between the two

domains.

an account on a domain that has a two-

way full trust with the domain of the

VMM server, and then try the operation

again. If this does not work, purge the

Kerberos tickets on the VMM server by

using kerbtray.exe, available at


LinkId="93709". Then, reset the SPN for

%ServerName; by using setspn.exe

available from


LinkId="93710". If this still does not fix

the problem, make %ServerName; a

member of a workgroup instead of a

domain, restart the computer, rejoin

the domain, and then try the operation

again.

2918 The folder name %FileName; is not valid on


Ensure that %FileName; is a valid folder

name, and then try the operation again.

2919 The destination file %FileName; already exists

or the destination device is not ready on the



path, delete the file if it exists, and then


2920 An I/O error occurred while opening the file



path, delete the file if it exists, and then


2921 VMM cannot complete the operation on the

file %FileName; on the %ServerName; server.

One of the following system errors occurred: a

file is read-only, the specified path is a

directory, or Virtual Machine Manager does

not have the required permissions.

Ensure that the path is valid and VMM

has the appropriate rights to perform

this action.

2922 VMM is unable to create a temporary file on

the %ServerName; server. A unique temporary

file name is not available.

Ensure that the system has enough

resources and the appropriate rights to

proceed, and then try the operation

again.

2923 A malformed response was received trying to

contact the agent on %ServerName; server.


running. If the agent is running, restart

the agent and verify that WS-

Management is installed correctly.

2924 Unable to complete the request. Operation on

the %ServerName; server timed out.


2925 The device used to access the specified path

%FileName; is not ready on the %ServerName;

server.

Insert the appropriate media into the

available device or specify a different


Troubleshooting VMM


2926 Logon failure. Unknown user name or bad

password on the %ServerName; server.

Set a valid username and password and


2927 A Hardware Management error has occurred

trying to contact server %ServerName;.

Check that WinRM is installed and

running on server %ServerName;. For

more information use the command

"winrm helpmsg hresult".

2928 The specified logon credentials are not valid


Set a valid domain username and

password and try the operation again.

2929 VMM could not resolve the specified file



file name, then try the operation again.

2930 The network path %FileName; was not found


Ensure that the share name provided is

valid and then try the operation again.

2940 VMM is unable to complete the requested file

transfer. The connection to the HTTP server

%BITSServerName; could not be established.

Ensure that the HTTP service and/or the

agent on the machine

%BITSServerName; are installed and


blocking HTTPS traffic.


connection to the agent on machine

%ServerName; has been lost.

Ensure that the WS-Management

service and the agent are installed and


blocking HTTP traffic.

2942 VMM is unable to complete the requested file

transfer. The HTTP server %BITSServerName;

returned access denied.

Ensure that the HTTP service and/or the

agent on the machine

%BITSServerName; are installed and

running.

2943 VMM is unable to complete the requested

operation because there are no logon servers

available.

Ensure that the domain controller is up

and running and that you have access to

it.

2944 VMM is unable to complete the requested

operation because the server name

%ServerName; could not be resolved.



administrator.

2945 Unable to connect to the Virtual Server service

on the server %ServerName;.

Ensure that the Virtual Server service

and the Virtual Machine Manager Agent

are installed and running on the server

%ServerName;.

2946 A malformed response was received trying to

contact server %ServerName;

(%DetailedErrorMessage;).

Ensure that the communication is set

up properly.

2947 Virtual Machine Manager cannot complete

the VirtualCenter action on the server

%ServerName; because of the following error:

Resolve the issue and then try the

operation again.

Troubleshooting VMM


%DetailedErrorMessage;.


the VirtualCenter action on server


%DetailedErrorMessage; (%Value;).

This error occurs when the key, name,

or identifier for the element that you

are trying to add already exists for an

element in the collection. Provide

unique values for those parameters and






This error occurs when a function

contains an invalid argument. Resolve

the issue and then try the operation

again.





This error occurs when a referenced

component of a managed object -

either a data object type (such as a role

or permission) or a primitive (such as a

string) - cannot be found. Resolve the

issue and then try the operation again.





This error occurs when an operation is

denied access because of insufficient

privileges on a managed object. Resolve

the issue and then try the operation

again.

2952 %FileName; cannot be created on server

%ServerName; because the target volume is

not set to "Available for placement."

Specify a different target volume or set

the target volume to "Available for

placement" and then try the operation

again.

2953 VMware ESX Server host %ServerName; is not

in the same VirtualCenter as host

%VMHostName;.

Specify a different server and then try



started because the run under credentials are

not valid on the %ServerName; server.

Set the run under credentials for

%VMName; to valid credentials and try


2972 The credentials supplied for the virtual

machine to run under are not valid.

Enter a valid account and password, and


3100 VMM cannot open the specified VHD file


Ensure that the file is present and

accessible. Unmount the VHD file by

using vhdmount.exe if the file is

mounted. Try the operation again.

3101 VMM failed to mount VHD file %FileName; on

the %ServerName; server. A timeout occurred.

Check Device Manager/System Devices

to make sure that Microsoft Virtual

Server Storage Bus is installed and

functional. If it is not, install VHDMount

component of Virtual Server. Restart

Troubleshooting VMM


Virtual Disk Service, and then try the

operation again.

3102 VMM failed to mount VHD file %FileName; on

the %ServerName; server. IOCTL Failed.






the Virtual Disk Service, and then try


3103 VMM failed to find the SCSI address for

mounted VHD file %FileName; on the







the Virtual Disk Service, and then try


3105 VMM failed to load the vhdmount .dll file on






component of Virtual Server.

3106 The VHD file %FileName; mount was canceled



3107 The format of the file %FileName; on the

%ServerName; server is not compatible with

the VHD format.

Ensure that the file is not corrupted,

and try the operation again.

3108 The format of the file %FileName; on server

%ServerName; is not recognized.

Ensure that the input .vmdk file is the

.vmdk file that the .vmx file points to.

\n\nThe .vmx file points to a .vmdk file

that contains metadata. That .vmdk file

in turn points to a binary .vmdk file.

With the Copy-VMDK cmdlet, use the

.vmdk file that contains the metadata.

\n\nAdditionally make sure that both

.vmdk files are not corrupted, and then

try the operation again. If the problem

persists, contact Microsoft Help and

Support at


LinkId="45276".

3109 VMM is unable to create a snapshot set on

%ComputerName;. The writer

%VssWriterName; is in the failed state

%VssWriterStatus;.


happens again, disable the failing writer

and/or the writer corresponding to this

writer application for online physical-to-

virtual handling.

Troubleshooting VMM



%ComputerName;. An unexpected error

occurred during the Volume Shadow Copy

service operation.


3111 An unexpected error occurred on an attempt

to contact Volume Shadow Copy service on

%ComputerName;.

Verify that Volume Shadow Copy

service is enabled, and try the operation

again.


%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


3113 VMM cannot create either the shadow copy

storage file or other shadow copy data

because there is not enough storage available

on %ComputerName;.

Create sufficient space on disk to create

the initial snapshot set and to record

changes during the physical-to-virtual

time. Try the operation again.

3114 VMM is unable to perform a snapshot set -

related operation on %ComputerName;. This

is a general failure in Volume Shadow Copy

service.

1) Ensure that Volume Shadow Copy

service is enabled on this computer. 2)

Check recent records from the VolSnap

source in the Application Event Log to

determine the issue. 3) Try the

operation again.

3115 The snapshot creation set on

%ComputerName; was canceled.



%ComputerName;. A timeout occurred.


3117 If a value for the -DiskSizeAdd parameter is

specified, a value for the -VolumeDeviceID

parameter must also be specified.

Specify a value for the missing

parameter -VolumeDeviceID or remove

-DiskSizeAdd parameter, and then try


3118 An intermediate job in a JobGroup must

specify the value for the -VolumeDeviceID

parameter.


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.


parameters or remove binding

parameters, and then try the operation

again.

3120 The volume %VolumeDriveLetter; is not

present on the %ServerName; computer.

Add a value to the -VolumeDeviceID

parameter to specify a drive letter or

name (in \\?\Volume{GUID}\ format) of

a volume that exists on the source

machine %ServerName;. If the

configuration of the source machine

Troubleshooting VMM


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


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


3124 The -IDE and -SCSI parameters are mutually

exclusive.

Resolve the conflict, and then try the

operation again.

3125 Parameters -Path and -Name are required for

a standalone or a final job in a job group.

Specify the -Path and -Name

parameters and try the operation again.

3126 Parameters -Name, -Description, -StartVM, -

MemoryMB, -ProcessorCount, -

ProcessorType, -RelativeWeight, -DriverPath, -

RunAsSystem, -RunAsUserCredential, -

StartAction, -StopAction, -DelayStart, -

UseHardwareAssistedVirtualization can only

be specified in a standalone or final JobGroup

job.

Remove these parameters from the

intermediate jobs and specify them on

the final job.

3127 The job failed to configure %ComputerName;

to restart in Windows PE.


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


3129 A timeout occurred while waiting on the agent

service on %ComputerName; to respond.

Ensure that the Virtual Machine

Manager agent service is started on


operation again.

3130 The specified driver path %FolderPath; is

either not found or is not accessible.

Ensure that the path exists and Virtual

Machine Manager server

%ServerName; has read permissions to

all the files under the specified path.

3131 The job failed to restart %ComputerName;

(temporary computer name is %ServerName;)

back into the original operating system.

Automatic restart is scheduled to occur within

If %ComputerName; does not restart in

15 minutes, manually restart it back

into the original operating system using

the boot menu.

Troubleshooting VMM


15 minutes.

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


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.




the boot menu.

3134 An internal agent error has occurred on

%ComputerName;.


3135 An error occurred while communicating with

the agent on %ComputerName;.

Ensure %ComputerName; is online and

not blocked by a firewall, and then try


3136 An error occurred executing %FileName; on

%ServerName;.

Try the operation again. If problem

persists, reinstall the Windows

Automated Installation Kit on

%ServerName;.

3137 The driver installation file %FileName; cannot

successfully install into the Windows PE image

required for the physical-to-virtual conversion.

Remove %FileName;, and then try the

operation again.

3138 The files needed to install the agent are

missing from the Virtual Machine Manager

server %ServerName;.

Run Setup again to install the missing

files.

3139 Virtual Machine Manager could not connect to

the physical-to-virtual source computer

%ComputerName; after it restarted to its

original operating system.




the boot menu.

3142 Failed to fully clean up %ComputerName;. Ensure that the correct boot loader is

installed and remove all files named

"$scvmm*.*" from the root directory of

the boot volume on %ComputerName;,


3144 Unable to proceed because a

SourceNetworkConnectionID is not specified.

This parameter must have a value if a value is


parameter -

SourceNetworkConnectionID or remove

Troubleshooting VMM


specified for any of the

VirtualNetworkAdapter parameters.

any of the VirtualNetworkAdapter

parameters and then try the operation

again.

3145 The operating network adapter

'%MACAddress;' is not found on the source

machine %ServerName; or TCP/IP is not

bound and enabled on this network adapter.

Add a value to the -

SourceNetworkConnectionID parameter

to specify the network connection

name or the MAC address of a TCP/IP

bound network adapter on source

machine %ServerName;. If the


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.


parameter -Credential.

3148 The volume %VolumeDriveLetter; selected for

physical-to-virtual imaging is not accessible

from Windows PE. This is usually caused by

missing or incorrect storage drivers.

%ComputerName; may now need to be

manually restarted into the original operating

system using the boot menu.

Exclude this volume from conversion.

Or, if you are performing offline

physical-to-virtual conversions, create a

new folder under %StaticDriverPath; on

the VMM computer and then copy all of

the storage or networks drivers to the

new folder.

3149 The -Fixed and -Dynamic parameters are

mutually exclusive.


operation again.

3150 If a value for -Fixed or -Dynamic parameter is

specified, a value for the -VolumeDeviceID

parameter must also be specified.


parameter -VolumeDeviceID or remove

-Fixed or -Dynamic parameter, and then


3151 VMM failed to extend volume on the VHD file

%FileName;. A timeout occurred.

Restart Virtual Disk Service, and then


3152 The network adapter '%MACAddress;' is

already present in the selection of network

adapters for conversion.

Ensure there are no duplicate values


3154 An internal error has occurred trying to

contact an agent on the %ServerName; server.


running. Ensure the WMI service is

installed and running, then restart the

agent.

3155 Cannot connect to the local WMI service. Ensure the WMI service is installed and

running on the Virtual Machine

Manager server.

Troubleshooting VMM


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.


connection to the agent %ServerName; was

lost.

Ensure that the computer

%ServerName; exists on the network,

WMI service and the agent are installed

and running and that a firewall is not

blocking HTTP and WMI traffic.

3158 VMM is unable to emulate the exact


%ServerName;. The virtual machine memory

could not be set to %MemorySize; MB

because the current limit on virtual machine

memory has been reached on the

%VMHostName; host. The memory on the

resulting virtual machine will be adjusted to

the closest value within the valid range for this

host.

Ensure the virtual machine host

%VMHostName; has required available

memory, and then change the memory

on the resulting virtual machine to the

desired value. Or, move the virtual

machine to a host that has enough

memory to start this virtual machine.

3159 The volume %VolumeDriveLetter; of source

computer %ServerName; cannot be extended

to the size of the resulting VHD due to a

system error. The VHD is extended and will

have unallocated space.

Consider expanding the volume after

starting up the resulting Virtual

Machine.

3160 The name of the source virtual machine is

either outside of the valid range for a Virtual

Machine name supported by Virtual Server or

contains one of the following characters: (one

of *?:<>/|\").

Override the source virtual machine

name with a valid Virtual Server-based

virtual machine name.

3200 The patch file %FileName; cannot be found. Ensure that the patch file exists and is

accessible by the machine account on

the Virtual Machine Manager server.


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


3202 The patch file %FileName; format is not valid. Specify a valid self-extractable

executable file or a .cab file, and then


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


3204 Failed to populate the cache at %FolderPath; Ensure that the system has enough

Troubleshooting VMM


because of an I\O error. 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


3206 Disk hardware or File System on volume

%VolumeDriveLetter; is not supported by

Volume Shadow Copy Service.

%ServerName; cannot be virtualized

using an online conversion. Specify the -

Offline parameter to perform an offline

conversion.

3207 Cannot create a virtual machine for the x64

Windows operating system.

The selected machine %ServerName;

cannot be virtualized. Virtual Server

supports only 32-bit operating systems.

3208 Volume %VolumeDriveLetter; cannot be

attached to IDE controller because the volume

exceeds the maximum IDE disk size

(%MaxLimit; GB) supported by virtualization

software on host %VMHostName;.


cannot be virtualized. Either assign this

volume to a SCSI channel or exclude the

volume from imaging, and then try the

operation again.

3209 Volume %VolumeDriveLetter; cannot be

attached to SCSI controller because the

volume exceeds the maximum SCSI disk size

(%MaxLimit; GB) supported by virtualization

software on host %VMHostName;.


cannot be virtualized. Exclude this

volume from imaging, and then try the

operation again.

3210 Boot and\or System volume

%VolumeDriveLetter; was not selected or is

not found on source machine %ServerName;.

Selected machine %ServerName;

cannot be virtualized. Verify that the

boot and system volumes are selected

for migration. Then try the operation

again.

3211 An older version of Virtual Server on host

%VMHostName; has been detected and is not

supported.


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.


cannot be virtualized. Contact Microsoft

Help and Support for further assistance.

3213 VMM does not support the specific type of the

system file %FileName; found on the source

machine %ServerName;.


cannot be virtualized. Contact Microsoft

Help and Support for further assistance.

3214 Virtual Machine Manager cannot extract patch

file %FileName; to folder %FolderPath;.

Verify that the physical disk contains

enough space to accommodate the

Troubleshooting VMM


patch file, and then try the operation

again.

3215 The source computer %ServerName; does not

have enough memory to perform the offline

physical-to-virtual conversion.

%MemoryMinRequired;MB is required for this

conversion.

Add additional physical memory to

%ServerName; and try the operation

again.

3216 Unable to convert %ServerName; because files

that are required for the conversion are

missing from the patch cache.

Download the update %FriendlyName;

for %OSName; (%Language;,

%OSPlatform;) from Windows Update

to "%FolderPath;" on the Virtual

Machine Manager server and then run

the Add-Patch cmdlet.

3217 Unable to convert %ServerName; because

required files to convert the source computer

are missing.

Copy %FileName; to "%FolderPath;" on


The files are archived in %FileName;,

which is located at

%%WINDIR%%\Driver

Cache\%OSPlatform; on %ServerName;

or on the %OSName; (%Language;,

%OSPlatform;) installation media. Run


3218 NTFS boot volume %VolumeDriveLetter; is less

than 4 GB in size. This configuration is not

supported by Virtual Server.


cannot be virtualized.

3219 Perimeter network host %VMHostName;

cannot be used in physical-to-virtual or virtual-

to-virtual conversions.

Specify a host located in a trusted

domain, then try the operation again.

3220 %ServerName; cannot be converted. Boot

volume %VolumeDriveLetter; must be

attached as the first hard drive for the virtual

machine to start up.

Modify the bus assignments to create

space for the boot volume.

3221 The selected machine %ServerName; will be

virtualized without CD\DVD drives. The

channels are not available on the IDE bus for

the addition of a DVD device to emulate the

source machine configuration.

Modify the bus assignments or volume

selection to create space on the IDE bus

for the CD or DVD drive.

3222 The selected machine %ServerName; cannot

be virtualized. The channels are not available

on the IDE or SCSI buses for the addition of

volume %VolumeDriveLetter;. Note that non-

boot volumes always follow the boot volume

during bus assignment.

Reduce the number of channels

selected for migration volumes or

change the bus assignment of the boot

volume to fit volume

%VolumeDriveLetter;.

3223 Boot volume %VolumeDriveLetter; must be The selected machine %ServerName;

Troubleshooting VMM


attached to the IDE bus or SCSI bus 0 for the

machine to boot up.

cannot be virtualized. Modify the bus

assignments for the boot volume which

must be located on the first hard disk of

the virtual machine, and then try the

operation again.

3224 VMM is unable to locate the source computer

%ComputerName; in Active Directory Domain

Services.

Verify that the server name and the



3225 The Windows Automated Installation Kit is not

installed.

Install Windows Automated Installation

Kit version 1.0.0.0 on %ComputerName;


3226 Unable to run job group because an -Offline, -

DriverPath, or -Shutdown parameter is

specified on a job other than the final job.

These parameters can only be specified in a

standalone job or in the final job in a job

group.

Remove these parameters from the

intermediate jobs and specify them on

the final job.

3227 Physical-to-virtual conversion failed because a

-DriverPath or -Shutdown parameter was

specified without specifying an -Offline

parameter.


parameter -Offline or remove -

DriverPath, -Shutdown parameters to

enable online physical-to-virtual

conversion, and then try the operation

again.

3229 Selected machine %ServerName; cannot be

virtualized.

For more information, view details for

this job.


required files are missing.




(Support Link: %URL;) to "%FolderPath;"

on the Virtual Machine Manager server

and then run the Add-Patch cmdlet.

3232 A Virtual Disk Service (VDS) error occurred on


Ensure that this service can be started

on %ServerName; and check the

Windows Event Log for troubleshooting

information. Try the operation again.

3233 Failed to extract patch file %FileName;. Verify that the patch file is extractable,


3234 Failed to copy file %SourceLocation; from

source server %ComputerName; to folder

%DestinationLocation; on the VMM server.

After resolving the problem, retry the

operation or copy the files required for

virtualization manually. Then use the

add-patch cmdlet to populate the patch

cache.

3235 Failed to extract patch file %FileName;. This Ensure that the patch file applies to 32-

Troubleshooting VMM


patch applies to the operating system type or

platform that is unsupported for virtualization.

bit platform of an operating system that

is supported for virtualization, and then



required files for the conversion are missing

from the patch cache.




to "%FolderPath;" on the Virtual

Machine Manager server and then run






The files are archived in %FileName;,

which is located on the %OSName;

(%Language;, %OSPlatform;) installation

media. And then run the Add-Patch

cmdlet.






(Support Link: %URL;) to "%FolderPath;"

on the Virtual Machine Manager server

and then run the Add-Patch cmdlet.

3239 File %FileName; that is required to convert

source computer %ServerName; is missing.

The file might be located at

%%WINDIR%%\Driver Cache\i386 on

%ServerName;, or at i386\Uniproc directory

on the %OSName; (%Language;) installation

media.



Run the Add-Patch cmdlet.

3240 VMM discovered that a restart is pending

after application of Microsoft updates on the

source computer %ServerName;.

Restart source computer %ServerName;

to enable conversion of this machine.


3241 The job cannot be restarted. If a more recent conversion job of the

source machine %ServerName; exists,

restart that job instead. Otherwise,

restart the conversion from the

beginning.

3242 The converted virtual machine may not

function correctly because it will not match

the configuration of the source VMware

virtual machine %FileName;.

Remove or supply a solution.

3243 Virtual Machine Manager is unable to update

the operating system of the source VMware

virtual machine %VMName;. The operating

The converted virtual machine may not

start or operate correctly. For the list of

supported Windows operating systems

Troubleshooting VMM


system, file system, or disk layout is not

recognized.

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.

3407 The entered URL is not valid. Enter a valid URL

3415 The -HostDrive and -AnyHostDrive parameters

are mutually exclusive. You can specify a value

for either the -AnyHostDrive parameter or the

-HostDrive parameter, but you cannot specify

a value for both parameters in the same

operation.

Review the command and then try the

operation again.

3453 Unable to verify the connection to the

reporting server %ServerName;.

Ensure that System Center Virtual

Machine Manager 2008 Management

Pack and its reports are installed on the

Operations Manager server. To

download the management pack, go to


LinkID="85858".

3509 ID %ProcessorTypeGuid; is not found in the list

of supported processors.

Ensure that the processor ID is valid and


3513 Unable to set the value for %Parameter;. The

sum of all elements exceeds the maximum

length of %MaxLength;.

Choose a different value below the

maximum length, and then try the

operation again.

3514 Unable to connect to the Virtual Server service

on the library server %ServerName;.

Ensure that the Virtual Server service is

installed and running on the library

server.

3516 The specified virtual network adapter

configuration is not supported by the host


Update the virtual network adapter

configuration and then try the

operation again.

3518 The VLAN setting for one or more network Ensure that virtual LAN identification is

Troubleshooting VMM


adapters on virtual machine %VMName; is not

compatible with the virtualization software on

host %VMHostName;.

disabled for all network adapters listed

in the hardware configuration of virtual

machine %VMName; or specify a

different host, and then try the

operation again.

10200 Setup has detected an unsupported version of

Windows Automated Installation Kit (WAIK)

on this computer.

Uninstall WAIK from this computer and

then run Setup again. Setup will

automatically install the correct version.

10206 Setup requires Microsoft System Center

Operations Manager SP1 to be installed.

Install Operations Manager 2007 SP1

and then run Setup again

10207 Setup was not able to retrieve the service

account from the specified Virtual Machine

Manager server.

Specify a different VMM server and


10208 Setup encountered an error while importing

management packs.

Uninstall all management packs related

to System Center Virtual Machine

Manager and then run Setup again.

Setup will import the required

management packs.

10209 Setup could not install Virtual Machine

Manager server because the computer name

has more than 15 characters.

Change the computer name to be less

than or equal to 15 characters and then

run Setup again.

10210 The parameter /prep is valid only for installing


For help with setup and information

about parameter usage, run the

command setup.exe /?.

10211 Another user or process is currently using the

Server Manager console.

Close the Server Manager console and

then run Setup again.

10212 File %CopyFileFromCD; was not found on the

Virtual Machine Manager CD.

Uninstall the VMM server, verify that

file %CopyFileFromCD; is on the CD, and

then run Setup again. If the problem

persists, contact Microsoft Help and

Support.

10213 Setup could not install Windows Automated

Installation Kit (WAIK) related assemblies in

the Global Assembly Cache.

Cancel Virtual Machine Manager Setup

and then run Setup again.

10214 To use an SQL Server 2008 instance and

database, the SQL Server 2008 Management

Tools - Basic or Command Line Utilities must

be installed on the Virtual Machine Manager

server.

To install the management tools, run

SQL Server 2008 Setup, and, on the

Feature Selection page, select

Management Tools - Basic, and then

complete the wizard. Or, to download

and install the command line utilities,


LinkId="110393".

Troubleshooting VMM


10215 The specified SQL Server database,

%DatabaseName;, is a Virtual Machine

Manager 2007 database, which is not valid for

this configuration.

Either specify the database name that is

provided with the OEM Setup, or create

a new database by typing a new

database name, and then selecting the

"Create a new database" check box.

10216 Setup could not retrieve the Virtual Machine

Manager server information from Active

Directory.

Ensure that the VMM server has a

service connection point registered in

the Active Directory, and then try the

operation again. If you are using disjoint

namespace, specify fully qualified

Active Directory domain name of the

VMM server.

10217 Setup could not retrieve the Virtual Machine

Manager server name from the .ini file.

Ensure that the VMM server name is

correctly specified in the .ini file, and


10218 Setup could not import the System Center

Virtual Machine Manager 2008 Management

Pack into Operations Manager 2007 because

one or more required management packs are

missing. The VMM 2008 Management Pack

cannot be deployed unless the following

component management packs are present in

Operations Manager 2007:\nWindows Server

Internet Information Services 2003\nWindows

Server Internet Information Services

2008\nWindows Server Internet Information

Services Library\nSQL Server Core Library

To provide the missing component

management packs, ensure that the

following management packs have been

imported into Operations Manager

2007:\n Microsoft Windows Server

2000/2003 Internet Information

Services Management Pack for OpsMgr

2007 (version 6.0.6278.0 or later) \n

Microsoft SQL Server 2000/2005

Management Pack \n You can

download the management packs from

the System Center Operations Manager

2007 Catalog at


LinkId="86411"

10400 Before Virtual Machine Manager can add a

host, the host must be restarted.

Restart %ComputerName; and then try

adding the host again.

10401

10402 Host configuration failed on

%ComputerName; because the specified

memory reserve exceeds the total memory.

Specify a memory reserve that is less

than the total amount of memory.

10403 %ComputerName; is not listed in Active


Verify that the computer name and the



10404 %ComputerName; already serves the specified

Virtual Machine Manager role.

Enter different computer name and


10405 %ComputerName; does not have the specified

virtualization software installed or enabled.

Install the correct virtualization

software on %ComputerName;, or enter

a different computer name and then try

Troubleshooting VMM



10406 Virtual Machine Manager cannot contact

%ComputerName; because the credentials for

%ComputerName; are missing.

Run Associate-VMhost on

%ComputerName; providing root

credentials and then try the operation

again

10407 Virtual Machine Manager could not query

Active Directory Domain Services.

Verify that the domain name and the

credentials, if provided, are correct and


10408 This cmdlet can be run only on a Virtual Server

host.

Specify a Virtual Server host and then


10409 Virtual Machine Manager cannot contact

%ComputerName;.

1. Verify that the correct security file is

specified.\n2. Verify that DCOM access,

launch, and activation permissions are

enabled for the Administrators group

on %ComputerName;\n3. Use

dcomcnfg.exe to modify permissions as

needed and then try the operation

again.

10410 Virtual Machine Manager cannot add an ESX

host to host group "All Hosts."

Specify a host group that is not a root

host group and then try the operation

again.

10411 The host group does not exist on VirtualCenter

server %ComputerName;.

Specify a valid host group and then try


10413 Virtual Machine Manager is unable to add the

cluster %ComputerName; as a clustered host

because the operating system is not

supported. Clustered hosts must be running

Windows Server 2008 or later.

Ensure that the cluster is running

Windows Server 2008. If the operating

system was updated recently, Active

Directory Domain Services updates

might still be pending. Wait until Active

Directory Domain Services updates run,

and then try adding the cluster again.

10414 Virtual Machine Manager cannot add

%ComputerName; as a Hyper-V host because

the Hyper-V version detected on

%ComputerName; is not the released version.

1) If the host is intended to be used as a

Hyper-V host, download and install the

released version of Hyper-V from


LinkID="113199". If you are not sure

whether the host has hardware-assisted

virtualization support or whether it is

enabled in the BIOS, download the

Virtualization Detect (DetectVp.EXE)

tool and run it on the host to confirm it

meets the requirements. To download

the tool as part of the Windows Logo Kit

(WLK), go to


Troubleshooting VMM


LinkId="121104".\n2) If the host is

intended to be used as a Virtual Server

host, download and install Virtual

Server 2005 R2 SP1 and the latest

update on the host. To download

Virtual Server 2005 R2 SP1, go to


LinkID="120488". To download the

latest update, go to


LinkId="121055".

10415 Virtual Machine Manager is not able to use

Hyper-V on host %ComputerName;. You must

accept the Microsoft Software License Terms

for Hyper-V on %ComputerName; before

Virtual Machine Manager can manage the

host.

Install the Hyper-V Client Management

Pack on the host or on another

computer running Windows Server

2008. In Administrative Tools, open

Hyper-V Manager, connect to

%ComputerName;, accept the license

terms, and then refresh

%ComputerName; in the Host view of

the VMM Administrator Console.

10416 The specified key length for the Virtual

Machine Remote Console (VMRC) certificate

request is not valid.

Valid key lengths are 512, 1024, 2048,

4096, and 8192.

10417 Virtualization manager %ComputerName; is

not associated with this Virtual Machine

Manager server.

Check the virtualization manager name


10418 Virtual Machine Manager cannot add host

%ComputerName; because the version of

Virtual Server installed on the host is not

supported.

Install Virtual Server 2005 R2 SP1 on the

host %ComputerName; from


LinkId="120488" and then apply update

948515 from


LinkId="120407".

10419 The -SshPublicKey and -SshPublicKeyFile

parameters are mutually exclusive.


operation again.

10420 VMM cannot establish a trust relationship for

the SSH secure channel for %ServerName;

server.

Check the remote server name, port

and SSH public key, and then try the

operation again.

10421 The specified user account cannot be the

same as the VMM service account.

Specify a different account and then try


10427 AvailableForPlacement property for a VMware

ESX Server host cannot be changed directly

within Virtual Machine Manager.

This property can be changed only by

using the VMware VirtualCenter Server

to change the host's maintenance mode

setting. Putting an ESX Server host into

Troubleshooting VMM


maintenance mode sets the

AvailableForPlacement property in

VMM to false, and taking an ESX Server

host out of maintenance mode sets the

AvailableForPlacement property in

VMM to true.

10600 The operating system specified for the

template or guest operating system profile is

not compatible with the answer file.

Specify unattend.xml format answer file

for a Windows 2008 or Vista template,

or a GuestOSProfile. Otherwise specify

sysprep.inf format answer file.

10601 The specified unattended installation xml file

is not valid.

Specify a valid unattend .xml file.

10602 Virtual Server does not support 64-bit virtual

machines.

Place the virtual machine on a Windows

Hyper-V or ESX host.

10603 Specified memory size %MemorySize; is not

supported by the host %VMHostName;


Select a host that supports the specified

memory limits or change the memory

specification. Valid memory size ranges

from %MemorySizeMinLimit; to

%MemorySizeMaxLimit;.

10604 Specified memory size %MemorySize; is not

supported.

Specify a valid memory size and then try

the operation again. Valid memory size

ranges from %MemorySizeMinLimit; to

%MemorySizeMaxLimit;.

10605 The specified VLAN configuration is not valid. Ensure that the virtual network adapter

is connected to a virtual network, that a

valid VLAN ID is specified, and then try


10606 The -VirtualHardDisk and -PassThroughDisk

parameters are mutually exclusive. You can

specify only one of these parameters.

Specify either -VirtualHardDisk or -

PassThroughDisk and then try the

operation again.

10607 The VHDDrive operation requires either -

VirtualHardDisk or -PassThroughDisk

parameters.

Specify either -VirtualHardDisk or -

PassThroughDisk and then try the

operation again.

10608 Cannot create a highly available virtual

machine because Virtual Machine Manager

could not locate or access %FolderPath;.

Ensure that the path exists and that the

path is for a cluster disk in available

storage, and then try the operation

again.

10609 Cannot create a highly available virtual

machine because host %HostNames; is not in

a host cluster.

Specify a host that is in a host cluster

and ensure that the cluster service is

running on that host, and then try the

operation again.

10610 Cannot change the Highly Available property You can change the HighlyAvailable

Troubleshooting VMM


for a virtual machine that is deployed on a

host.

property only when the virtual machine

is stored in the library.


creation of highly available virtual machines

for the virtualization software on host

%VMHostName;.

To create a highly available virtual

machine, select a clustered Hyper-V

host.

10612 Cluster resource with name Virtual Machine

%FriendlyName; already exists on cluster

%VMHostName;.

Specify a different name for the virtual

machine and then try the operation

again.

10613 Cluster resource group with name Virtual

Machine %FriendlyName; already exists on

cluster %VMHostName;



again.

10614 Cluster resource with name Virtual Machine

Configuration %FriendlyName; already exists

on cluster %VMHostName;



again.

10615 Unable to move virtual hard disk. You can only

move virtual hard disks that are connected to

a virtual machine on a Virtual Server or Hyper-

V host.

Ensure that the virtual hard disk is

connected to a virtual machine on a

Virtual Server or Hyper-V host and then


10616 Unable to move virtual hard disk. Only use the

Move-VirtualHardDisk with Bus, Lun and

BusType parameters for a New-VM or Move-

VM JobGroup.

Check the parameters and then try the

operation again.

10617 Specified location has a pass-through disk

attached.

Ensure that the virtual disk drive

attached at specified bus and LUN has a

virtual hard disk attached, and then try


10618 The virtual hard disk or its parent is attached

to more than one Virtual Machine and cannot

be moved.

Ensure that the specified virtual hard

disk is associated with one virtual


again.

10619 The user name provided is not a valid local

administrator user name for Windows Vista.

Provide a valid user name other than

the built-in Administrator account name


10620 The specified host disk is not attached to

virtual machine on a host.

Ensure that the specified host disk is

attached to a virtual machine and then


10621 The convert virtual disk drive operation timed

out after waiting for



10622 The specified virtual disk drive is not Ensure that the specified virtual disk

Troubleshooting VMM


connected to a host disk. drive has host disk attached and then


10623 The virtualization software for the virtual hard

disk %FileName; is not compatible with the

virtualization software on the host

%VMHostName;.

Remove the specified virtual hard disk

from the virtual machine or specify a

different host, and then try the

operation again.

10624 The virtualization software on the host

%VMHostName; does not support integration

services.

Specify a host with Hyper-V

virtualization software and then try the

operation again.

10625 The virtualization software on host

%VMHostName; does not support setting the

boot order in the BIOS.

Migrate the virtual machine to a host

that is running Windows Hyper-V and


10626 Boot device type %BootDevice; is not valid. Specify a valid parameter and try the

operation again.

10627 The specified boot order is not complete. Not

all valid boot devices are specified.

Include all valid boot devices in the boot

order and then try the operation again.

10628 Invalid memory size specified for virtual

machine. The virtualization software on host

%VMHostName; requires memory size to be a

multiple of 4 MB.

Specify a memory size that is a multiple

of 4 MB and then try the operation

again.


%VMHostName; does not support a processor

count of %Count;. Supported processor

counts: %ValidProcessorCount;.

Specify a host with different

virtualization software or change the

processor count, and then try the

operation again.

10630 The processor count of %Count; is not

supported. The supported processor counts

are %ValidProcessorCount;

Change the processor count and then


10631 The virtualization software for virtual machine

%VMName; does not support shared SCSI bus

configurations.

Specify a virtual machine with different


operation again.

10632 The virtualization software on the selected

host does not support virtual hard disks on an

IDE bus.

Specify a host that is running Windows

Hyper-V or Virtual Server or change the

bus type, and then try the operation

again.

10633 The virtualization software on the specified

host does not support user impersonation

using the "Run As" parameter.

Do not specify "run-as" credentials and


10635 Virtual machine customization is not

supported for the %OSName; operating

system.

Specify an operating system for which

customization is supported and then try


10636 The virtualization software on host Specify a host with different

Troubleshooting VMM


%VMHostName; does not support

customization of the %OSName; operating

system.


operation again.


%VMHostName; does not support the

%OSName; operating system.

Specify a host with different


operation again.


%VMHostName; does not support setting

NumLock.


Hyper-V and then try the operation

again.


%VMHostName; does not support changing

the BIOS configuration.


Hyper-V and then try the operation

again.

10640 Hyper-V does not support the specified COM

port setting.

Specify a named pipe for the COM port.

Hype-V does not support mapping a

virtual COM port to a physical COM port

or a text file.



creation of dynamic virtual hard disk.

Specify a Fixed Virtual Hard Disk disk

type and then try the operation again.

10644 Virtual Machine Manager cannot access the

WAIK (Windows Automated Installation Kit)

Image Manager DLLs.

Install WAIK and ensure that the Image

Manager DLLs are installed in the GAC

(Global Assembly Cache).


cloned because it has checkpoints. That

functionality is not supported for Hyper-V

virtual machines.

Delete all checkpoints for the virtual


again.

10646 The source and target location for virtual hard

disk %FileName; are the same.

Ensure that the source and target

locations are different and then try the

operation again.

10647 The virtual network adapter is connected to a

virtual network switch that is not valid.

Ensure that virtual network switch

exists or disconnect the virtual network

adapter, and then try the operation

again.

10648 Windows Hyper-V does not support attaching

a virtual floppy drive to a physical drive.

To configure a virtual floppy drive,

migrate the virtual machine to a host

with different virtualization software


10651 Cannot create the template because source

virtual machine %VMName; has checkpoints.

\n\nThis feature is not supported for virtual

machines that are deployed on hosts running

Windows Hyper-V.

Delete all checkpoints for the source

virtual machine and then try the

operation again.

Troubleshooting VMM


10652 Cannot create template because source virtual

machine %VMName; has pass-through disks.

Convert pass-through disks to virtual

hard disks and then try the operation

again.

10653 The virtualization software on the host does

not support the Limit Processor Functionality

setting.

Migrate the virtual machine to a

Windows Hyper-V host and then try the

operation again.

10654 Could not reset local Administrator password

on %VMName; to empty string before starting

Sysprep.

Change the local security policy on the

virtual machine to allow an empty string

as a password and then try the

operation again.

10655 Hardware changes while cloning a Hyper-V,

VMware or stored virtual machine are not

supported and were ignored.

Make any hardware changes to the

virtual machine after the cloning

operation is complete.

10656 Unable to delete cluster resource group

%FriendlyName; on host %VMHostName;.

Use Failover Cluster Management to

delete the cluster resource group.

10657 Unable to move the virtual hard disk because

a valid Bus, LUN, and Bus Type are not

specified.

Specify a valid Bus, LUN, and BusType,


10658 The %CmdletName; cmdlet requires an -

OperatingSystem or -GuestOSProfile

parameter.

Repeat the %CmdletName; cmdlet and

specify a guest operating system, either

directly (with the -OperatingSystem

parameter) or by specifying a guest

operating system profile (-

GuestOSProfile parameter).

10659 Cannot run Sysprep on virtual machine

%VMName; because the template does not

have a virtual hard disk attached that has been

generalized.

Specify a template that has been

generalized and then try the operation

again.

10660 Cannot install virtualization guest services on

virtual machine %VMName; because its virtual

hard disks are generalized.

Install the virtualization guest services

after the virtual machine has been

customized.

10661 The virtualization software on the selected

host does not support conversion of a pass-

through disk to a virtual hard disk.

Migrate the virtual machine to a host

that supports the conversion of pass-

through disks and then try the

operation again.


cloned because the virtual machine has

checkpoints. This functionality is not

supported for VMware virtual machines.

Delete all checkpoints for the virtual


again.

10663 The specified pass-through disk and virtual

machine are not on the same host.

Ensure that the pass-through disk and

virtual machine are on the same host,


Troubleshooting VMM


10665 Cannot attach a pass-through disk to a virtual

machine or template that is stored in the

library.

To add a pass-through disk (host disk)

to a virtual machine, deploy the virtual

machine to a host that supports pass-

through disks.

10666 Hardware changes while creating a template

from a virtual machine are not supported and

were ignored.

Make any hardware changes to the

template after you create the template.

10667 The virtual machine being created from a

template must contain at least one virtual

hard disk, which must be generalized.

Specify at least one virtual hard disk

that is generalized and then try the

operation again.

10668 Cannot clone the virtual machine because the

source virtual machine %VMName; has pass-

through disks.

Convert the pass-through disks to

virtual hard disks and then try the

operation again.



expanding of a differencing virtual hard disk.

To expand the hard disk, migrate the

virtual machine to a host that is running

different virtualization software.

10671 Hard disk file %FileName; is not compatible

with the SCSI adapter on %VMName;.

Either specify a compatible hard disk file

or convert hard disk file %FileName; by

using the VMware VirtualCenter server.

10672 You cannot remove virtual hard disk

%FileName; with the Remove-VirtualHardDisk

cmdlet because this virtual hard disk is

associated with a virtual machine on host.

Use the Remove-VirtualDiskDrive

cmdlet to remove virtual hard disk

%FileName;.

10673 Unable to share the SCSI adapter. A shared

SCSI adapter can only have one virtual hard

disk attached to location 0.

Ensure that the SCSI adapter has one

virtual hard disk attached to location 0


10674 Integration services cannot be enabled on a

virtual machine that is stored in the library.

Deploy the virtual machine to a Hyper-V

host and then try the operation again.

10675 Virtual machine customization is not

supported for the %OSName; operating

system. Please use the -NoCustomization

parameter to create a template with the

specified operating system.

Specify an operating system for which

customization is supported, or use the -

NoCustomization parameter, and try


10676 Unable to create virtual hard disk %FileName;

on library server %ServerName;. VMM cannot

create a virtual hard disk on a library server

that is not also a virtual machine host.

Select a library server that is also a

virtual machine host, or use an existing

virtual hard disk, and try the operation

again.

10677 The Hyper-V exported file %FileName; is not

valid.

Specify a valid Hyper-V exp file.

10679 The virtual machine %VMName; resource

%FileName; could not be deleted from host

Manually delete resource %FileName;

from the host.

Troubleshooting VMM


%VMHostName;.

10680 Disk %FileName; cannot be attached as a pass-

through to virtual machine %VMName;

because one or more volumes on the disk

already are used by the same virtual machine.

Please specify a disk resource that is not

used by this virtual machine or any

other virtual machine, and then try the

operation again.


%VMHostName; does not allow a virtual

machine name to exceed %MaxLength;

characters.

Specify a shorter virtual machine name


10686 Virtual Machine Manager cannot clone virtual

machine %VMName; on the Virtual Server

host to a Hyper-V host because the virtual

machine is in a saved state.

Delete the saved state, and then try the

operation again.

10687 To create a template from a virtual machine,

the virtual machine must have at least one

virtual hard disk attached.

Ensure that the virtual machine has at

least one virtual hard disk attached, and


10688 Virtual hard disk %FileName; is of type .vmdk.

VMM does not support it on an IDE bus.

Either select a virtual hard disk of

different type or select a SCSI adapter,



adding pass-through disks to virtual machines

with checkpoints.

Ensure that virtual machine %VMName;

does not contain checkpoints and then


10690 Hyper-V does not support boot and system

volumes on a disk attached to SCSI adapter.

The disk at the location (%BusType;, %Bus;,

%Lun;) must be moved to an IDE bus for the

machine to boot up.

Modify the bus assignments so that

boot and system volume disks are

located on an IDE bus.

10691 Hyper-V does not support boot and system

volumes on a disk attached to SCSI adapter. All

disks containing boot and system volumes

must be moved to an IDE bus for the machine

to boot up.



located on an IDE bus.

10803 Unable to refresh %FileName; because the file

is in use by another process.

Wait for the next automatic library

refresh, or manually refresh the library

share after the process completes.

10811 The VMM server was unable to impersonate

the supplied credentials.

The VMM server must run as the local

system account to ensure that it can

impersonate other users.

11020 Virtualization platform on host

%VMHostName; doesn't allow boot and

system volumes to be on a disk attached to

SCSI adapter. Disk at the location (%BusType;,



located on IDE bus, and then try the

operation again.

Troubleshooting VMM


%Bus;, %Lun;) must be attached to the IDE bus

for the machine to boot up and work properly.


%VMHostName; doesn't support pass-though

disks.

Remove pass-though disk from the VM

or try different host

11022 The specified source virtual machine cannot

be used to create a new virtual machine

because the disk at location (%BusType;,

%Bus;, %Lun;) is a pass-through disk and two

virtual machines cannot share the same pass-

through disk.

Specify a different virtual machine as

the source, and then try the operation

again.

11023 Host %VMHostName; doesn't have network

adapter

Please select a different host and then


11024 The bus location for the disk at (%BusType;,

%Bus;, %Lun;) is not valid on host

%VMHostName; for one of the following

reasons:\n1. The Bus exceeds the maximum

number of SCSI adapters(%MaxBusCount;)

supported by the virtualization software on

host. \n2. The LUN exceeds the maximum

number allowed (%MaxLunCount;) by the

virtualization software on host.

Ensure that the bus location for the disk

is valid, and then try the operation

again.

11025 Host %VMHostName; is not available for

placement.

Please select a different host and then


11026 Host %VMHostName; is not responding and is

not available for placement.


operation again.

11027 Clustered host %VMHostName; is not

available for placement. For the host to be

available for placement, the Cluster Service

must be running on the host.


operation again.


%VMHostName; does not support shared DVD

ISO images.

Remove the shared ISO image from

hardware profile or select a different

host.

11029 The disk at the location (%BusType;, %Bus;,

%Lun;) will be moved to the IDE bus. The

virtualization platform on host

%VMHostName; does not allow boot and

system volumes to be on a disk attached to

SCSI adapter.



located on IDE bus, and then try the

operation again.

11030 Host %VMHostName; is not available for

placement because it is in a state that has

limited management functionality. To use an

ESX Server host for placement, you must

Configure the security settings of host

%VMHostName; to enable full

management functionality and then try


Troubleshooting VMM


configure the security settings of the host to

enable full management functionality.


migrated from host %VMHostName; because

the host is in a state that has limited

management functionality. For hosts in the OK

(Limited) state, a virtual machine can only be

migrated within the same Virtual Center

server.

Configure the security settings of host

%VMHostName; to enable full

management functionality, or select a

target host within the same Virtual

Center server, and then try the

operation again.

11400 User role %FriendlyName; already exists. Specify a different user role name and


11402 Cannot remove member %UserName;

because %UserName; is not a member of the

specified user role.

Specify a different user role and then


11410 The user role no longer exists. Close and reopen Windows PowerShell

1.0, and then try the operation again.

11411 Cannot use Set-VMMUserRole with an

Administrator profile. There can be only one

Administrator user role.

You can add or remove members to the

Administrator user role, or delegate

administration, by creating new

Delegated Administrator user roles.

11415 The -ParentUserRole parameter is required for

Set-VMMUserRole with a Delegated

Administrator profile.

Select the ParentUserRole parameter

for the new user role and then try the

operation again.

11416 The -ParentUserRole specified must be a

Delegated Administrator user role.

Select UserRole for the DelegatedAdmin

profile as the ParentUserRole and then


11418 You do not have permission to access one or

more of the objects required by this

operation.



permissions.

11419 You do not have permission to modify this

user role.



permissions.

11420 A connection cannot be established with the

specified virtual machine.


administrator to verify that the user has

access to this virtual machine and that

the VirtualCenter host is running.

11421 There must be at least one member in the

Administrator user role.

Attempt to remove users from the

Administrator role again but leave at

least one user in the role.

11422 The object used with the -AddScope or -

RemoveScope parameter is not valid.

For the -AddScope or -RemoveScope

parameters, only the following types of

Troubleshooting VMM


objects can be used: Template,

HostGroup, or LibraryShare.

11425 The user role specified is not valid. Valid values for the user profile are:

Administrator, DelegatedAdmin or

SelfServiceUser.

11428 The specified user role is not valid or no longer

exists.

The SelfServiceUser value is the only

valid value for -UserRole in this

situation.

11429 The specified user role is not valid because

owner %UserName; of this virtual machine is

not a member of the specified user role.

Add %UserName; as a member of the

specified user role or provide a different

user role, and then try the operation

again.

11430 Either the specified user role or the specified

owner (%UserName;) for this virtual machine

is not valid.

Either add %UserName; as a member of

the user role and the try the operation

again, specify a different user role for

%UserName;, or specify a different

owner.

11431 The user role specified cannot be applied to

this virtual machine because no owner has

been set for this virtual machine.

Set the user role again, specifying an

owner who is a member of the user

role.

11432 The specified parent user role is not a top-

level user role.

Specify a top-level user role as the

parent user role.

11433 This operation could not be completed

because the virtual machine is not associated

with any Self-Service user role.


administrator and have this virtual

machine associated with a user role of

which you are a member.

11436 The Virtual Machine Manager server could not

validate user %UserName;.

Ensure that there is a two-way trust

relationship between the domain of the

VMM Server and the user's domain

11438 Virtual Machine Manager cannot add the

library servers to the scope because the state

of one or more of the library servers is not

valid.

Ensure that all library servers you are

adding to the scope are in the

Responding state and then try the

operation again.

11439 Virtual Machine Manager cannot add one or

more objects to the scope of user role

%UserRoleName; because the objects are not

in the scope of the parent user role

%FriendlyName;.

Ensure that all objects you are adding

are in the scope of the parent user role


11440 The current session with the Self-Service

Portal has been lost. This might have occurred

by changing the browser's current internet

zone for the Self-Service Portal without

Log on to the Self-Service Portal again.

If this problem occurs frequently,

contact your administrator.

Troubleshooting VMM


restarting the browser. This can also occur if

the Web server has been reset.


Management server for this session has been

lost. The server may have been reset or is no

longer available.

Confirm that scripting is enabled for

your browser and log on to the Self-

Service Portal again. If the problem

persists contact your administrator.

11442 The current session with the Self-Service

Portal has been lost. This can be caused by

changing the current internet zone for the

Self-Service Portal without restarting the

browser or by directly browsing to a Self-

Service Portal Webpage without first logging

on to the site.

Log on to the Self-Service Portal again.

If the problem persists, contact your

administrator.

11443 Cannot attach the specified ISO to the virtual

machine because user role %UserRoleName;

associated with the virtual machine does not

have access to the ISO.

Contact your VMM administrator to add

the library share path for the ISO to

user role %UserRoleName; or specify a

different ISO and then try the operation

again.

11444 Unable to add member %UserName; to the

user role %UserRoleName;. Only domain

users, security groups or computers can be

user role members.

Select a valid user role member and try


11445 Virtual Machine Manager could not place this

virtual machine on host %VMHostName;

because there are no volumes available for

placement on this host.

Contact your VMM administrator to

request at least one volume be made

available for placement.



because there are no default virtual machine

paths on this host.


request default virtual machine paths

on this host or access to another host.



because the host does not have any default

virtual machine paths on volumes that are

available for placement.


request at least one default virtual

machine path on a volume that is

suitable and available for placement.

11448 Cannot create this virtual machine because

the selected user role %UserRoleName; does

not have create permissions.

Create a virtual machine from a user

role which has permission or contact

your administrator to gain the

necessary permissions.



because remote connections are not enabled

on this Host.


enabled remote connections on this

host or request access to another host.

Troubleshooting VMM


11601 Unable to move the host cluster

%HostClusterName; to the specified path

because another host cluster with the same

name already exists at that level.

Specify a different location for the host

cluster and then try the operation

again.

11603 Unable to delete host group

%HostGroupName; because the host group for

VirtualCenter server %ServerName; is not

empty. The host group may have hosts

assigned to it, or hosts may be assigned to

child host groups of this host group.

Remove all hosts from this host group

and from any child host groups that the

host group contains, and then try the

operation again.

11604 Unable to delete host cluster

%HostClusterName; because the host cluster

in VirtualCenter server %ServerName; is not

empty.

Remove all hosts from the host cluster


11606 The Virtual Machine Manager Administrator

Console cannot connect to the specified

Virtual Machine Manager server because the

versions are not compatible.

Upgrade the Virtual Machine Manager

client and then try the operation again.

11607 The Virtual Machine Manager Administrator

Console cannot connect to the specified

Virtual Machine Manager server because the

versions are not compatible.

Upgrade the Virtual Machine Manager

server and then try the operation again.

11608 The ID %TaskID; does not map to an existing

VMM job.

Ensure that you typed the job ID

correctly.

11800 Cannot implement PRO tip because it is not

active.

To be implemented, a PRO tip must

have Active status. Do not attempt to

implement a PRO tip that is has

%PROTipState; status.

11801 Cannot dismiss PRO tip because it has been

implemented or implementation is in

progress.

Do not attempt to dismiss a PRO tip

that has %PROTipState; status.

11802 Unable to find the specified PRO tip. Verify that the specified PRO tip has not

been deleted.

11803 Unable to connect to the Operations Manager

root server, %OperationsManagerServer;.

Ensure that the server exists and that

System Center Operations Manager

2007 is installed and then try the

operation again.

11804 The Virtual Machine Manager service does not

have required credentials to access the

Operations Manager SDK service on


Add the VMM service account as an

Administrator on the Operations

Manager server and then try the

operation again.

11805 Unable to verify the connection to the Ensure that the server exists, that

Troubleshooting VMM


Operations Manager root server,



2007 is installed, that Virtual Machine

Manager has the appropriate rights to

perform this action, and then try the

operation again.

11806 Discovery of PRO performance and usage data

was terminated because the VMM 2008

Management Pack has not been imported into

System Center Operations Manager 2007.

Ensure that VMM 2008 Management

Pack is imported on the Operations

Manager Server and then try the

operation again.

11808 Unable to set the Operations Manager root

server in VMM because the Operations

Console for Operations Manager is not

installed on the Virtual Machine Manager

server.

Install the Operations Console for


2007 on the Virtual Machine Manager

server and then try the operation again.

11810 Unable to set %PROParameter; to the given

value.

Enter a valid value for %PROParameter;.

You can enter a number or a text

string:\n\n Turn off PRO tips: "0" or

"Off"\n Receive critical errors only: "1"

or "CriticalOnly"\n Receive critical

errors and warnings: "2" or

"CriticalandWarning"

11811 Cannot implement PRO tip because no

automatic recovery action is defined for the

Operations Manager monitor that generated

the tip.

Review knowledge for the PRO tip for

recommended actions to resolve the

issue.

11812 Cannot update PRO settings because the

cmdlet includes invalid parameters.

To set PRO settings for a host group or a

host cluster, you must set

InheritPROSettings="False" and then set

both the PRO monitoring level

(PROMonitoringLevel parameter) and

PRO automation level

(PROAutomationLevel parameter). To

inherit PRO settings from the parent

host group, set

InheritPROSettings="True".

11819 Unable to inherit PRO settings for the root

host group.

Manually configure the PRO monitoring

and automation settings.

11820 Cannot update PRO settings until the

Operations Manager root server connection is

configured.

Configure the Operations Manager root

server connection using Set-VMMServer

-OpsMgrServer.

11821 Operations Manager server cannot be

specified because the VMM 2008

Management Pack has not been imported.

Use the Configure Operations Manager

option of VMM Setup to import version

%MPVersion; of the System Center

Virtual Machine Manager 2008

Troubleshooting VMM


Management Pack onto your

Operations Manager server, and then

retry the operation. It is recommended

that you use Setup instead of

downloading the management pack

from the System Center Operations

Manager 2007 Catalog to ensure that

other required Operations Manager

configuration tasks are completed.

11822 Operations Manager server cannot be

specified because there is an incompatible

VMM 2008 Management Pack on the

Operations Manager server.

Use the Configure Operations Manager

option of VMM Setup to import version

%MPVersion; of the System Center


Management Pack onto your

Operations Manager server, and then

retry the operation. It is recommended

that you use Setup instead of

downloading the management pack

from the System Center Operations

Manager 2007 Catalog to ensure that

other required Operations Manager

configuration tasks are completed.

11823 Discovery of one or more Virtual Machine

Manager objects monitored by Operations

Manager 2007 failed.

This might be caused by a missing or

outdated version of the System Center


Management Pack in Operations

Manager 2007. To download version

%MPVersion; of the management pack,

open the System Center Operations

Manager 2007 Catalog

(http://go.microsoft.com/fwlink/?

LinkId="86411").

11825 PRO tip implementation failed to start. Ensure that the VMM Administrative

Console is installed on the Operations

Manager root management server and

that the action account that Operations

Manager uses has access to Virtual

Machine Manager.

12409 %ComputerName; cannot be reached. Verify network connectivity between

the Virtual Machine Manager server

and %ComputerName;. If the issue


administrator.

12421 The certificate file on the VMware

VirtualCenter server is not valid.

Ensure that the file is a valid certificate


12700 VMM cannot complete the Hyper-V operation Resolve the issue in Hyper-V and then

Troubleshooting VMM


on the %ServerName; server because of the

error: %VMAsyncTaskErrorMessage;


12701 VMM cannot complete the VMware operation

on the %ServerName; server because of the

error: %VMAsyncTaskErrorMessage;

Resolve the issue in VMware and then


12702 Cannot bind to TCP port %TCPPort; because it

is in use by another process on the


Wait until the other process is

completed, and then try the operation

again.

12703 VMM cannot establish a trust relationship for

the SSL/TLS secure channel for %ServerName;

server.

Install the certificate to the trusted

people root store of the VMM server


12704 Unable to connect to the Hyper-V service on

the server %ServerName;.

Ensure that the Hyper-V Virtual

Machine Management service (vmms)

and the Virtual Machine Manager Agent

are installed and running on the server

%ServerName;.

12705 The volume does not contain a recognized file

system.

Please make sure that all required file

system drivers are loaded and that the

volume is not corrupted.


%ServerName; does not support the

conversion operation on a virtual hard disk.

Select a host with different


operation again.


%ServerName; does not support the

compacting of a fixed virtual hard disk.

To compact the hard disk, migrate the

virtual machine to a host that is running

different virtualization software.

12708 The specified pass-through disk %FilePath;

does not exist on host %ServerName;.

Select an offline pass-through disk and

then try the operation again. If you

have recently changed your disk

configuration, wait approximately 30

minutes or you can manually refresh

the properties by using the Refresh-

VMHost cmdlet and then try the

operation again.

12709 >The operation on %ComputerName; did not

complete successfully because of the error:


Ensure that the parameters are valid,



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


13202 Virtual Machine Manager is unable to emulate

the exact configuration of the source machine

Ensure the virtual machine host

%VMHostName; has adequate

Troubleshooting VMM


%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.

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


operation again.

13204 Boot Configuration Data (BCD) WMI provider

is not installed on the Virtual Machine

Manager Server.

Install the BCD WMI provider on

%ServerName; and then try the

operation again.

13205 The Boot Configuration Data (BCD) file on

virtual machine %VMName; is not recognized.

Ensure that the file boot\BCD on the

boot volume of the virtual machine

%VMName; is not corrupt.

13207 The file system of boot\system volume on

virtual machine %VMName; is not recognized.

Ensure that the boot\system volume on

the virtual hard disk has a valid file

system.

13208 Unable to insert integration services disk

because it is not found on the system drive

path on host %VMHostName;.

Ensure that the host is running Virtual

Server or Hyper-V virtualization

software.

13209 Cannot insert integration services disk

because virtual machine %VMName; on host

%VMHostName; does not have a virtual DVD

drive.

Ensure that the virtual machine has a

virtual DVD drive and then try the

operation again.

13210 Timeout occurred while waiting for VM

integration services to be installed on virtual

machine %VMName; residing on host

%VMHostName;.

Ensure that the version of the VM

integration services binaries matches

the version of the guest operating

system in the virtual machine and then


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.

Troubleshooting VMM


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


%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


%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.


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


%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


See Help for the Virtual Guest Services

installer, resolve any issues preventing

the installation from succeeding, and


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,


Troubleshooting VMM


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


%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


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.

Troubleshooting VMM


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



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


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

Exclude this volume from conversion.

Or, if you are performing an offline

physical-to-virtual conversion, create a

Troubleshooting VMM


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.

new folder under %StaticDriverPath; on

the VMM computer and then copy all of

the storage or networks drivers to the

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.


%StaticDriverPath; on the VMM

machine and then copy all of the



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;


%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;


%StaticDriverPath; on the Virtual

Machine Manager server and then copy

the necessary 32-bit Windows Vista

driver package files for this device to

the new folder. The driver package files

include the driver (.sys) and installation

(.inf and .cat) files. Check the device

manufacturer's website or try the

following link:

%SuggestedDriverLocation; for the

necessary driver files.

13248 VMM does not recognize the format of INF file

%FileName;.

Ensure that the correctness of the

driver package that %FileName; is a part

of and then try the operation again.

13249 Online physical-to-virtual conversion of a

domain controller is not recommended.

To perform an offline conversion, run

the New-P2V cmdlet again, and specify

the -Offline parameter.


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

Specify the same location for all virtual

hard disks and the virtual machine and

Troubleshooting VMM


machine must be placed on the same volume. then try the operation again.

13252 There is already an SSL certificate associated

with port %TCPPort; on machine

%ServerName;.

Ensure that no application on machine

%ServerName; listens for HTTP traffic

on TCP port %TCPPort; during the

conversion. Alternatively use registry

key

HKLM\Software\Microsoft\Microsoft

System Center Virtual Machine

Manager

Server\Settings\P2VBITSTcpPort on the

VMM server to change the P2V transfer

port number and add the necessary

firewall rule for TCP port %TCPPort; on

machine %ServerName;.

13600 The network location override flag must be set

when specifying a network location.

Specify the OverrideNetworkLocation

flag and then try the operation again.

13601 VLAN IDs are not consistent with the VLAN

mode.

For the VLAN Access mode, specify only

-VLANID. For the VLAN Trunk mode,

specify only -VLANTrunkID.

13602 VLAN IDs are specified without the VLAN

mode.

When using -VLANID or -VLANTrunkID,

specify the -VLANMode.

13603 The -OverrideNetworkLocation parameter is

inconsistent with -NetworkLocation.

If -OverrideNetworkLocation is set to

TRUE, specify -NetworkLocation. If -

OverrideNetworkLocation is set to

FALSE, omit -NetworkLocation.

13604 The Virtual Machine Manager server lost

connectivity to host %VMHostName; after

applying the network settings. This might be

the result of an incorrect VLAN setting.

Check connectivity from the Virtual

Machine Manager server to the host. If

there is no connectivity, try connecting

a terminal to the host and reverting the

changes by using the Hyper-V Virtual

Network Manager locally on the host. If

that is not possible, provide

connectivity between the host and the

VMM Server by using a different

network adapter.

13605 Cannot set VLAN properties on physical

network adapter %FriendlyName;, because it

is not connected to a virtual network.

Connect the physical network adapter

to a virtual network and then try the

operation again.

13606 Cannot connect physical network adapter

%FriendlyName; to virtual network

%VirtualNetworkName;, because it is

connected to another virtual network.

Disconnect the physical network

adapter from the other virtual network


13607 The specified network location is not valid. Specify a different network location and


Troubleshooting VMM


13609 The specified MAC address range conflicts

with an existing Organizationally Unique

Identifier (OUI) or reserved address.

Specify a MAC address range, which

does not conflict with an existing OUI or

reserved range.Virtual Machine

Manager default range is

00:1D:D8:B7:1C:00-00:1D:D8:F4:1F:FF.

13610 The specified MAC address range

%RangeStart; - %RangeEnd; is not valid.

1. Specify an end address for the range

that is greater than the start

address.\n\n2.Ensure that the first

three octets of the start address and

the end address for the range are equal.

13611 All addresses in the MAC address range have

been used.

Extend the MAC address range or

specify a new range.

13612 Cannot connect the virtual network adapter

because virtual switch %FriendlyName; on

host %VMHostName; has no available ports.

Use the VMware Virtual Infrastructure

Client to increase the number of

ports.\n\nNote: This setting requires

the host to be restarted.

13613 Cannot set VLAN properties on virtual network

%FriendlyName;, because the virtual network

is not bound to the host.

Connect the virtual network to the host


13619 The host physical network adapter cannot be

removed from virtual network

%VirtualNetworkName; because the virtual

network has a VMware service console port

on host %ServerName;.

Remove the service console port from

virtual network %VirtualNetworkName;

by using the VMware Virtual

Infrastructure Client or specify a

different virtual network.

13621 The -Path parameter must be specified for

New-VirtualNetwork.

Specify the -Path parameter and then


13623 Cannot remove physical network adapter

%FriendlyName; from virtual network

%VirtualNetworkName; because the adapter

is not connected to the virtual network.

Specify a different host network

adapter and then try the operation

again.

13626 The specified virtual network does not exist. Run Get-VirtualNetwork and ensure

that the virtual network is on the list.

13800 The host cluster name contains a character

that is not allowed.

A host cluster name cannot contain any

of the following characters: : * ? < > / |

\ ". Check the host cluster name and


13801 A host cluster with the name

%HostClusterName; already exists.

Specify a different host cluster name


13802 A cluster with the name %HostClusterName;

does not exist.

Specify a different cluster name and


13803 The cluster node failure reserve equals or Specify a cluster node failure reserve

Troubleshooting VMM


exceeds the number of nodes in cluster

%HostClusterName;.

less than the number of nodes in the

cluster and then try the operation

again.

13806 The host does not exist in cluster

%HostClusterName;.

Specify a different host name and then


13807 Unable to add %ComputerName; as a virtual

machine host.

Ensure that the specified machine name

is a cluster name or a node of a cluster,


13808 Unable to add %ComputerName; as a Library

server.

Ensure that the specified machine name

is a clustered file server or a node of a

cluster, and then try the operation

again.

13811 Virtual network %FriendlyName;, configured

on host %ComputerName;, is not highly

available.

To make the virtual network highly

available, ensure that a virtual network

with the same name, tag, and

connectivity exists on all hosts in the

cluster.

13813 The specified VMware resource pool was not

found.

Ensure that the resource pool exists in

this virtualization manager and then try


13814 The virtual machine %ComputerName; cannot

be moved to VMware resource pool

%FriendlyName;.

Ensure that the target resource pool

belongs to the same computer resource


13815 Virtual Machine Manager could not

enumerate the network shares on

%ComputerName;.

Ensure that the computer

%ComputerName; exists, that the

specified credentials have

administrative rights, and then try the

operation again.

13919 Specified failure node reserve

(%ParameterValue;) exceeds the %MaxLimit;

limit for host cluster %HostClusterName; (total

nodes in cluster- 1).

Specify a failure node reserve less than

or equal to %MaxLimit;.

13921 Highly available virtual machine %VMName; is

not supported by VMM because one or more

of its network adapters is not configured

correctly.

Ensure that all of the virtual network

adapters are either disconnected or

connected to highly available virtual

networks.


not supported by VMM because one or more

of its network adapters is not configured

correctly.

Ensure that all of the virtual network

adapters are either disconnected or

connected to highly available virtual

networks. Additionally, each port group

the VM is connected to must be present

on each of the nodes of the cluster.

Troubleshooting VMM

Troubleshooting Operations Manager, PRO, and Reporting Issues in VMM / Configure

Operations Manager Setup option is not completed successfully Page 116


not supported by VMM because its cluster

resource group is not configured correctly.

Ensure that the resource group only

contains a single VM resource, a single

VM configuration resource, and zero or

more disk resources all belonging to this

VM.


not supported by VMM because the VM uses

non-clustered storage.

Ensure that all of the files and pass-

through disks belonging to the VM

reside on highly available storage.

13925 Host cluster %HostClusterName; cannot be

removed directly from Virtual Machine

Manager because it is a VMware cluster.

To remove the host cluster from Virtual

Machine Manager, remove the

Virtualization Manager that it belongs

to. To destroy the host cluster, use the

VMware Virtual Infrastructure Client.

13926 Host cluster %HostClusterName; was not fully

refreshed. The host cluster might appear to

not have highly available storage or virtual

networks.

Ensure that all the nodes are online and

do not have Not Responding status in

Virtual Machine Manager. Then refresh

the host cluster again.

Troubleshooting Operations Manager, PRO,

and Reporting Issues in VMM

This topic provides guidance for troubleshooting issues with Performance and Resource Optimization

(PRO), reporting, and the integration of System Center Operations Manager 2007 with System Center

Virtual Machine Manager (VMM) 2008 and Virtual Machine Manager 2008 R2.

Configure Operations Manager Setup option is not

completed successfully

Possible causes • The root management server for Operations Manager is in a different Active Directory

domain than the VMM server. If the two servers are in different domains, manual

configuration of Operations Manager is required.

• The VMM server is in a disjointed namespace, and the server was not identified by its fully

qualified domain name (FQDN).

• The Configure Operations Manager option of the VMM Setup Wizard is run on the root

management server too soon after you install the VMM server. The Setup Wizard attempts

to add the VMM service account to the local Administrators group on the root management

server. That operation will fail unless you allow time for the service connection point (SCP) to

replicate to your Active Directory Domain Services (AD DS) domain controllers.

• A VMM Administrator Console is already installed on the root management server when you

run the Configure Operations Manager option of the VMM Setup Wizard.

Troubleshooting VMM

Troubleshooting Operations Manager, PRO, and Reporting Issues in VMM / Access denied

when specifying the Operations Manager server for VMM Page 117

Solutions • If your root management server is in a different domain from the VMM server, do not use

the Configure Operations Manager option of the VMM Setup Wizard. Instead, follow the

instructions in How to Manually Configure Operations Manager for VMM 2008 R2.

Important

This procedure explains how to perform one task in the integration process. To ensure a

successful integration, do not perform this procedure without first performing the integration

tasks that precede this one, as described in How to Integrate Operations Manager with VMM

2008 R2.

• If the VMM server is in a disjointed namespace, run the Configure Operations Manager

option of the VMM Setup Wizard again, and identify the VMM server by its FQDN.

• If you run the Configure Operations Manager option of the VMM Setup Wizard immediately

after you install the VMM server, the service connection point (SCP) might not replicate to

your AD DS domain controllers before the wizard runs. Run the Setup Wizard again after

allowing time for AD DS replication. AD DS replication time varies, depending on your

network configuration, locations of your domain controllers, and the size and complexity of

your AD DS environment.

• If a VMM Administrator Console is installed on the root management server when you run

the Configure Operations Manager option of the VMM Setup Wizard, a message appears

that states that the Setup Wizard will remove the console. Finish the wizard to allow it to

remove the console. Then, run the wizard again.

Access denied when specifying the Operations Manager

server for VMM

Possible causes • The OpsMgr SDK Service in Operations Manager 2007 (known as the System Center Data

Access service in Operations Manager 2007 R2) is unable to register Service Principle Names

(SPNs) for itself in AD DS. This is the most common cause of an Access Denied error message

when you attempt to specify the Operations Manager server in VMM. This error message is

associated with error event 26371 (0x80006703) in the Operations Manager event log, but it

is manifested in VMM as an Access Denied error. Every time the OpsMgr SDK Service starts

on your Operations Manager root management server, the service must be able to register

SPNs for itself in AD DS. If the SDK service runs as Local System, the account has the

necessary permissions to read and write the SPNs and you do not have to update any

configurations. However, if you are using an Active Directory domain account as the service

account, you must either manually register the SPNs for the root management server or you

must grant the SDK service account the permissions that it requires to read and write the

SPNs when the service starts.

• The service account for the VMM server was not added to the Administrator role in

Operations Manager.

Solution Use the following procedure to troubleshoot these issues.

To troubleshoot Access Denied issues when specifying the Operations Manager server in VMM

Troubleshooting VMM

Troubleshooting VMM Cmdlet Issues / The Add-Patch cmdlet does not run on a VMM 2008

server installed on a Windows Server 2008 computer Page 118

1. To verify that SPNs are registered correctly, log on to a computer that is in an Active

Directory domain by using an account that has Read SPN permission, and then run the

following command, where <computername> identifies the root management server:

SetSPN.exe –L <computername>

2. If the command does not return SPNs for the root management server, use the procedures in

task 1 in How to Integrate Operations Manager with VMM 2008 R2 either to manually

register the SPNs for the root management server or to grant the SDK service account the

permissions that it requires to read and write the SPNs when the service starts. Task 1

provides steps to verify that an Operations Manager deployment meets the requirements of

VMM.

3. Ensure that the VMM service account is a member of the Administrator role in Operations

Manager. To add the account to the Administrator role, follow the instructions in How to Add

Members to the Administrator Role in Operations Manager 2007.

4. On the root management server, restart the SDK service. (In Operations Manager 2007 SP1,

the service name is OpsMgr SDK Service; in Operations Manager 2007 R2, the service name is

System Center Data Access service.)

5. Restart the root management server.

6. Specify the Operations Manager server in VMM by following the steps in How to Specify the

Operations Manager Server for VMM.

7. If you still receive an Access Denied error message, contact Customer Support Services (CSS)

for VMM. For more information about VMM support options, see System Center Virtual

Machine Manager Troubleshooting and Support

(http://go.microsoft.com/fwlink/?LinkID=68951).

Troubleshooting VMM Cmdlet Issues

This topic provides guidance for troubleshooting issues when you are working with System Center

Virtual Machine Manager (VMM) cmdlets.

The Add-Patch cmdlet does not run on a VMM 2008 server

installed on a Windows Server 2008 computer

Possible cause (or causes) Garbage collection is enabled on the server in the vmmservice.exe.config file.

Solution (or solutions) Remove the vmmservice.exe.config file from the %SYSTEMDRIVE%\Program Files\Microsoft System

Center Virtual Machine Manager 2008\Bin directory, and then restart the Virtual Machine Manager

service. You can then run the Add-Patch cmdlet.

After the Add-Patch cmdlet is finished running, you can re-enable garbage collection by moving the

vmmservice.exe.config file back to the %SYSTEMDRIVE%\Program Files\Microsoft System Center

Virtual Machine Manager 2008\Bin directory and restarting the Virtual Machine Manager service.