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
- Launch the WMI MMC snapin: go to Start -> Run -> type wmimgmt.msc
- 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.
- If WMI is working correctly, you will see Successfully connected window as shown below.
- 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.