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.
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
Enabling WMI event tracing
By default, WMI events are not traced. This procedure describes how to use Event Viewer to enable WMI event tracing and locate WMI events.
- Open Event Viewer:
- press Win + R;
- in the Run window that opens, type eventvwr.msc and press Enter - On the View menu, click Show Analytic and Debug Logs:
- Locate the Trace channel log for WMI under Applications and Service Logs > Microsoft > Windows > WMI Activity.
- Right-click the Trace log and select Properties. Click the Enable Logging check box to start the WMI event tracing.
- Reproduce the issue.
- WMI events appear in the event window for WMI-Activity. Double-click an event in the list to see the detailed information.
- In some cases, the event will contain instructions on how to resolve a particular error. For other events, use the Event ID and Source in your search to find additional information online.
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 WMI Events in Event Viewer.
If the command returns that the WMI database is in an inconsistent state, perform recovery of the repository as described below.