Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Hardware Asset Scan or Device Scan fails with the error: WMI connection required for WMIAssetEcho (2038742)

Symptoms

  • You cannot run a successful device scan in VMware Go.
  • You cannot run a hardware asset scan in vCenter Protect.
  • The Discover.native.log for VMware Go or the ST.Protect.native.log for vCenter Protect may contain an error similar to:

    ActionBase.cpp:270 MrFixit - error class mrFixit::CMrFixitException at WMIAssetAction.cpp:98: WMI connection required for WMIAssetEcho. in action WMIAssetEcho/

Cause

The WMI component on the target machine being scanned is accessed to enumerate the hardware and software values of the machine. If this cannot be accessed, the scan fails.
 
This issue occurs if:
  • The WMI component is not enabled

    Or

  • The credentials being used do not have rights to access the target machines WMI component

Resolution

To test if the WMI component can be accessed on the target machine for a Windows operating system:
  1. Go to the built-in WMI testing tool (installed by default on most Microsoft operating systems). Click Start > Run, type wbemtest, and click OK.
  2. Click Connect.
  3. Enter the full namespace path. For example:
    • \\machinename
    • \\root\cimv2

      Note: The namespace for the WMI component is often cimv2. However,this can be changed by an administrator. Look on the target machine's WMI component (click Component Management > Services and Applications > WMI control, then right-click Properties and click the Advanced tab).

  4. Enter the username and password to access the WMI component.
  5. If this fails with RPC server is unavailable or access denied, the WMI component cannot be accessed from the VMware Go machine or vCenter Protect console system.
If you are cannot connect to the WMI component:
  1. Right-click the target machine WMI component, and click Properties to see if you can access it locally. If not, ensure that the WMI service is set to automatic and is started on the machine.
  2. Ensure that port TCP/IP 135 is open:
    • Outbound from the VMware Go machine or vCenter Protect console system
    • Inbound to the target machine

  3. Flush the WMI repository on the target machine:
    1. Stop the WMI service.
    2. Delete the contents of <%WINDIR%>\System32\wbem\Repository.
    3. Reboot the system and ensure that the WMI service is started.
    4. Create a new full local administrative account on the target machine and attempt to connect to the target WMI using the wbemtest tool with these credentials.

If the issue persists, contact your network administrator for further assistance.

Additional Information

For related information, see the Microsoft article WMI Troubleshooting (Windows).

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 0 Ratings
Actions
KB: