Resolving Issue: Cannot List Virtual Machines on Hyper-V Host - Troubleshooting Guide

Troubleshooting: Unable to List VMs on Hyper-V Host

KB ID: 104057
Issue:
The BDRSuite Backup Server is unable to display virtual machines from the added Hyper-V host/Cluster, resulting in an alert.
Possible Causes and Solutions:
Cause 1: Hyper-V Host/Cluster Not Reachable or Network Issues
Solution:
  1. Ensure the Hyper-V cluster/node/host is reachable and powered on.
  2. Verify that the Hyper-V host machine's IP/machine name is pingable from the BDRSuite Backup Server using commands like "ping 192.168.x.x" or telnet utility.
  3. Check if the Hyper-V Virtual Machine Management Service (VMMS) is operational on the host machine and confirm VMs are listed in Hyper-V Manager.
Cause 2: Active Directory Machine Offline
Solution:
  1. Ensure that the Active Directory Domain Server machine is online and accessible.
  2. Confirm that the Hyper-V node is connecting using valid domain credentials.
Cause 3: Incorrect Host Credentials
Solution:
  1. Verify that the credentials saved in the credentials manager are accurate.
  2. If the Hyper-V host/cluster password changes after adding it to the BDRSuite server, update it in the credential manager.
  3. Confirm that the user used to push VIS has administrator privileges.
Cause 4: WMI Services Issues
Solution:
  1. Ensure the "Windows Management Instrumentation Service" is running in services.msc on the Hyper-V host.
  2. Test WMI connectivity between the server and host using the "wbemtest" utility:
    1.  Search for "wbemtest" on the server machine and run it.
    2.  In the namespace text box, enter: \{HostIP}\root\cimv2 [e.g., \192.168.102.34\root\cimv2].
    3.  Enter the username, password, and click "Connect".
    4.  If errors occur, resolve them before pushing the agent.
Cause 5: Cluster Name/IP Change
Solution:
  1. If the cluster name/IP address changes after VIS is pushed to nodes, the BDRSuite database might not update. This can affect VM listing.
Cause 6: Blocked 42005 Port (Used by BDRSuiteIntegrationService)
Solution:
  1. Navigate to Control Panel -> System and Security -> Windows Firewall.
  2. Click "Advanced settings" -> "Inbound Rules".
  3. Check if the "BDRSuiteIntegrationServicePort" rule [42005] is enabled.
    1.  If disabled/blocked, enable it by right-clicking and selecting "Allow the connection".
    2.  If absent, add it manually as described in the steps.
Note: If the VMs still aren't listed after trying the solutions above, contact vembu-support@vembu.com for further assistance.


    • Related Articles

    • Unable to list Disks/Volumes of the host

      KB ID: 103087 Issue: The issue at hand is the inability to list Disks/Volumes of the host in BDRSuite. This can arise due to various reasons: Possible Causes: 1. Communication Issue: The agent might be unable to communicate with the server due to a ...
    • Unable to list Disks/Volumes of the host

      KB ID : 103087 Products : Windows - ImageBackup Possible reasons for the issue "Unable to list Disks/Volumes of the host" include: 1.Communication issue: The agent may not be able to communicate with the server due to a blocked port (Port 32004). ...
    • Unable to Process Guest VMs Due to Outdated Hyper-V Integration Service

      KB ID: 104062 Description: This Knowledge Base article addresses an alert indicating the inability to process guest VMs during Appware enabled Hyper-V backups. The alert is triggered when the Hyper-V Integration service in the guest machine is either ...
    • Configuring Hyper-V VM Replication

      Hyper-V replication allows you to create a copy of virtual machines (VMs) from one Hyper-V host to another, ensuring data redundancy and business continuity. This replication feature provides near real-time protection, enabling quick recovery in case ...
    • Troubleshooting: Vembu Integration Service Not Running During Live Recovery to Hyper-V Host

      KB ID: 115112 Cause: During Live Recovery to a Hyper-V host, the test connectivity might fail with the error "BDRSuite Integration Service is not running on the remote host. Make sure it is running and proceed with the restore." This issue can occur ...