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
11600 A VMware ESX Server host cannot be moved to the root host group. ESX hosts must be in a host group that maps to a Datacenter node in VMware VirtualCenter. The root host group does not map to a Datacenter node.
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.
11602 Unable to move the host cluster %HostClusterName; because it is a VMware VirtualCenter cluster. BLANK
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 and then try the operation again.
11605 To restart the job, run the following command:\n\nPS> Restart-Job -Job (Get-VMMServer %ServerName; | Get-Job | where { $_.ID -eq "%TaskID;"}) BLANK
11606 The VMM component cannot connect to the VMM server because the VMM versions are not compatible. Update the VMM component to the same version as VMM server, and then try the operation again.
11607 The VMM component cannot connect to the VMM server because the VMM versions are not compatible. Update the VMM 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.
11609 The %JobName; job cannot be restarted. This job started before VMM 2008 was upgraded to VMM 2008 R2, and it cannot be restarted.
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, 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 %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, %OperationsManagerServer;. 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 R2 Management Pack has not been imported into System Center Operations Manager 2007. Deploy the VMM 2008 R2 Management Pack in System Center Operations Manager 2007.
11807 Operations Manager discovery failed with error: "%ActualException;". BLANK
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 System Center Operations Manager 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.
11813 A parameter passed to PRO data source is null. N/A
11814 Host cannot be found. N/A
11815 Host virtualization platform is not VMware. N/A
11816 Credentials to connect to host are not available. N/A
11817 An invalid parameter value is passed for performance counters. N/A
11818 Operations Manager discovery succeeded. BLANK
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 R2 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 R2 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 R2 Management Pack on the Operations Manager server. Use the Configure Operations Manager option of VMM Setup to import version %MPVersion; of the System Center Virtual Machine Manager 2008 R2 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 Virtual Machine Manager 2008 R2 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).
11824 PRO tip implementation failed. %DetailedErrorMessage; BLANK
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.
11826 PRO tip implementation did not complete successfully. Ensure that you can connect to the Operations Manager server from the Operations Console, and that the Operations Manager Health Service (HealthService.exe) is running on the Operations Manager root management server.
11827 The Virtual Machine Manager service stopped while PRO tip %TaskID; was being implemented. That might have been caused by a system restart. The PRO tip may still being executed by Operations Manager agent. Make sure the PRO tip execution is completed by Operations Manager agent and if the issue is not resolved, rerun the PRO tip.