System Center 2012 – Virtual Machine Manager (VMM) Error Codes [0-499]

Use Ctrl-F to find a specific code.

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

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

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

 

Code	Message	Recommended Action (in product)	Additional Troubleshooting Information
200	VMM cannot connect to the service.\nService name: %ServiceName;.	Check the Windows Event Log for troubleshooting information.
201	VMM cannot ensure configuration of the service.\nService name: %ServiceName;.	Check the Windows Event Log for troubleshooting information.
202	VMM cannot connect to the Service Control Manager (SCM).	Check the Windows Event Log for troubleshooting information.
203	VMM cannot start the service. Service name: %ServiceName;	Click Start, click in the Search programs and files box, type services. msc, and then press Enter. Right-click the service name, and then click Start.
204	VMM cannot stop 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 R2 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.
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 file, and then try the operation again.
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 try the operation again.
218	(Internal error.)
219	(Internal error.)
220	This computer is not part of a domain.	Virtual Machine Manager requires a computer that is a member of a doma in. 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.
222	There is insufficient disk space on the program files volume %BinaryVolumeDriveLetter; to complete the installation.	Create %BinaryDiskSpaceRequired; MB of disk space on the volume to continue with the installation.
223	There is insufficient disk space on the database volume %DatabaseVolumeDriveLetter; to complete the installation.	Create %DatabaseDiskSpaceRequired; MB of disk space on the volume to continue with the installation.
224	Setup has detected instance MICROSOFT$VMM$ running on an older version of SQL Express 2005.	Uninstall MICROSOFT$VMM$ and then run Virtual Machine Manager Setup again to install SQL Express 2005 Service Pack 3.
225	Setup has detected SQL instance %SqlInstance; on the local server.	Select "Use an existing SQL Server instance", and then try the operation again.
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 feat ures and then install Virtual Machine Manager 2008 R2.
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.
229	System Center Virtual Machine Manager requires Windows PowerShell 1.0 or 2.0.	To download Windows PowerShell 1.0, go to http://go.microsoft.com/fwlink/?LinkId=77521.
230	Virtual Machine Manager cannot be successfully installed because service %ServiceNa me; 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 SP3 instance, and then continue with S etup.
232	(Internal error.)
233	The SQL Server database %DatabaseName; is currently in use by another program or pr ocess.	Select another database and try again. If this is a highly available V MM management server installation, ensure that all active VMM consoles are closed while VMM Setup installs the VMM management server.
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 install ed.	Delete %DatabaseName; from SQL instance %SqlInstance; and then continue with Setup.
236	System Center Virtual Machine Manager 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 add the Web Serv er (IIS) role and enable the ASP.NET, IIS 6 Metabase Compatibility and IIS 6 WMI Compatibility server role services.
237	(Internal error.)
238	(Internal error.)
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.
240	Setup has detected an unsupported version of Windows PowerShell. System Center Virt ual Machine Manager requires Windows PowerShell 1.0 or 2.0.	Uninstall the existing version of Windows PowerShell, and then to down load Windows PowerShell 1.0, go to http://go.microsoft.com/fwlink/?LinkId=77521.
241	Disk space cannot be calculated.	Select a different installation location, and then try the operation a gain.
242	VMM cannot read the Virtual Machine Manager installation path registry key. Some fo lders cannot be deleted.	View the error log for a complete list of folders, and delete those fo lders manually.
243	System Center Virtual Machine Manager requires Windows Remote Management (WinRM) 1. 1.	To download WinRM 1.1, go to http://go.microsoft.com/fwlink/?LinkId=84 599.
244	The Windows Remote Management (WinRM) service is not running on the computer.	Verify that WinRM service is running, and then try the operation again .
245	SQL service %ServiceName; is not running on the computer.	Verify that service %ServiceName; is running, and then try the operati on again.
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.
247	Setup has detected an unsupported version of Windows Remote Management (WinRM). Virttual Machine Manager requires WinRM 1.1.	To download WinRM 1.1, go to http://go.microsoft.com/fwlink/?LinkId=84599.
248	VMM management 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.
250	System Center Virtual Machine Manager Workgroup Edition cannot manage more than fiv e 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 http:// go.microsoft.com/fwlink/?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 produc t 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.
258	(Internal error.)
259	(Internal error.)
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.
261	The parameter %InputParameterTag; is missing.	Select a value for the parameter.
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.
265	(Internal error.)
266	The path %FileName; exceeds %MaxLimit; characters.	Enter a shorter path name, and then try the operation again.
267	Installation source %FolderPath; for installing prerequisites does not exist, canno t 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 a gain.
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 then try the operation a gain.
272	The selected location %DirectoryPath; is read-only, hidden, a system folder, or a r oot 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.
274	The directory %DirectoryPath; is not on an NTFS volume.	Install prerequisite software and Virtual Machine Manager on an NTFS volume, and then try the operation again.
275	The volume information for directory %DirectoryPath; cannot be acquired.	Select a different installation location, and then try the operation again.
276	The parameter %CommandlineArgument; is not valid.	See "Installing Virtual Machine Manager" in the Virtual Machine Manage r Setup help for information about parameter usage.
277	The parameter %CommandlineArgument; is already specified.	See "Installing Virtual Machine Manager" in the Virtual Machine Manage r setup help for information about parameter usage.
278	The parameter %CommandlineArgument; does not have a value associated with it.	See "Installing Virtual Machine Manager" in the Virtual Machine Manage r 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.
283	(Internal error.)
284	Setup has detected an existing installation of Virtual Machine Manager on this computer.	To install Virtual Machine Manager, uninstall the existing version, a nd then run Setup again.
285	%InputParameterTag; must be an integer between 0 and 65535.	Enter the port number again.
286	(Internal error.)
287	(Internal error.)
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 re mediate it. Once the failure has been resolved, try the uninstallation again.
291	(Internal error.)
292	Configuration of Virtual Machine Manager failed.	For more information about configuration, see "Troubleshooting" in th e Virtual Machine Manager Setup help.
293	Setup could not remove the shortcuts to the VMM console from: %CommaSeparatedShort cutLocations;.	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 t he 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 management server.	Enter the name of an existing share.
300	Setup was unable to delete the SQL login %SqlLoginName; from SQL instance %SqlInst ance; 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 a s", 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 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 an d 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 VMM console from: %CommaSeparatedShort cutLocations;.	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.
315	(Internal error.)
316	Setup could not configure the firewall exceptions.	If the configuration is being run from OEM Setup, verify that Setup h as the necessary privileges to configure firewall exceptions, and then run the configuration again. Otherwise, uninstall the VMM management 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.
318	(Internal error.)
319	The Virtual Machine Manager database was not created.	The Virtual Machine Manager database was not created. Delete %Databas eName;.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 %DataFilesCompleteLocation; could not be removed.	Delete the files manually.
322	Cannot locate the file SqlCmd.exe.	Install the SQL Client Tools and then run Setup again.
323	The Virtual Machine Manager database was not created from the existing database files.	Delete the existing files or choose another location for the database .
324	(Internal error.)
325	Cannot enable the service %ServiceName;.	Enable the service in the Services MMC snap-in 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;.	Check the Windows Event Log for troubleshooting information.
329	Could not install the necessary Setup files from %SourceLocation; to %InstallLocat ion;.	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.
333	(Internal error.)
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.
335	(Internal error.)
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.
338	(Internal error.)
339	Setup cannot connect to the specified SQL Server instance.	Ensure that the server name, instance name, and, if specified, port n umber are correct. If you are installing VMM remotely, ensure that remote connections are set up correctly, and then tr y 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 correct ly.
348	An error has occurred while trying to connect to database %DatabaseName;.	Ensure that the SQL Server service %ServiceName; can be started and t hat you have permissions to query the SQL Server.
349	(Internal error.)
350	Setup cannot write to file %FileName;.	Delete the file if it exists, and then run Setup again.
351	An error has occurred while trying to delete database %DatabaseName;.	Manually delete %DatabaseName; from SQL instance %SqlInstance;.
356	(Internal error.)
357	(Internal error.)
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 check the "Existing database" radio button 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 "New database" radio button to create a new database, or us e an existing database.
363	The Virtual Machine Manager database could not be upgraded.	Uninstall the VMM management server selecting the "Retain data" optio n, and then try installing the VMM management server again.
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.
365	System Center Virtual Machine Manager is not preinstalled on this computer.	For more information about installing Virtual Machine Manager go to http://go.microsoft.com/fwlink/?LinkId=117338.
366	System Center Virtual Machine Manager requires the Windows Automated Installation Kit (WAIK) 2.0 to be installed.	To download the Windows Automated Installation Kit, go to http://www. microsoft.com/downloads/details.aspx?familyid=696DD665-9F76-4177-A811-39C26D3B3B34.
367	Setup has detected an unsupported version of Windows Installer.	To install the correct version of Windows Installer, go to http://go. microsoft.com/fwlink/?LinkId=117300.
368	To continue, your computer must be restarted.	Cancel the VMM management server setup, restart the computer, and the n run the VMM management server setup again.
369	Run command %FileName; with argument %CommandlineArgument; failed.	Verify that the command and arguments are correct and then run VMM ma nagement server setup again.
370	The VMM Self-Service Portal requires the IIS 6 Management Compatibility role servi ce.	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.
372	An error occurred while trying to register the Virtual Machine Manager Volume Shad ow Copy Service (VSS) writer.	Uninstall Virtual Machine Manager, and then run Setup again.
373	Setup was unable to unregister the Virtual Machine Manager Volume Shadow Copy Service (VSS) writer.	Unregister the writer manually.
400	The server %ComputerName; is already associated with this VMM management server.	Check the remote server name, and try the operation again.
401	Virtual machine host %ComputerName; is not associated with this VMM management ser ver.	Check the virtual machine host name and then try the operation again.
402	Library server %ComputerName; is not associated with this VMM management server.	Check the library server name, and try the operation again.
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.
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, and then try the operation again.
407	The agent operation with server %ComputerName; was not successful.	Try the operation again. If the problem persists, ensure that the VMM management 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 VMM management server. A computer can only be associated with one VMM management server at a time.	Remove the association of %ComputerName; from its current Virtual Machine Manager management server or uninstall the Virtual Machine Manager agent using Add or Remove Programs on %Computer Name; 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, and then try the operation again.
412	SCVMM cannot configure Virtual Machine Remote Client (VMRC) on host server %Comput erName;.	Try the operation again.
413	The files needed to install agent, version %SoftwareVersion;, are missing from the VMM management server %ServerName;.	Reinstall the missing files by running VMM management server Setup.
414	Agent installation could not access the ADMIN$ share on server %ComputerName;.	1. Verify that the selected user account has administrative privilege s on %ComputerName;.\n2. Verify the permissions on the ADMIN$ share of %ComputerName;. The ADMIN$ share must allow writ e access to the Administrator group.\n3. Verify that the system time on the VMM management server and the server %Compu terName; 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 file and printer sharing is enabled on %ComputerName; and it not blocked by a firewall. \n3. Ensure that there is sufficient free space on the system volume. \n4. 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 the operation again.
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 http://go.microsoft.com/fwlink/?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.
420	Agent installation failed on %ComputerName; because of an incompatible operating s ystem version.	Verify that %ComputerName; is running either Windows Server 2003 SP2 or Windows Server 2003 R2 operating system.
421	Agent installation failed on %ComputerName; because of a WS-Management configurati on error.	Ensure that the Windows Remote Management service is enabled and runn ing on the server %ComputerName;. Additionally, in the Local Group Policy Editor (gpedit.msc), navigate to Computer Con figuration\Administrative Templates\Windows Components\Windows Remote Management (WinRM), and then ensure that there ar e no policy settings configured for WinRM Client or WinRM Service.
422	Machine %ComputerName; is not associated with this VMM management server.	Check the machine name, and then try the operation again.
423	Source machine is not associated with this VMM management server.	Check the source machine name, and then try the operation again.
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 VMM management server.	Verify that the agent is installed on the computer, %ComputerName; is accessible from the VMM management 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 then try the operation again.
429	Failed to configure Virtual Machine Remote Client (VMRC) on host server %ComputerN ame;.
431	The servers in domain %FriendlyName; cannot be enumerated.	Check the name, and then try the operation again.
434	The status of managed computer %MachineName; changed from %FromState; to %ToState; .
435	The status of host %MachineName; changed from %FromState; to %ToState;.
436	The state of library %MachineName; changed from %FromState; to %ToState;.
437	Service %ServiceName; could not be stopped on %ComputerName;.	Stop the service locally in the Services MMC snap-in by running servi ces.msc on %ComputerName;, choose the service %ServiceName;, right-click and then select Stop.
438	Service %ServiceName; is not present on %ComputerName;.	Check that the service exists in the Services MMC snap-in on %Compute rName; by running services.msc.
439	VMM is unable to add the server %ComputerName; as a managed computer because the s erver is not listed in Active Directory Domain Services.	Verify that the server name and the domain name are correct, and then try the operation again.
440	Virtual Machine Manager is unable to add the server %ComputerName; as a managed co mputer because the operating system is not supported. Managed computers must be running Windows Server 2003 SP2 or late r.	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 s oftware or the VMM agent is unsupported.	Update the agent and virtualization software, and then try the operat ion again.
442	The agent version state of managed computer %MachineName; changed from %FromState; to %ToState;.
443	The virtual server version state of host %MachineName; changed from %FromState; to %ToState;.
444	%ComputerName; is a VMM management server. A VMM management server cannot be assoc iated with another VMM management server.	Uninstall the VMM management 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 snap-in by running serv ices.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.
447	Agent installation failed on %ComputerName; because the supported version of Windo ws Remote Management (WinRM) is not installed.	Download WinRM from http://go.microsoft.com/fwlink/?LinkId=84599.
450	The specified host name %FriendlyName; does not match the name in the security fil e. The name in the security file is %ComputerName;.	Ensure that the host name is correct in the security file and try the operation again.
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 file, and then try the operation again.
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.
457	The server %ComputerName; could not be disassociated from this VMM management server.
458	The Virtual Machine Manager agent could not be removed from %ComputerName;.	Uninstall the Virtual Machine Manager agent using Add or Remove Programs on %ComputerName;.
459	Agent update failed on %ComputerName;.	Try the operation again. If the error persists, reboot %ComputerName; and then try the operation again.
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 then try the 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.
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.
466	System Center Virtual Machine Manager Workgroup Edition cannot manage more than fi ve hosts.	To manage more than five hosts, you must upgrade System Center Virtual Machine Manager. For information about upgrading, go to http://go.microsoft.com/fwlink/?LinkId=117133
467	System Center Virtual Machine Manager Workgroup Edition cannot manage more than five hosts.	Remove some existing hosts and then try the operation again. To manag e more than five hosts, upgrade VMM Workgroup Edition. Find information on upgrading at http://go.microsoft.com/fwlink/ ?LinkId=117133. Command Line Interface: 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 Machine Manager. For information about upgrading, go to http://go.microsoft.com/fwlink/?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 management server or if the host is on a perimeter network.	Add the cluster as a trusted domain host.