Virtual Machine management options grayed out due to third-party software locks in vCenter
search cancel

Virtual Machine management options grayed out due to third-party software locks in vCenter

book

Article ID: 316570

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSphere ESXi VMware Cloud Foundation

Issue/Introduction

  • The "Migrate" and "Power Off/On" options may be unavailable (grayed out) in the vCenter Server for a virtual machine (VM). This typically occurs when a VM is locked by third-party software (such as disaster recovery, backup, or replication solutions). The vCenter Server database contains orphaned records in the VPX_DISABLED_METHODS table that persist, restricting VM management functions.


  • A migration initiated in vCenter failed with the error: "Cannot relocate VM_Name because the action is disabled in vCenter"

Environment

VMware vCenter Server 8.x

VMware vCenter Server 9.x

Cause

  • Virtual Machine is locked by 3rd party software (such as disaster recovery, backup, or replication software).

  • The vCenter Server database contains orphaned records in the VPX_DISABLED_METHODS table. vCenter uses this table to restrict VM operations during active tasks (e.g., backups). If a task fails or does not complete gracefully, these restrictive entries persist and lock the VM management functions. This list of specific vSphere operations that are currently disabled can be found in vSphere UI under Virtual Machine > Configure > Disabled Methods.

Resolution

Identify Locked Methods:
You can identify specific vSphere operations currently disabled in the vSphere UI:

  1. Navigate to Virtual Machine > Configure > Disabled Methods.
  2. Review the Source and Reason columns to determine if tasks are active. If tasks are ongoing, do not proceed with the steps below.

 


    

Option 1: Using the vSphere Client (vCenter 8.0 Update 3 and later)

  1. Navigate to Virtual Machine > Configure > Disabled Methods.
  2. Click the Enable option located below the Disabled Methods list to clear the restrictions:

 

Option 2: Manually remove entries via vCenter MOB

Note: The MOB is deactivated by default in VCF 9.0+. Refer to The MOB is disabled to enable it.

  1. Identify the VM MOB ID:
    • Select the VM in the vSphere Client.
    • In the URL bar, locate the object ID.

      Example:

      https://ExamplevCenterFQDNorIP/ui/#?extensionId=vsphere.core.vm.summary&objectId=urn:vmomi:VirtualMachine:vm-141:########-####-####-####-############&navigator=vsphere.core.viTree.hostsAndClustersView

      In this example VM's MOB ID is vm-141.

  2. Access Virtual Machine Operations:
    • From browser, enter the vCenter MOB by directing to the following URL:
      https://<vcenter IP or FQDN>/mob/?moid=AuthorizationManager&method=enableMethods
  3. Login: Use [email protected] or an equivalent SSO administrator account.
    The following page should load:
  4. Invoke Method:
      • In the first parameter box entity (required), enter the VM's MOB ID (e.g., vm-141).
        For example:
        <!-- array start -->
        <entity type="ManagedEntity"xsi:type="ManagedObjectReference">vm-141</entity>
        <!-- array end --> 


      • In the second parameter box method(required), enter:
        <method>RelocateVM_Task</method>
      • Click on Invoke Method

                     

5. Refresh the vCenter Server web client and the migration option for the VM should now be available.


If you are unable to clear the stale entry, open a case with Broadcom Support and mention this article. See Contact Broadcom support