System Center 2012 – Virtual Machine Manager (VMM) Error Codes [11000-11999]

System Center 2012 – Virtual Machine Manager (VMM) Error Codes [11000-11999]

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

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 try the operation again.

11001

The number of network adapters 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 network adapters on the virtual machine and then try the operation again.

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 tr y 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.

Select a different host or reduce the number of processors on the vi rtual machine to %MaxLimit; or fewer. Try the operation again.

11006

The virtual machine %VMName; is configured as highly available but the selected h ost is not a highly available host.

Select a highly available host for the virtual machine and then try the operation again.

11007

Host cluster %HostClusterName; is overcommitted.

Select a different highly available host and then try the operation again.

11008

This configuration causes the host cluster %HostClusterName; to become overcommit ted.

Select a different highly available host and then try the operation again.

11009

The number of LUNs requested on the virtual machine %VMName; (%Count;) exceeds the number of LUNs available on the host (%MaxLimit;).

Select a different host or reduce the number of LUNs on the virtual machine, and then try the operation again.

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.

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. The placement weight for availability on this host must be set to less than most important to allow deployment to upgrade availability.

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.

Select a different host and then try the operation again.

11015

You have selected a non-clustered host for placing a highly available virtual machine. Highly available virtual machines cannot be placed on a non-clustered host.\n\nDo you want to continue and make t his virtual machine non-highly available?

11016

You have selected a clustered host for placing a virtual machine that is not currently highly available.\n\nDo you want to make this virtual machine highly available?

11017

The number of legacy network adapters (%Count;) requested on the virtual machine (%VMName;) exceeds the maximum number of legacy network adapters that the host virtualization software supports.\nMaximum number of legacy adapters: (%MaxLimit;).

Select a different host or reduce the number of legacy network adapters on the virtual machine and then try the operation again.

11018

All of the volumes on %VMHostName; are marked as not available for placement.

Select a different host or add more storage and then try the operation again.

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 and then try the operation again.

11020

Virtualization platform on host %VMHostName; doesn't allow boot and system volume s to be on a disk attached to SCSI adapter. Disk at the location (%BusType;, %Bus;, %Lun;) must be attached to the IDE bus for the machine to boot up and work properly.

Modify the bus assignments so that boot and system volume disks are located on IDE bus, and then try the operation again.

11021

Virtualization platform on host %VMHostName; doesn't support pass-through disks.

Remove pass-through 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 try the operation again.

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 try the operation again.

11026

Host %VMHostName; is not responding and is not available for placement.

Select a different host and then try the 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.

Select a different host and then try the operation again.

11028

Virtualization platform on host %VMHostName; does not support shared DVD ISO images.

Remove the shared ISO image from hardware profile or select a differ ent 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 SCS I adapter.

Modify the bus assignments so that boot and system volume disks are 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 the host to enable full management functionality.

Configure the security settings of host %VMHostName; to enable full management functionality and then try the operation again.

11031

Virtual machine %VMName; cannot be deployed 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 deployed 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.

11032

The virtual machine (%VMName;) cannot be placed on the Hyper-V host (%VMHostName; ) because it has checkpoints that are in a format that is incompatible with the Hyper-V virtualization platform.

Select a different host and then try the 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 %V MHostName; is not connected.

Ensure that the network adapter is enabled and connected, and then try the operation again.

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.

11036

Virtual machine %VMName; cannot be placed on host %VMHostName; because the host i s 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.

11037

There currently are no network adapters with network optimization available on host %VMHostName;.

11038

The virtualization host (%VMHostName;) is in maintenance mode. Hosts in maintenance mode are not available for placement.

Please select a different host and then try the operation again.

11039

VMM cannot determine the processor family for the virtualization host (%VMHostName;) or one of its snapshots. The virtual machine (%VMName;) may not start or operate correctly on the host.

To select the most suitable host for virtual machine %VMName;, use the Migrate or Clone Virtual Machine Wizard. The wizard rates all available hosts based on their suitability for this vi rtual machine.

11040

VMM cannot determine the processor family for virtual machine %VMName;. The virtu al machine may not start or operate correctly on server %VMHostName;.

To select the most suitable host for virtual machine %VMName;, use the Migrate or Clone Virtual Machine Wizard. The wizard rates all available hosts based on their suitability for this vi rtual machine.

11041

VMM cannot find suitable hosts for all virtual machines in the service. The virtu al machines returned the following error list: %DetailedErrorMessage;

Select a more suitable computer folder for the service instance, or change the virtual machine requirements for the service and attempt deployment again.

11042

VMM could not reserve the resources needed for this operation.

Attempt the operation again.

11043

VMM could not retrieve the reservations made by activities that share resources.

Attempt the operation again.

11044

VMM failed to generate a globally unique name for computers with the name pattern . Name pattern: %ComputerName;

Change the computer name and attempt the operation again.

11045

VMM failed to find the service associated with the computer.\nComputer name; %ComputerName;

Ensure that the computer is in a valid state and attempt the operation again.

11046

The number of network adapters (%Count;) requested on the virtual machine (%VMName;) exceeds the maximum number of network adapters that the host virtualization software supports.\nMaximum number of adapters: (%MaxLimit;).

Select a different host or reduce the number of network adapters on the virtual machine and then try the operation again.

11047

The virtual machine %VMName; or one of its checkpoints is configured to use dynam ic memory allocation. However, the target host does not support dynamic memory allocation.

Either change the memory allocation setting for the virtual machine to static or place the virtual machine on a host that is running Windows Server 2008 R2 with Service Pack 1 or later.

11048

To migrate the virtual machine, the host must have a compatible graphics processing unit (GPU) with adapter ID: %GPUID;.

For a Hyper-V virtual machine, either configure the video adapter setting on the virtual machine to use the standard video adapter or place the virtual machine on a host with a compatible GPU.

Command Line Interface: For a Hyper-V virtual machine, either disable the Microsoft RemoteFX 3D video adapter or place the virtual machine on a host with a compatible GPU.

11049

There are insufficient video memory resources on the host. The minimum amount of memory required is %MemorySize; MB in a Microsoft RemoteFX-compatible graphics processing unit (GPU).

For a Hyper-V virtual machine, either modify the settings for the Re moteFX 3D video adapter to support fewer monitors or a lower maximum monitor resolution, or place the virtual machine o n a host with enough video memory resources.

11050

To configure Microsoft RemoteFX 3D video adapter settings, the host CPU must supp ort Second-Level Address Translation (SLAT).

For a Hyper-V virtual machine, either configure the video adapter setting on the virtual machine to use the standard video adapter or place the virtual machine on a host with a CPU that supports SLAT.

Command Line Interface: For a Hyper-V virtual machine, either disable the RemoteFX 3D video adapter or place the virtual machine on a host with a CPU that supports SLAT.

11051

To configure Microsoft RemoteFX 3D video adapter settings, the host must have at least one RemoteFX-compatible graphics processing unit (GPU).

For a Hyper-V virtual machine, either configure the video adapter setting on the virtual machine to use the standard video adapter or place the virtual machine on a host with a RemoteFX-compatible GPU.

Command Line Interface: For a Hyper-V virtual machine, either disable the RemoteFX 3D video adapter or place the virtual machine on a host with a RemoteFX-compatible GPU.

11052

To migrate the virtual machine, the host must have a compatible graphics processing unit (GPU) with adapter ID: %GPUID;.

For a Hyper-V virtual machine, either configure the video adapter setting on the virtual machine to use the standard video adapter or place the virtual machine on a host with a compatible GPU.

Command Line Interface: For a Hyper-V virtual machine, either disable the Microsoft RemoteFX 3D video adapter or place the virtual machine on a host with a compatible GPU.

11053

There are insufficient video memory resources on the host. The minimum amount of GPU memory required is %PlacementRequestValue; MB and the maximum space after considering the virtual machine requirements was %PlacementCapacityValue; MB at the time of evaluation.

For a Hyper-V virtual machine, either modify the settings for the RemoteFX 3D video adapter to support fewer monitors or a lower maximum monitor resolution, or place the virtual machine o n a host with enough video memory resources.

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 then try the operation again.

Command Line Interface: Specify a different user role name and then try the operation again.

11401

%UserName; is already a member of user role %FriendlyName;.

11402

Cannot remove member %UserName; because %UserName; is not a member of the specified user role.

Specify a different user role and then try the operation again.

11403

The -AddScope parameter cannot be used for Host Groups with an Administrator profile.

BLANK

11404

The -AddScope parameter for the LibraryShare object cannot be used with Set-VMMUserRole with an Administrator profile.

BLANK

11405

The -AddScope parameter with a Template object cannot be used for Set-VMMUserRole with an Administrator profile.

BLANK

11406

The -VMPermission parameter cannot be used for Set-VMMUserRole with an Administrator or Delegated Administrator profile.

BLANK

11407

The -QuotaPoint parameter cannot be used for Set-VMMUserRole with an Administrator or Delegated Administrator profile.

BLANK

11408

The -RemoveQuotaPoint parameter cannot be used for Set-VMMUserRole with an Administrator or Delegated Administrator profile.

BLANK

11409

The -QuotaPerUser parameter cannot be used for Set-VMMUserRole with an Administrator or Delegated Administrator profile.

BLANK

11410

The user role no longer exists.

Close and reopen the VMM console, and then try the operation again.

Command Line Interface: Close and reopen Windows PowerShell, and then try the operation again.

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.

Command Line Interface: You can add or remove members to the Administrator user role, or del egate administration, by creating new Delegated Administrator user roles.

11412

The -LibrarySharePath parameter cannot be used for Set-VMMUserRole with an Administrator or Delegated Administrator profile.

BLANK

11413

A Virtual Machine Manager administrator cannot be added to user role %FriendlyNam e;.

BLANK

11414

The Administrator user role cannot be deleted.

BLANK

11415

The -ParentUserRole parameter is required for Set-SCUserRole with a Delegated Administrator or Cloud Manager profile.

Select the ParentUserRole parameter for the new user role

Command Line Interface: Select the ParentUserRole parameter for the new user role and then try the operation again.

11416

The -ParentUserRole specified must be an Administrator, Delegated Administrator, or Cloud Manager user role.

Select UserRole for the Administrator, DelegatedAdmin, or CloudManag er profile as the ParentUserRole and then try the operation again.

Command Line Interface: Select UserRole for the Administrator, DelegatedAdmin, or CloudManager profile as the ParentUserRole and then try the operation again.

11417

Administrator permission is required to perform this operation.

BLANK

11418

You do not have permission to access one or more of the objects required by this operation.

Contact the Virtual Machine Manager administrator to obtain the appropriate permissions.

11419

You do not have permission to modify this user role.

Contact the Virtual Machine Manager administrator to obtain the appropriate permissions.

11420

A connection cannot be established with the specified virtual machine.

Contact the Virtual Machine Manager 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 typ es of objects can be used: Template, HostGroup, or LibraryShare.

11423

The name of the Administrator user role cannot be changed.

BLANK

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.

Command Line Interface: Valid values for the user profile are: Administrator, DelegatedAdmin or SelfServiceUser.

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 virt ual machine associated with a user role that you are a member of.

11427

The ownership for this object cannot be changed because the new owner is not a member of a user role that has access to this object.

Either change the new owner to a user who has access to this object, or contact your Virtual Machine Manager administrator to request access for the user who you want to own this object, and then try the operation again.

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.

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

Command Line Interface: Add %UserName; as a member of the specified user role or provide a d ifferent 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.

Add %UserName; as a member of the user role and try again or provide a different user role or a different owner.

Command Line Interface: 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 object because no owner has been set for this object.

Attempt to set the user role again, additionally providing an owner who is a member of the user role.

Command Line Interface: 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.

Command Line Interface: 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.

Contact your Virtual Machine Manager administrator to associate this virtual machine to a Self-Service user role of which you are a member.

Command Line Interface: Contact the Virtual Machine Manager administrator and have this virtual machine associated with a 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 try the operation again.

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 management server could not validate user %UserName;.

Contact your Virtual Machine Manager administrator to verify that there is a two-way trust relationship between the user domain and the domain of the Virtual Machine Manager management server.

Command Line Interface: Ensure that there is a two-way trust relationship between the domain of the VMM management server and the user's domain

11437

The Virtual Machine Manager management server could not copy a required Hyper-V a uthorization file to %ServerName;.

Contact your Virtual Machine Manager administrator to verify that %S erverName; is running and connected to the network.

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 t he 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 paren t user role and then try the operation again.

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 restarting the browser. This can also occur if the Web server has been reset.

Log on to the Self-Service Portal again. If this problem occurs freq uently, contact your administrator.

11441

The connection to the Virtual Machine Manager management server for this session has been lost. The management 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 cause d by changing the current internet zone for the Self-Service Portal without restarting the browser or by directly brows ing 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, co ntact your administrator.

11443

Cannot attach the specified ISO image to the virtual machine because user role (% UserRoleName;) associated with the virtual machine does not have access to the ISO image.

Contact your VMM administrator to add the library share path for the ISO image to the user role (%UserRoleName;), or specify a different ISO image and then try the operation again.

11444

Unable to add a member (%UserName;) to the user role (%UserRoleName;). Only domain user accounts, security groups, or computers can be user role members.

Select a valid user role member and try the operation again.

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 mad e available for placement.

11446

Virtual Machine Manager could not place this virtual machine on host %VMHostName; because there are no default virtual machine paths on this host.

Contact your VMM administrator to request default virtual machine pa ths on this host or access to another host.

11447

Virtual Machine Manager could not place this virtual machine on host %VMHostName; because the host does not have any default virtual machine paths on volumes that are available for placement.

Contact your VMM administrator to request at least one default virtu al 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 sufficient rights.

Create a virtual machine from a user role which has sufficient right s, or contact your administrator be granted the necessary rights.

11449

Virtual Machine Manager could not place this virtual machine on the virtualizatio n host (%VMHostName;) because remote connections are not enabled on the host.

Contact your VMM administrator to enable remote connections on this host or request access to another host.

11450

A required parameter, -SelfServiceRole, is not specified.

Specify the -SelfServiceRole parameter and then try the operation ag ain.

11451

Cannot create this virtual machine because no product key was provided.

Enter a valid product key and try again.

11452

VMM cannot store this virtual machine because the private cloud (%CloudName;) has no writable library path.

Your administrator must set a writable library path for the private cloud (%CloudName;).

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 o peration 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 VirtualCen ter 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 Virtu alCenter server %ServerName; is not empty.

Remove all hosts from the host cluster and then try the operation ag ain.

11605

To restart the job, run the following command:\n\nPS> Restart-Job -Job (Get-VM MServer %ServerName; | Get-Job | where { $_.ID -eq "%TaskID;"})

11606

This VMM feature cannot connect to the VMM management server because the VMM versions are not compatible.

Update this VMM feature to the same version as VMM management server , and then try the operation again.

11607

This VMM feature cannot connect to the VMM management server because the VMM versions are not compatible.

Update the VMM management 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.

Command Line Interface: 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 pr ogress.

Do not attempt to dismiss a PRO tip that has %PROTipState; status.

Command Line Interface: 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.

Command Line Interface: 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 is installed, and then try the operation again. Use Remove-SCOpsMgrConnection -Force if you are trying to remove th e connection to that server.

Command Line Interface: Ensure that the server exists and that System Center Operations Mana ger is installed and then try the operation again. Use Remove-SCOpsMgrConnection -Force if you are trying to remove the connection to that server.

11804

The Virtual Machine Manager service does not have required credentials to access the Operations Manager SDK service on %OperationsManagerServer;.

Ensure that the RunAs account credentials or the VMM service account used to connect to Operations Manager server have necessary administrative privileges on the Operations Manager server .

Command Line Interface: Ensure that the RunAs account credentials or the VMM service account used to connect to Operations Manager server have necessary administrative privileges on the Operations Manager server .

11805

Unable to verify the connection to the Operations Manager root server, %OperationsManagerServer;.

Ensure that the server exists, that System Center Operations Manager is installed and running successfully on the server, and that Virtual Machine Manager has the appropriate rights to perform this action. Use Remove-SCOpsMgrConnection -Force if you are trying to remove the connection to that server.

Command Line Interface: Ensure that the server exists, that System Center Operations Manager is installed and running successfully, and that Virtual Machine Manager has the appropriate rights to perform this act ion, and then try the operation again. Use Remove-SCOpsMgrConnection -Force if you are trying to remove the connection to that server.

11806

Discovery of PRO performance and usage data was terminated because the VMM 2008 R 2 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.

Command Line Interface: Ensure that VMM 2008 R2 Management Pack is imported on the Operation s Manager Server and then try the operation again.

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 management server.

Install the Operations Console for System Center Operations Manager 2007 on the Virtual Machine Manager management server and then try the operation again.

11810

Unable to set %PROParameter; to the given value.

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.

Command Line Interface: Review knowledge for the PRO tip for recommended actions to resolve the issue.

11812

Cannot update PRO settings because the cmdlet includes invalid parameters.

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.

11820

Cannot update PRO settings until the Operations Manager root server connection is configured.

Configure the Operations Manager root server connection using Set-VM MServer -OpsMgrServer.

11821

Management pack %MPName; version %MPVersion; was not found.

Use Repair-SCOpsMgrConnection cmdlet to import version %MPVersion; o f the %MPName; management pack onto your Operations Manager server, and then retry the operation.

11822

Management pack %MPName; version %MPIncompatibleVersion; is incompatible with this version of Virtual Machine Manager

Use Repair-SCOpsMgrConnection cmdlet to import version %MPVersion; o f the %MPName; management pack onto your Operations Manager server, and then retry the operation.

11823

One or more of the Virtual Machine Manager objects monitored by Operations Manage r could not be discovered. This might be caused by a missing or outdated version of the System Center Virtual Machine Manager management pack in Operations Manager.

Import the correct version (%MPVersion;) of the management pack into Operations Manager. The management pack is most likely located in the ManagementPacks subfolder in the Virtual Machine Manager installation folder.

11824

PRO tip implementation failed. %DetailedErrorMessage;

See PRO tip for further troubleshooting

Command Line Interface: See PRO tip for further troubleshooting

11825

PRO tip implementation failed to start.

Ensure that PowerShell remoting is enabled on Virtual Machine Manage r 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 th e Operations Console, and that the Operations Manager Health Service (HealthService.exe) is running on the Operations M anager 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. Ma ke sure the PRO tip execution is completed by Operations Manager agent and if the issue is not resolved, rerun the PRO tip.

11828

Unable to inherit network configuration for the root host group.

Do not configure the root host group to inherit network configuratio n.

Leave a Comment
  • Please add 5 and 3 and type the answer here:
  • Post
Wiki - Revision Comment List(Revision Comment)
Sort by: Published Date | Most Recent | Most Useful
Comments
Page 1 of 1 (2 items)
Wikis - Comment List
Sort by: Published Date | Most Recent | Most Useful
Posting comments is temporarily disabled until 10:00am PST on Saturday, December 14th. Thank you for your patience.
Comments
Page 1 of 1 (2 items)