KB ID : 117024
Products :
Published : Nov. 30, 2018
Created : Nov. 30, 2018
Last Modified : Feb. 8, 2019

Cause:

This error occurs in both Vembu BDR and Vembu VMBackup 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’.

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 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 exists, remove the entry using the command prompt.

         sc delete VembuIntegrationService

Step 3: Go to File Explorer → Open OS installed Drive (Commonly ‘C’ drive) → Open Windows Folder → and search for folders named 'Vembu', 'VembuIntegrationService' and delete both of 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 'Run' and type ‘taskmgr’ → Enter

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

Step 3: Switch over to ‘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 server\VMBackup 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, if so please add the below rule into your Inbound firewall rules in your target machine

Step 1: Open control panel

Step 2: Navigate to System and Security → Windows Firewall → Advanced Setting

Step 3: In Windows firewall with advanced security, click Inbound rules

Step 4: Inbound rules → click new rule and proceed to opt for Predefined option

Step 5: In 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 Windows Management Instrumentation service is running in your target machine.

Follow the below steps:

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

Step 2: Navigate to Windows management instrumentation service

Step 3: Check the status of Windows management

   → If the service is stopped then right click on 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 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 static port, then directly add the WMI port into NAT firewall.
    II. If your WMI is running in 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’ → Enter

    Step 2: Navigate the tree to My Computer → DCOM Config → Windows Management and Instrumentation, select 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 below link to change WMI port to fixed:

    https://docs.microsoft.com/en-us/windows/desktop/WmiSdk/setting-up-a-fixed-port-for-wmi

Confirmation test:

When Above mentioned solutions are verified, perform a pre-test using 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’

Agent installation needs access to the registry in the target machine.

If this access to registry editing tools is restricted using local group policy then the agent cannot be installed.

To allow permission to registry editing tools, follow the below steps:

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

Step 2: In 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 the 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’

  • If you are about to allow access to installation privilege then follow the below steps in order:

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

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’ then click Apply and the then click Okay

After following the above steps, you can add the target machine to your desired BDR server or VMBackup client.

Turn Off Windows Installer - Not Configured

edit retag flag offensive close merge delete