Troubleshooting: Vembu Integration Service Not Running During Live Recovery to Hyper-V Host

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 due to the following reasons:
1. BDRSuite Integration Service is disabled or stopped on the target host.
2. The port [42005] used by BDRSuite Integration Service is blocked in the Windows firewall.
Solution:
To resolve this error, follow the steps below:
Cause 1: BDRSuite Integration Service Not Running
1. Check whether BDRSuite Integration Service is running on the target host:
  1. Press 'Win + R' and type `services.msc`.
  2. Look for 'VembuIntegrationService' in the list.
  3. If the service is stopped, start it manually.
  4. If the service is disabled, set the startup type from disabled to automatic.
Cause 2: Port [42005] Blocked
1. Check if port 42005 used by BDRsuite Integration Service is blocked:
  1. Open Control Panel → System and Security → Windows Firewall.
  2. Click on "Advanced settings" and navigate to Inbound rules.
  3. Check if there is a rule for the VIS agent port [42005].
  4. If the rule is in a blocked state, allow the connection by:
    1. Right-clicking and choosing "Properties."
    2. Selecting "Allow the connection."
2. If no 42005 port rule exists:
Add it manually by clicking "Add new rule" → selecting "Port" → choosing TCP port and entering "42005."
  1. Allow the connection, apply the rule to Domain, private, and public, and name it "VembuIntegrationService.exe."
3. Check Inbound rules again to verify that the new rule is added to the firewall.