Intermittent WMI query " 'Win32_PerfRawData_PerfOS_Memory' failed : The RPC server is unavailable. 0x800706BA" on Windows Server 2008 R2.
Intermittent 0x800706BA error is a classic WMI problem on Windows 7 and Windows Server 2008 R2 (for both, RTM and SP1).
Intermittent 0x800706BA error is a classic WMI problem on Windows 7 and Windows Server 2008 R2 (for both, RTM and SP1).
If it is the case, please check the hot fix
http://support.microsoft.com/kb/2547244
Otherwise, Please perform the following tests:
Test 1:
1. On the Diagnostic Server machine log on under the account used to run the Spotlight Diagnostic Server;
2. Go to “Computer Management” (on the Diagnostic Server machine), right click on the “Computer Management (Local)” | “Connect to another computer”, specify the “\\HOSTNAME”; where “HOSTNAME” is the name of machine you want to monitor with Spotlight;
3. Go to “Services and Applications”| right click on the “WMI Control”, go to properties in the context menu | be sure “General” tab is opened;
If it succeeded, try to monitor this machine with Spotlight again.
Test 2:
1. To check the WMI is not broken and returns data properly, run the command below in the command prompt locally on the machine you want to monitor:
wmic path Win32_PerfRawData_PerfDisk_LogicalDisk get FreeMegabytes
2. Then run the same command on the Diagnostic Server machine specifying remote host name which you want to monitor with Spotlight and valid credentials:
wmic /node:MonHostFQDN /user:DOMAIN\USER path Win32_PerfRawData_PerfDisk_LogicalDisk get FreeMegabytes
where MonHostFQDN – monitored machine fully qualified domain name, machine name or IP-address;
DOMAIN\USER – valid credentials.
If tests failed with an error, use the table below to identify the problem:
Error | Solution |
Access denied: [0x80070005] | Change Spotlight Diagnostic Server service credentials to a domain-level account (preferably with domain admin privileges) and then restart the Spotlight Diagnostic Server or configure each connection not to use Windows Authentication and specify valid user credentials. |
The RPC server is unavailable. [0x800706BA] | 1. The remote computer is blocked by the firewall. Solution: Open the Group Policy Object Editor snap-in (gpedit.msc) to edit the Group Policy object (GPO) that is used to manage Windows Firewall settings in your organization. Open Computer Configuration, open Administrative Templates, open Network, open Network Connections, open Windows Firewall, and then open either Domain Profile or Standard Profile, depending on which profile you want to configure. Enable the following exception: "Allow Remote Administration Exception" and "Allow File and Printer Sharing Exception".
2. Host name or IP address is wrong or the remote computer is shutdown. Solution: Verify correct host name or IP address.
3. The "TCP/IP NetBIOS Helper" service isn't running. Solution: Verity that "TCP/IP NetBIOS Helper" is running and set to auto start after restart.
4. The "Remote Procedure Call (RPC)" service is not running on the remote computer. Solution: Verity that "Remote Procedure Call (RPC)" service is running and set to auto start after restart.
5. The "Windows Management Instrumentation" service is not running on the remote computer. Solution: Verity that "Windows Management Instrumentation" service is running and set to auto start after restart.
|
WMI connection time outs | The WMI COM API doesn't support specifying a timeout value. The timeout value is https://docs.microsoft.com/en-us/windows/win32/cossdk/setting-the-transaction-time-out |
WMI query ... failed: Invalid class. [0x80041010] | This error can be fixed by enabling PerfDisk, PerfNet, PerfOS and PerfPRoc counters. Use the Extensible Counter List (Exctrlst) utility to do this: It was created by Microsoft in Windows 2000 times and since those times documentation was not updated. So, it is officially supported to run the Exctrlst under Windows 2000 OS family only. Customer can request official clarification on this topic by contacting Microsoft. However, the utility downloaded from the link above successfully works on Windows Server 2003 and 2008 machines. |
WMI query ... failed: Invalid query. [0x80041017] | This error occurs when the performance objects are enabled, but return no proper columns used in WQL queries. This is known MS problem: <http://msdn.microsoft.com/en-us/library/aa394528(VS.85).aspx> To resolve it Microsoft suggests to update WMI classes from the performance libraries using the following command in the command prompt on the monitored machine: wmiadap /f |
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center