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

Cause:

This error occurs in both Vembu BDR and Vembu BDR Client due to the following reasons:

1) Network issue during agent installation in the target host

2) Insufficient drive space in the target host

3) Another MSI running in the target host

4) Access to WMI services is denied in the target machine

5) Registry editing has been disabled in the target host using Local Group Policy

6) Installation privilege is blocked in the target host using Local Group Policy

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

8) Vembu BDR Suite does not support backup for outdated Operating Systems (OS)

Solution:

For Cause 1: Network issue during agent installation in 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.

  • Try to add the host again. If it ends in failure, it means the previous installation is not done properly.

Follow the below steps in your target machine to overcome such failures:

  • Step 1: Check for the registry entry - ‘VembuIntegrationService’. If exists, then remove/rename the entry.

  • Step 2: Check for 'VembuIntegrationService' entry under 'Services.msc'. If it exists, remove the entry using the following command in the command prompt.

    sc delete VembuIntegrationService
    
  • Step 3: Go to File Explorer → OS installed Drive (Commonly ‘C’ drive) → Windows Folder → and search for folders named 'Vembu', 'VembuIntegrationService' and delete them.

After following the above steps, try adding the same target machine.

For cause 2: Insufficient drive space in the target host

  • Recommended storage space in your target machine’s OS drive is “2GB”.

  • Storage space less than 2GB would result in the above-mentioned error.

For cause 3: Another MSI running in 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.

For Cause 4: Access to WMI services is denied in the target machine

Case 1: Make sure your firewall does not block any Windows Management Instrumentation function. Add the below rule into your Inbound firewall rules in your target machine to ensure the same

  • Step 1: Navigate to the Control Panel

  • Step 2: Click on System and SecurityWindows FirewallAdvanced 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: Make sure that the Windows Management Instrumentation service is running in your target machine.

Follow the below steps:

  • 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 you are using NAT, please make sure 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
    

For cause 5: Registry editing has been disabled in the target host using ‘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

Prevent access to registry editing tools - Not Configured state

For cause 6: Installation privilege is blocked in the target host using ‘Local Group Policy’

To allow access to installation privilege, 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

For cause 7: Installation failure of Microsoft Visual C++ Redistributable packages

Required versions of Microsoft Visual C++ Redistributable packages have to be installed.

If there is any interruption during package installation, then it leads to installation failure.

The reason for installation failure can be checked in the log located at C:\Windows\Vembu\EXEInstallation.log

Once you check the log and find the reason for failure, you can add the target machine to your desired BDR Backup Server or Vembu BDR Client.

Turn Off Windows Installer - Not Configured

For cause 8: Vembu BDR Suite does not support backup for outdated Operating Systems

The Vembu BDR Suite does not support the Operating Systems (OSs) that are no longer supported by Microsoft Windows in the market.

edit retag flag offensive close merge delete