System Center 2012 – Virtual Machine Manager (VMM) Error Codes [1500-1999]
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 |
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 VMM management server %ServerName; because the specified computer name could not be resolved. |
Close and then reopen the VMM console, and then try the operation again. If the problem persists, contact your network administrator. Command Line Interface: 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 VMM management 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 VMM management server %ServerName;. The attempt to connect timed out. |
1) Verify that %ServerName; is online and accessible from your computer. 2) If a firewall is enabled on %ServerName;, ensure that it is not blocking requests for TCP port %RemoteUIPort;. Command Line Interface: 1) Verify that %ServerName; is online and can be accessed from your computer. 2) If a firewall is enabled on %ServerName;, ensure that it is not blocking requests for TCP port %RemoteUIPort;. |
|
1604 |
You cannot access VMM management server %ServerName;. |
Contact the Virtual Machine Manager administrator to verify that your account is a member of a valid user role and then try the operation again. |
|
1605 |
You cannot contact the VMM management server. The credentials provided have insufficient privileges on %ServerName;. |
Ensure that your account has access to the VMM management server %ServerName;, and then try the operation again. |
|
1606 |
Unable to connect to the VMM management server %ServerName; on port %RemoteUIPort; . |
Verify that the server name and port number are correct. |
|
1607 |
You cannot contact the VMM management server. The credentials provided have admini strator privileges instead of self-service only privileges on %ServerName;. |
Use the troubleshooting mode of the Self-Service Portal, and then try the operation again. |
|
1610 |
The connection to the VMM management 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 th e 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 management 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;"} |
|
1612 |
The connection to the Virtual Machine Manager management server %ServerName; was lost. |
1) Verify that %ServerName; is online and can be accessed from your c omputer. 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. |
|
1613 |
The connection to the Virtual Machine Manager management 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 VMM console. |
|
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. |
|
1615 |
VMM is unable to perform this operation without a connection to a Virtual Machine Manager management server. |
Use the Get-VMMServer cmdlet or the -VMMServer parameter to connect t o a Virtual Machine Manager management server. For more information, type at the command prompt: Get-Help Get-VMMServer -detailed. |
|
1616 |
Unable to start SCVMMService because the VMM database has more than five hosts. |
VMM Workgroup Edition can manage a maximum of five hosts. Uninstall the Virtual Machine Manager management server using the "Remove data" option, or upgrade VMM Workgroup Edition to manage more than five hosts. Find information on upgrading at http://go.microsoft.com/fwlink/?LinkId=117133. |
|
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. |
Contact the Virtual Machine Manager 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 website is running under the NETWORK SERVICE identity and that no restrictions have been placed on this account that would prevent impersonation. |
|
1620 |
(Internal error.) | ||
1621 |
The connection to Virtual Machine Manager has been disconnected because the scope of the current user was changed. |
BLANK |
|
1650 |
This action will cancel all of the selected jobs.\n\nAre you sure you want to continue? |
||
1651 |
VMM will attempt to restart the selected jobs from the last known status. This may require restarting from the beginning and any interim changes may be discarded.\n\nDo you want to restart the selected jobs? |
||
1652 |
Are you sure you want to cancel the wizard? All entered data will be lost. |
||
1653 |
One or more of the selected jobs were started by another user. This action will cancel all of the selected jobs.\n\nAre you sure you want to cancel the selected jobs? |
||
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. Command Line Interface: 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;. |
To restart the job, select the job in the Jobs view, and click Restart. Command Line Interface: Restart the job by running the following command:\n\nPS> Restart-J ob -Job (Get-VMMServer %ServerName; | Get-Job | where { $_.ID -eq "%TaskID;"}) |
|
1702 |
The job could not be restarted. Only failed jobs may be restarted. |
BLANK |
|
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;. |
|
1704 |
A %FriendlyName; job was started with ID %TaskID;. |
||
1705 |
Job %TaskID; (%FriendlyName;) completed successfully. |
||
1706 |
Job %TaskID; (%FriendlyName;) failed to complete. |
||
1707 |
Job %TaskID; (%FriendlyName;) was canceled. |
||
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. |
|
1711 |
The Virtual Machine Manager service on the %ServerName; server stopped while this system job was running. This may have been caused by a system restart. The job will automatically run again later. |
BLANK |
|
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 a gain. |
|
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;, and then try the operation again. |
|
1734 |
Connecting to virtual machine %VMName; will start the machine.\n\nAre you sure you want to connect to %VMName;? |
||
1735 |
The virtual machines cannot be shut down because Virtual Guest Services are not installed on the guest operating system (%ObjectList;) or because the installed Virtual Guest Services do not support shutting down the guest operating system that is running on the virtual machine. |
To shut down, you must install Virtual Guest Services that support shutting down the guest operating system. |
|
1736 |
Cannot connect to virtual machine %VMName; because the Virtual Guest Services feat ure is not available. |
If the VMM 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. |
|
1737 |
The virtual machine %VMName; cannot be 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 Ma chine Manager Help. |
|
1738 |
The virtual machine %VMName; cannot be migrated to a different host because its cu rrent 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 Ma chine Manager Help. |
|
1739 |
Cannot connect to virtual machine %VMName; because the virtual machine is not running. |
Start the virtual machine, and then try the operation again. |
|
1740 |
Another user is already connected to the virtual machine (%VMName;). If you continue, that user will be disconnected.\n\nDo you want to continue? |
||
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 exist s on the Virtual Machine Manager management 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 then try the operation again. |
|
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 th e operation again. |
|
1753 |
Unable to modify host group %HostGroupName; because the host group has been delete d. |
To update the list of host groups, restart the Virtual Machine Manage r service, or wait until the host groups list is automatically refreshed. |
|
1754 |
Root host group properties cannot be modified. |
BLANK |
|
1755 |
Unable to delete host group %HostGroupName; because the host group is not empty. T he 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 %HostGroupNa me;. |
|
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 %HostGroupN ame; host group. |
|
1758 |
Unable to change the host group name because no name was specified. |
Enter a name for this host group. |
|
1759 |
Deleting %HostGroupName; host group will remove all of its child host groups.\n\nD o you want to continue? |
||
1760 |
The settings on the root host group cannot be changed to inherit. |
BLANK |
|
1761 |
The Disk IO Reserve mode values must be one of [IOPS, Percent]. |
BLANK |
|
1762 |
Disk Space Reserve mode values must be one of [MB, GB, Percent]. |
BLANK |
|
1763 |
Memory Reserve mode values must be one of [MB, GB, Percent]. |
BLANK |
|
1764 |
Network IO Reserve mode values must be one of [Mbps, Percent]. |
BLANK |
|
1765 |
The EndHour parameter value must be larger than the StartHour parameter value. |
Alter the end hour to a value larger than the start hour parameter and try the action again. |
|
1766 |
Unclustering %HostClusterName; will release the clustered hosts and delete the cluster.\n\nDo you want to continue? |
||
1770 |
The following virtual machine hosts will no longer be managed by this Virtual Machine Manager management server: %ObjectList;.\nDo you want to continue? |
||
1771 |
You have chosen to remove the following virtual machines from Virtual Machine Manager and delete their virtual hard disks: %ObjectList;.\n\nDo you want to continue? |
||
1772 |
Stopping a virtual machine causes a loss of service to any users of the machine. Y ou have chosen to stop the following virtual machines: %ObjectList;.\n\nDo you want to continue? |
||
1773 |
Pausing a virtual machine causes a loss of service to any users of the machine. You have chosen to pause the following virtual machines: %ObjectList;.\n\nDo you want to continue? |
||
1774 |
Placing a virtual machine in a saved state causes a loss of service to any users o f the machine. You have chosen to save the following virtual machines: %ObjectList;.\n\nDo you want to continue? |
||
1775 |
Shutting down a virtual machine causes a loss of service to any users of the machine. You have chosen to shut down the following virtual machines: %ObjectList;.\n\nDo you want to continue? |
||
1776 |
You have chosen to discard saved state for the following virtual machines: %Object List;.\nAfter discarding saved state, you cannot resume a virtual machine in the condition in which it was saved.\n\nDo you want to continue? |
||
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, and then try the operation again. |
|
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. |
|
1779 |
Restarting a virtual machine causes a temporary loss of service to any users of the machine. You have chosen to restart the following virtual machines: %ObjectList;.\n\nDo you want to continue? |
||
1780 |
One or more of the selected virtual machines are missing or their virtual machine host is not responding. Deleting these virtual machines will remove their record from Virtual Machine Manager, but will not delete their associated file-based resources.\n\nDo you want to continue? |
||
1781 |
To update Virtual Server on the virtual machine host %ObjectList; all virtual machines on the host will be stopped to avoid data loss. The host will be restarted when the upgrade job is complete.\n\nDo you want to continue? |
||
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. |
|
1784 |
The following virtual machine hosts are in host groups that are used for Virtual Machine Self-Service: %HostNames;. Moving these hosts could cause service interruptions for Self-Service users.\n\nDo yo u want to continue? |
||
1785 |
Disabling the undo disks causes a virtual machine to be shut down. To avoid losing any unsaved data, ensure that the virtual machine is shut down before you take an action. You have chosen to disable t he undo disks of the following virtual machines: %ObjectList;.\n\nDo you want to continue? |
||
1786 |
Resetting a virtual machine causes a temporary loss of service to any users of the machine. You have chosen to reset the following virtual machines: %ObjectList;.\n\nDo you want to continue? |