WMI is unable to return data in a timely manner

Purpose

The purpose of this article is to provide troubleshooting steps for investigating the "WMI is unable to return data in a timely manner" error. This error can be encountered when attempting to scan one or more target devices with PDQ Inventory.

Troubleshooting

When PDQ Inventory scans a device, log files for the scan will be generated in the \\target-pc\ADMIN$\AdminArsenal\PDQInventory-Scanner directory. After the scan fails, review the log files in this directory and see if any CrashLog files were created.

 

While troubleshooting, we recommend deleting these logs from a target that is failing with this error, then scanning the device again so that only the latest logs are present. 

Example: CrashLog-PDQInventoryScanner-YYYY-MM-DDT00_00_00.log

Exception has been thrown by the target of an invocation.
Configuration system failed to initialize
System.Configuration.ConfigurationErrorsException
HResult: 0x80131902 Code:6402 Facility:19 Warning
------- INNER EXCEPTIONS -------
Unrecognized configuration section runtime. (C:\Windows\AdminArsenal\PDQInventory-Scanner\service-1\exec\PDQInventoryScanner.exe.Config line 3)
System.Configuration.ConfigurationErrorsException
HResult: 0x80131902 Code:6402 Facility:19 Warning
at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
at System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(ConfigurationSchemaErrors schemaErrors)
at System.Configuration.ClientConfigurationSystem.EnsureInit(String configKey)
[...]

Referencing the error above in the CrashLog, the "Unrecognized configuration section runtime" error can occur if the "machine.config" file is missing in the .NET installation directory on the target device. Check to ensure the following files are present on the target:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\machine.config
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config

If these files are missing, you can try the following:

  • Check to see if the "machine.config.default" file exists in these directories.
    • If this file exists, create a copy of it and rename the copy to "machine.config"
  • Copy the "machine.config" file from another machine in your environment.
  • Repairing or re-installing .NET Framework

If you continue to experience this error after ensuring valid "machine.config" files exist in these directories, the issue may be related to a corrupt WMI repository, or a corrupt .NET installation. For additional troubleshooting, please refer to the links below:

Was this article helpful?
Still have a question or want to share what you have learned? Visit our Community Discord to get help and collaborate with others.