How to troubleshoot WMI errors

Operating Systems: 

 

In some cases Acronis products may produce an error caused by malfunction in Windows Management Instrumentation (WMI). For example, an operation fails with message "WMI 'ExecQuery' failed".

 

 

 

WMI is Windows Management Instrumentation, Acronis uses its functionality on Windows machines to get information about disks, system and services. The WMI errors indicate that Acronis Agent had attempted a query via WMI tools and WMI tools failed to process it.

This article describes how to troubleshoot WMI errors using WMIDiag tool.

Confirm WMI is broken

  1. Launch the WMI MMC snapin: go to Start -> Run -> type wmimgmt.msc 
  2. Right click WMI Control (Local) and click Properties

     Alternatively, you can open WMI properties by going to Control Panel -> Administrative Tools -> Computer Management. In the left-hand pane, click Services & Applications -> WMI Control, right-click and select Properties.

  3. If WMI is working correctly, you will see Successfully connected window as shown below. 

  4. If you see Invalid class or any other error message then WMI is not working properly

Run Microsoft WMIDiag tool

Download http://www.microsoft.com/en-us/download/details.aspx?id=7684

Run the downloaded .EXE and specify a folder to extract the files. Once extracted right click the WMIDiag VBScript and click Open with Command Prompt

Diagnostic script will start automatically:

Once complete you will get a text file of the results. Check the the report to narrow down the cause of your WMI issue.

By default WMIDiag log files are stored in C:\USERS\%USERNAME%\APPDATA\LOCAL\TEMP

Example:

If WMIDiag log contains the following errors: MOF registration: WMI information not available, reregister all .MOF files with WMI. Run the following command from elevated command prompt:

CD C:\Windows\System32\WBEM
dir /b *.mof *.mfl | findstr /v /i uninstall > moflist.txt & for /F %s in (moflist.txt) do mofcomp %s

If needed, contact MS support for assistance with WMI troubleshooting.

How to check WMI repository consistency

In Windows Vista or higher, you can check if the repository is damaged with the following command from the elevated Command Prompt (Start -> Search -> type "cmd" -> right-click and select Run as administrator):

winmgmt /verifyrepository

If the repository is not corrupted, a “WMI Repository is consistent” message will be returned. If the repository is consistent, you need to troubleshoot more granularly using the WMIDiag utility.

If the command returns that the WMI database is in inconsistent state, perform recovery of the repository as described below.

Rebuilding WMI repository manually can result in some 3rd party products not working until reinstallation. 
It is strongly recommended to create a backup of your system before making changes to WMI repository. In case Acronis product does not work properly due to WMI errors, you can create a backup using Acronis Bootable Media or a third-party tool.

 

HideHow to rebuild WMI repository:

1. Disable and stop the WMI service.

     sc config winmgmt start= disabled

(note the blank space before disabled)

     net stop winmgmt

(this will also ask to stop Acronis services)

 2. Run the following commands

     Winmgmt /salvagerepository %windir%\System32\wbem      

     Winmgmt /resetrepository %windir%\System32\wbem

3. Re-enable the WMI service and reboot the machine

     sc config winmgmt start= auto

 If the problem remains after consistency check, rebuild the WMI repository:

 1. Disable and stop the WMI service.

     sc config winmgmt start= disabled 

     net stop winmgmt

2. Rename the repository folder located at %windir%\System32\wbem\repository to repository.old.

3. Re-enable the WMI service.

     sc config winmgmt start= auto

 4. To recreate the repository, you need to run a WMI-using application. The simplest way to do this is to launch the WMI MMC snapin again (Start -> Run -> wmimgmt.msc), right click WMI Control (Local) and click Properties. There will be a delay of some seconds while a new repository is created. 

  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

New Software 2018 - How to recover / restore files customer login

To Recover / restore files from customer login: When logged in, You will see you have an option...

New software 2018 - Initial setup + Installing Software and adding a backup

Installing Software - Initial Setup Initially as client/ customer you will get an activation...

Guardian Neo Backup of SQL instance fails with "There are no SQL writers"

Symptoms You have installed Guardian Neo Backup agent for SQL and created a backup plan for a...

New Software 2018 - Reseller Rebranding

Reseller BrandingOnce you have logged in, Go to Settings > Branding on the left side panel...