KB ID : 104057
Published : Nov. 30, 2018
Created : Nov. 30, 2018
Last Modified : Aug. 27, 2021

This alert usually throws if the Vembu BDR Backup Server is unable to list the virtual machines from the added Hyper-V host/Cluster.

The possible causes could be as follows:

Cause 1:

Hyper-V Cluster/Node/Host is Not reachable/Down (OR) Network Issues- where unable to ping to hostname, IP from the Vembu BDR Backup Server


  • Ensure whether Hyper-V cluster/node/host is reachable & powered on
  • Make sure the Hyper-V host machine IP/machine name is pinging from the Vembu BDR Backup Server machine (Open the command prompt and execute the command “ping 192.168.x.x” or by using telnet utility)
  • Make sure Hyper-V Virtual Machine Management Service (VMMS) is running in the host machine and check whether VMs listing in Hyper-V Manager

Cause 2:

Active Directory machine goes Down\Offline


  • Make sure Active Directory Domain Server machine is online and accessible
  • Make sure the hyper-v node is connecting with domain credentials

Cause 3:

During invalid host credentials


  • Make sure credentials saved in credentials manager is correct
  • If Hyper-V host/cluster password changed after adding the Hyper-V host, update the same in credential manager in VembuBDR server
  • Make sure the user (used to push VIS) having administrators privilege

Cause 4:

The "WMI services" stopped/ Paused / Disabled in the target host


  • Make sure “Windows Management Instrumentation Service” in services.msc is running in the Hyper-V host
  • Make sure WMI test connectivity between Server and host is working fine. Do WMI test with wbemtest utility by the following steps:

    a) Search for “wbemtest” application in Server Machine and connect it

    b) On the namespace text box enter: \{HostIP}\root\cimv2 [eg - \\root\cimv2]

    c) Enter username, password and click on "Connect".

    d) In case of any error, try pushing the agent after fixing the error.

  • If test connectivity failed, resolve the windows error and try to list the VMs again

Cause 5:

If the Cluster Name/IP address is changed


Since cluster name/IP address got changed after VIS pushed to nodes, could not update the same in VembuBDR database.

Cause 6:

When the 42005 port which is used by VembuIntegrationService (VIS) is blocked in the target host.


For this navigate to Control Panel in the host -> select System and Security feature -> select Windows Firewall in it:

  • Click Advanced settings option -> and select the Inbound Rules
  • Check VembuIntegrationServicePort rule is enabled or not [42005]

a) If it is disabled/blocked then enable the port connection by following the below steps:

  • Right-click on VembuIntegrationServicePort and choose Properties and select "Allow the connection"

b) If there is no 42005 port then add it manually in the firewall by following the steps below:

  • Click on New Rule to add a new one -> select Port and click 'Next'
  • Choose the TCP port -> and select Specific local ports option and enter “42005” and click 'Next'
  • Select Allow the connection and click 'Next'
  • Select the checkboxes to apply rules as Domain, Private and Public then click 'Next'
  • Enter the name as “VembuIntegrationService.exe” and click 'Finish' to add this rule to the firewall
  • Go to Inbound Rules again to check whether the new rule is added to the firewall or not.

Using any one of the solutions mentioned above the VMs of the added Hyper-V host will be listed.

If the VMs are not listed even after following the solutions given above then drop a mail to vembu-support@vembu.com our support team will assist you.

edit retag flag offensive close merge delete