Virtual Machine Manager Error Codes (2000-2499)
Links to other error code pages can be found on the Virtual Machine Manager (VMM) 2008 R2 Error Codes page.
To find a specific error message in this table, type Ctrl-F and enter the error code. If you have additional information about how to fix an error, add it to the "Additional Troubleshooting Information" column.
Code | Message | Recommended Action (in product) | Additional Troubleshooting Information |
2200 | Could not find the specified virtual machine checkpoint. | Ensure the specified virtual machine checkpoint exists and try the operation again. | |
2201 | The selected virtual machine will need to be shut down in order to create a new checkpoint.\n\nDo you want to continue? | BLANK | |
2202 | The selected virtual machine will need to be shut down and restarted in order to create a new checkpoint.\n\nDo you want to continue? | BLANK | |
2203 | All changes and checkpoints for this virtual machine made after checkpoint %CheckpointName; will be lost after using this checkpoint to restore the virtual machine.\n\nDo you want to continue? | BLANK | |
2204 | All checkpoints created after the selected checkpoint will also be removed. After being removed, checkpoints cannot be used to restore the virtual machine.\n\nDo you want to continue? | BLANK | |
2205 | Checkpoint %CheckpointName; will be removed.\n\nDo you want to continue? | BLANK | |
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. | |
2208 | The Virtual Machine Manager database %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 then try the operation again. | |
2214 | Checkpoint actions on virtual machine %VMName; are unsupported because one or more hard disks are shared with other virtual machines. The shared hard disks are: %ObjectList;. | Ensure that the virtual machine doesn't share any hard disks with other virtual machines. | |
2215 | Virtual Machine Manager must shut down the following virtual machines to create the new checkpoint: %ObjectList;.\n\nDo you want to continue? | BLANK | |
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 %MaxLimit; characters. | 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 then try the operation again. | |
2218 | BLANK | ||
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. | |
2220 | Checkpoint %CheckpointName; will be restored.\n\nDo you want to continue? | BLANK | |
2221 | A new checkpoint cannot be created for 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 and then try the operation again. | |
2222 | A new checkpoint cannot be created for 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 try the operation again. | |
2223 | A new checkpoint cannot be created for 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. | |
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;. | Specify a valid share path on %ComputerName; to the virtual machine to be saved, and then try the operation again. | |
2402 | VMM cannot rename %FileName; because a file or folder with that name already exists. | Specify a different folder name, and then try the operation again. | |
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 %FileName;. | Verify that the folder name is valid, and that 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, 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 determined by the Active Directory replication policy for the domain. | |
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 then try the operation again. | |
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). | |
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. | |
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. | |
2414 | You have selected %NumberOfMembers; members to remove from this user role.\n\nDo you want to continue? | BLANK | |
2415 | BLANK | ||
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. | |
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. |