-
Titre
"Invalid WMI query 0x80041017" error found in log files when collecting Windows performance counter data -
Description
What does the error message "WMI query failed: Invalid query. 0x80041017" in a FglAM or agent log file represent?
Disk metrics are not available from the Databases Dashboard home.
- The following error is present on the DB Instance alarms:
“Oracle – Collection Status. DBO_OS_File_System_IO Failed with the exception: Failed to execute query on host HOSTNAME. Reason : [WinRM request to http://HOSTNAME:5985/wsman failed: [code:2150858778] The WQL query is invalid"
- When running the WMI Query from the error message on the host using the “wbemtest” utility the following error is seen:
Number: 0x80041017Facility: WMIDescription: Invalid query- When modifying the original query by selecting “all” columns, “select * from Win32_PerfRawData_PerfDisk_PhysicalDisk where Name != '_Total'].”, a result is presented by the utility.
-
Cause
Cause 1
Missing WMI classes
Cause 2
Broken performance counters
Cause 3
The query syntax was parsed incorrectly due to issues with quotation marks when cutting and pasting the query.
Cause 4
Performance counters are disabled in the registry
Cause 5
The columns returned by the WMI class are incomplete or unexpected. This error can indicate that the query returned a null value. Therefore the script can't continue / will throw the 0x80041017.
It is possible that the Win32_PerfRawData_PerfOS_Processor cannot be found or accessed on the server causing a null result. If the same query runs and retrieves values from other similar Windows systems at the same OS level this indicates that the query is correct and something is different at the OS level causing the query not to retrieve data.This is a often due to a Microsoft bug happening outside of the Foglight product.
-
Résolution
Use WBEMTEST to test OS data collections locally on the system and from remote Windows systems (114295).
Resolution 1
In some cases, as per KB 93113 running the following command in the Windows' command line (CMD) may solve the problem of missing WMI classes.
%windir%\system32\wbem\wmiadap.exe /f
This command parses all the performance libraries on the system and refreshes the Performance Counter Classes. For further details see Windows Management Instrumentation Documentation.
Resolution 2
Rebuild the Performance Counters using the "lodctr /r" command as per KB 185319. Additional information can be found on solution 2554336 from the Microsoft Knowledge Base.
Resolution 3
Replace the quotation marks in the WMI query or copy them into notepad and then back into the query tool.
Resolution 4
The registry key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\PerfProc\Performance” or “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\PerfDisk\Performance” is set so that “Disable Performance Counters” is set to 1, which means it is disabled.
Users can manually change the registry key to "0" or they can use the Extensible Counter List Tool as described in this Microsoft blog titled "Two-Minute Drill: Disabled performance counters and Exctrlst.exe" to enable the Performance Counters in the Operating System. The registry change happens immediately.
If the "Disable Performance Counters" registry key is not present then the Performance Counters have not been disabled at the registry key here.
Note: Support does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.
Resolution 5
Please contact your Microsoft support team to recreate the WMI class properly.
Additional information can be found on solution 961435 from the Microsoft Knowledge Base.
NOTE: A restart of the system may be required after applying the suggested solutions.