System Center 2012 – Virtual Machine Manager (VMM) Error Codes [25000-25999]

25101

Adding the specified host groups to the MAC address pool (%Name;) would result in overlapping network-settings-accessible host groups.

Specify non-overlapping host groups or update the inherit network settings property.

25103

Adding the specified host groups to the network site (%Name;) would result in overlapping network-settings-accessible host groups.

Specify non-overlapping host groups or update the inherit network settings property.

25105

The VLAN ID (%VlanId;) is not valid because the logical network (%LogicalNetworkName;) does not include the VLAN ID in a network site accessible by the host.

Either specify a valid VLAN ID, or don't specify a VLAN ID and a valid one will be assigned automatically.

25107

The address range of the pool (%Name;) could not be updated because the requested range would not contain the currently allocated address (%Address;). There may be other allocated addresses not contained in the updated range.\nRequested range start: %RangeStart;\nRequested range end: %RangeEnd;

Please ensure that the updated address range contains all currently allocated addresses.

25109

The cmdlet New-SCSubnetVLan was called without specifying either a subnet or a VL AN ID.

Please specify either a subnet, a VLAN ID, or both, and then try again.

25111

(%Name;) is not a valid virtual IP address (VIP) member name.

VIP names must start with a letter, must contain only alphanumeric characters, hyphens (-), periods (.), or underscores (_), cannot be empty or contain spaces, and must not exceed 127 characters.

25113

VMM is unable to delete the virtual IP address (%VIPName;) because the service (% ServiceName;) depends on it.

Please remove the services that depend on the virtual IP address.

25115

The logical network (%LogicalNetworkName;) could not be found.

Network tags and network locations are obsolete in this version of V MM. Use a logical network to identify the desired network instead.

25117

The load balancer (%LoadBalancerName;) cannot be modified.

BLANK

25119

The specified load balancer configuration provider (%ProviderName;) cannot be use d to set a load balancer.

Use a different load balancer configuration provider.

25121

The load balancer (%LoadBalancerName;) cannot be refreshed.

BLANK

25123

The requested reserved range contains an already allocated address (%Address;). The reserved address range for the pool cannot contain already allocated addresses. There may be other allocated addresses in the requested reserved range.

Release the allocated address in the requested reserved range back to the pool, and then try again.

25125

The allocated virtual IP address (%Address;) is not contained in the virtual IP address range. The reserved virtual IP address range should contain all currently allocated virtual IP addresses. There may be other allocated virtual IP addresses outside of this range.

Make sure the updated reserved virtual IP address range contains all currently allocated virtual IP addresses, or release all allocated virtual IP addresses that are not contained in the updated range.

25127

The virtual machine related to the virtual IP address member (%Name;) does not exist in VMM. VMM is unable to add a virtual IP address member if the virtual IP address member's virtual machine does not exist.

Add the virtual IP address member's virtual machine to VMM and try t he operation again.

25129

At least one virtual IP address member must be specified to create a virtual IP address using Microsoft Network Load Balancing.

Specify at least one virtual IP address member on the virtual IP address and try the operation again

25131

Ignoring the VLAN ID (%VlanId;) that corresponds to an IPv6 address pool because it conflicts with a VLAN ID that corresponds to an IPv4 address pool.

Configure both the IPv4 and IPv6 address pool subnets to correspond to the same VLAN ID.

25133

Selected Virtual Network Switch (%VirtualNetworkName;) is not available as a highly available clustered virtual network combination.

Please choose different highly available virtual network or if possible another one would be automatically chosen for you.

25300

Cluster validation failed because of error: %DetailedErrorMessage;.

Refer cluster documentation to resolve the issue.

25302

Failed to create the process to execute the task. Error %DetailedErrorMessage;.

Check if the user has permission on the VMM server and retry the operation.

25304

Unable to execute the task because of error %DetailedErrorMessage;.

Check if the user has permission on the VMM server and retry the operation.

25306

Unable to execute the task because of error %DetailedErrorMessage;.

Ensure VMM server has sufficient resources and retry the operation.

25308

The requested operation is supported only on VMM server installed on Windows Server 2008 R2 and above.

Try the operation on Windows Server 2008 R2 and above.

25310

Unable to connect to the user host process.

retry the operation.

25312

Unable to execute the task because of error %DetailedErrorMessage;.

Check if the user has permission on the VMM server and retry the operation.

25314

The hosts specified belong to more than one cluster.

Please select zero or more hosts from a single cluster and zero or more nodes that are not part of any cluster for validation.

25316

The cluster operation requires one or more hosts.

Select one or more host and retry the operation.

25318

Hosts selected cannot be clustered because they are running different versions of Windows.

Select one or more hosts which run the same version of Windows serve r and retry the operation.

25320

Hosts selected cannot be clustered because one or more of the hosts belong to another cluster.

Select one or more host that are not part of the cluster and retry t he operation.

25322

Cluster validation reported that the nodes do not meet clustering requirements. R efer %FileName; in %%windir%%\Cluster\Reports of any node for further information on the failure.

Refer to the cluster documentation for fixing the issue reported in the error file and retry the operation.

25324

Parameters specified for the install cluster are not valid.

Please specify valid parameters.

25326

Hosts selected cannot be clustered because they are running different SKUs of Windows OS.

Select one or more hosts that are running same SKUs and retry the operation.

25328

Hosts selected cannot be clustered because installation of cluster feature on %VM HostName; failed with error %DetailedErrorMessage;.

Refer to Windows documentation for how to fix installation issues.

25330

Uninstallation of cluster %HostClusterName; failed because of error %DetailedErrorMessage;.

Please refer to cluster documentation for resolving cluster problems.

25333

Removing host %VMHostName; from the cluster %HostClusterName; failed because of e rror %DetailedErrorMessage;.

Please refer to cluster documentation for resolving cluster problems.

25335

The host %VMHostName; does not belong to a cluster.

Please specify a host that belongs to a cluster.

25337

The hosts cannot be removed because host %VMHostName; is not in maintenance mode.

Please set the host in Maintenance mode and retry the operation.

25339

The cluster configuration requires a quorum resource to function properly.

Please specify valid parameters.

25341

The VMM Task Helper process terminated unexpectedly due to error %DetailedErrorMe ssage;.

Contact your support personnel for further help.

25343

No network adapter found on host %VMHostName; that matches cluster virtual networ k %VirtualNetworkName;.

Please add a network adapter to the host and set the Logical Network s on the adapter to match the cluster network.

25345

Cannot convert the last host cluster network into a virtual network without host access.

Please ensure there are other host cluster networks before removing this network from hosts.

25347

No clusterable networks found for the hosts.

Ensure at least one common network exists amongst hosts, and retry the operation.

25349

The unmanaged Storage Logical Unit %SMLunID;, which is presented to cluster alrea dy, is not accessible to host %VMHostName;.

Please ensure that new nodes have access to non-VMM managed cluster disks before adding the node to cluster. Present the storage disk to the new hosts and refresh host, before retrying the operation.

25351

Enable Cluster Shared Volume on the cluster failed.

Please refer to the cluster documentation to resolve the problem and retry the operation.

25353

Cluster validation report is located at %FileName;

25501

Error while storing the certificate.

Ensure that the SQL Server database for the VMM management server is functioning correctly.

25503

The certificate returned by VMM agent is not in the expected format.

Ensure that VMM agent is of the right version and installed properly .

25505

The cluster replication of VMM certificate failed.

Please ensure user has permission on the cluster.

25507

Uninstall of VMM service failed because HA-VMM is running on this host and there are other failover nodes exists for HAVMM.

Please move the HA-VMM resource group to another failover node and t hen retry the uninstallation.

25509

Quorum Disk specified for the cluster is not found on the cluster.

Check that the disk is clustered disk and is in available storage an d retry the operation.

25511

Parameters for NodeMajority and DiskQuorum cannot be specified together.

Specify either NodeMajority or DiskQuorum.

25513

Cluster disk resource name %Name; is in failure state

Fix the failed clustered disk resource

25515

Cluster disk %Name; is not a Cluster Shared Volume

Specify a Cluster Shared Volume and retry the operation

25517

%Name; cannot be managed by Virtual Machine Manager, as managing a host cluster i n which the HA-VMM is running on is not supported.

Managing a host cluster which the HA-VMM is running on is not supported

25519

Removing host %VMHostName; from the cluster %HostClusterName; failed because of e rror %DetailedErrorMessage;.

If this is a newly created cluster, please try again later after the DNS name has been updated, else refer to cluster documentation for resolving cluster problems.

25900

Operations Manager Action Account and Credentials for Operations Manager cannot be specified together

Specify either to use action account or a specific credential, and t hen try the operation again.

25902

One of the following should be provided - Default Action account or a specific credential

Specify at least one of the following - default action account or a specific credential, and then try the operation again.

25904

A connection already exists

Remove the existing connection, and then try the operation again

25906

A generic error has occurred during management pack import

Try the operation again

25908

Operations Manager connection is not configured.

Configure Operations Manager connection and try operation again

25911

The credentials provided do not have the necessary permissions to configure the server.

Provide the credentials for an Administrator on the server

25913

Not able to configure the remote management server %ComputerName; for implementing PRO Tip.

Provide the credentials that is an Administrator on the server

25915

VMM Management group object cannot be found.

Update Operations Manager connection and then try operation again.

25917

Virtual Machine Manager was not able to retrieve PRO tips from Operations Manager . Management pack class was not found.

Ensure that Virtual Machine Manager management pack is installed on the Operations Manager server.

25919

PRO Diagnostic error event

N/A

25921

Failed to create diagnostics PRO tip

Check if Operations Manager Agent is running on the computer running VMM management server and that it is monitored.

25923

PRO Diagnostics Target is not monitored.

Check if Operations Manager Agent is running on the computer running VMM management server and that it is monitored.

25925

The management pack "%Name;" containing the monitor is not sealed.

Seal the management pack and import it in Operations Manager and try the operation again.

25927

PRO is not enabled for the current Operations Manager connection.

Run Set-SCOpsMgrConnection to enable PRO and try the operation again.

25929

The specified PROMonitor "%Name;" does not target the given target type.

Check the PROMonitor or the target and then try operation again.

25931

Computer %ComputerName; is not managed by Operations Manager.

To enable VMM service monitoring install Operations Manager agent on all VMM cluster nodes and turn agent proxying on.

25933

Remote Session was not created.

N/A

25935

There is no monitor configuration set on the parent object to inherit PRO setting s.

Manually set the MonitoringEnabled and AutomaticMode

25937

Inherit parameter cannot be set on the root host group.

Specify a different scope and try the operation again

25939

Failed to restart VMMAgent service on computer %ComputerName;.

Manually restart the VMMAgent service.