1. Network issue during agent installation on the target host.

2. Insufficient drive space on the target host.

3. Another MSI (Microsoft Installer) process running on the target host.

4. Denied access to Windows Management Instrumentation (WMI) services on the target machine.

5. Registry editing has been disabled using Local Group Policy on the target host.

6. Installation privilege is blocked using Local Group Policy on the target host.

7. Installation failure of Microsoft Visual C++ Redistributable packages.

8. BDRSuite does not support backup for outdated Operating Systems (OS).

9. Improper removal of previously uninstalled VIS/BBA agent entry on the target machine.

Cause 1: Network issue during agent installation on the target host

Reason 1: The target host is rebooted or shut down during agent installation.

Reason 2: Network issues between the server and the target machine.

Ensure that the agent installation is not disrupted by network issues. If previous installation failed, follow these steps:

1. Check for the registry entry 'VembuIntegrationService' and remove or rename if present.

2. Remove 'VembuIntegrationService' (up to v52) or 'BDRSuite Delegation Service' (from v53) entry from 'Services.msc'.

3. Delete 'Vembu' and 'VembuIntegrationService' folders in the Windows directory.

Cause 2: Insufficient drive space on the target host

Ensure the OS drive of the target machine has at least 2GB of free storage space.

Cause 3: Another MSI process running on the target host

Agent installation to the target host is done using MSI. If another MSI installation is in progress in the target machine, then Windows itself will restrict simultaneous installation.

You can confirm this by performing the following steps:

Step 1: Open Task Manager in your target Windows machine

Step 2: Click ‘More details’ which is present at the bottom left corner of the task manager console.

Step 3: Switch over to the ‘Details’ tab.

Step 4: Under this tab search for ‘msiexec.exe’ under the name column.

Step 5: If such a name exists, it indicates that another MSI installation is in progress.

In such a case, you can wait until the MSI installation gets over and then try adding the host from the BDR Backup Server\Vembu BDR Client.

Cause 4: Denied access to WMI services on the target machine

Case 1: Add a rule in the Windows Firewall to allow Windows Management Instrumentation function.

Step 1: Navigate to the Control Panel

Step 2: Click on System and Security → Windows Firewall → Advanced setting

Step 3: In the Windows Firewall with advanced settings, click on Inbound Rules

Step 4: Inbound Rules → click New Rule and proceed to opt for the Predefined option

Step 5: In the predefined dropdown → select the “Windows Management Instrumentation“ rule and proceed with the default option to enable it and click 'Finish'.    

Case 2: Ensure Windows Management Instrumentation service is running. Start or enable it if needed.

Step 1: Open 'Run' and type ‘services.msc’

Step 2: Navigate to "Windows Management Instrumentation" (WMI) service

Step 3: Check the status of the WMI service

→ If the service is stopped then right-click on the Windows Management Instrumentation service and click Properties. Change the service status by clicking the Start button.

→ If the service is disabled then right-click on the Windows Management Instrumentation service and click Properties. Change the startup type to Automatic and then start the service.

Case 3: If using NAT, ensure WMI port is allowed in NAT firewall.

WMI port can be static or dynamic, by default WMI port is dynamic.

(I) If your WMI is running in a static port, then directly add the WMI port into the NAT firewall.

(II) If your WMI is running in a dynamic port, add the WMI port range into your NAT firewall. The range is from 1024 to 65535.

If not feasible, then convert WMI port into static port and add that static port into firewall setting of NAT.

Steps to convert the WMI port from dynamic to static:

Set the DCOM config to use a static port

Step 1: Open Run and type ‘dcomcnfg’

Step 2: Navigate the tree to My Computer→ DCOM Config → Windows Management Instrumentation, select the Properties of that folder

Step 3: Select the Endpoint tab under Windows Management and Instrumentation properties

Step 4: Select the Properties button for Connection-oriented TCP/IP

Step 5: Use static endpoint, set the port

Configure WMI to use a fixed port

Follow steps from this link to change WMI port to fixed.

Confirmation test:

When the above-mentioned solutions have been verified, perform a pre-test using the WBEM utility.

Step 1: Open “wbemtest” in your server/client machine

Step 2: In the namespace text box provide Target hostname\IP: \[hostname\IP]\root\cimv2

**Example:** \\192.168.100.100\root\cimv2​

Cause 5: Registry editing disabled on the target host

Enable registry editing tools by modifying Local Group Policy. To allow permission to registry editing tools, follow the below steps:

Step 1: Open 'Run' and type ‘gpedit.msc’

Step 2: In the Local Group Policy editor go to User Configuration → Administrative Templates → System

Step 3: Under System check for ‘Prevent access to registry editing tools’ and check its state

Step 4: If it is enabled then click ‘edit policy setting’

Step 5: Select ‘Not Configured’ then click Apply and then click Okay    

      

Cause 6: Installation privilege blocked on the target host

To Allow installation privilege by modifying Local Group Policy follow the below steps:

Step 1: Open 'Run' and type ‘gpedit.msc’

Step 2: Navigate to computer configuration → Administrative templates → Windows components → Windows installer

Step 3: Check for ‘Turn off windows installer’ and check the state of it

Step 4: If it is enabled then click ‘edit policy setting’

Step 5: Select ‘Not Configured’, click Apply, and then click Okay

Cause 7: Installation failure of Microsoft Visual C++ Redistributable packages

Install required versions of Microsoft Visual C++ Redistributable packages. Check C:\Windows\Vembu\EXEInstallation.log for installation failure details.

Cause 8: Unsupported Operating System

BDRSuite doesn't support backup for outdated OSs not supported by Microsoft.

Cause 9: Improperly removed VIS/BBA agent entry

Restart the target machine and attempt installation again.

Note: Follow the steps mentioned for each cause to resolve the issue. If the problem persists, contact Vembu support for further assistance.