"The RPC server is unavailable" error message displayed while adding or monitoring Windows server through WMI mode.

"The RPC server is unavailable" error message displayed while adding or monitoring Windows server through WMI mode.

Here are a few methods to resolve an error :
  1. Try adding the server using domain name if the server is in a domain
  2. Try adding the server using name if the server is in a workgroup.
  3. If the server is in a DMZ, add the ipaddress and hostname in the <C:\Windows\system32\drivers\etc\hosts> file in Applications Manager server. 
    1. Ensure that the DNS record for this computer is up-to-date in the DNS Server.
  4. Check whether the RPC and WMI services are running in the remote machine.
    1. In the remote machine, go to Start --> Run --> services.msc
    2. Check whether the services Remote Procedure Call and Windows Management Instrumentation are running.
    3. If they are not running, start those services and add them to Applications Manager.
  5. Check the firewall settings and open the following ports required for WMI mode of monitoring.
    1. Remote Procedure Call (RPC) (default : 135)
    2. DCOM for remote communication:
      1. The server to be monitored uses a random port number above 1024 by default to respond back. 
      2. Connect to the target server and configure it to use a port within a specified range of ports (5000 - 5100). You can follow the steps mentioned here for restricting the ports in the target server.
      3. Normally, opening at least a range of 100 ports is recommended. The same range of ports must also be opened in your firewall.
      4. Specific range of ports need to be opened based on the Windows' version to be monitored. Learn more
  6. Steps to enable Remote Administration in client machine's Firewall:
    1. Go to Start → Run → gpedit.msc to open Local Group Policy Editor.
    2. Click on Local Computer Policy and go to  Computer Configuration → Administrative Templates → Network → Network Connections→ Windows Firewall →Domain Profile.
    3. Right-click remote administration exception rule, and then click Edit.
    4. Choose Enabled, and then click OK.
  7. From the AppManager host, use wbemtest to find the error code when connecting to the remote system.
    • Click on Start --> Run --> wbemtest
    • It opens up the Windows Management Instrumentation Tester tool. Click on the Connect button. 
    • In the first text box (\\root\default) , enter the following path <\\hostname\root\cimv2>. Then enter the username and password under the Credentials tab. 
    • If it works, then you would be able to access the machine only through the IP address. This may be due to some wrong entries in the <C:\Windows\system32\drivers\etc\hosts> file. Remove the wrong entries in the file and try again with the hostname.
    • If the error code is "0x800706BA" , Configure the firewall to allow remote administration. To do this, open a command prompt on remote windows machine and execute the following commands:
      • netsh advfirewall firewall set rule group="Windows Remote Management" new enable=yes
      • netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes
      • netsh advfirewall firewall set rule group="remote administration" new enable=yes
    • If the result of the last command is "No rules match the specified criteria" then run the below command :
      • netsh firewall set service remoteadmin enable
                  Now re-execute the (iii) command again. 
If it still does not work, send the screen shot of the error dialog which comes in wbemtest to appmanager-support@manageengine.com







          New to M365 Manager Plus?
          New to M365 Manager Plus?
            New to RecoveryManager Plus?
            New to RecoveryManager Plus?
              New to Exchange Reporter Plus?
              New to Exchange Reporter Plus?
                New to SharePoint Manager Plus?
                New to SharePoint Manager Plus?
                  See all integrations
                  New to ADManager Plus?
                  See all integrations
                  New to ADManager Plus?

                    New to ADSelfService Plus?

                    Start your free trial
                    Start your free trial

                      • Related Articles

                      • Configuring non-admin user account for WMI monitoring

                        By default, Windows allows only members of the Administrators or Domain Admin groups to read WMI class information. However, you can configure a regular user to access WMI information by performing the following steps on the server that needs to be ...

                      • Windows Monitoring - FAQ

                        This Knowledge Base article provides answers to frequently asked questions related to Windows Server monitoring through WMI. The articles are categorized based on the monitoring lifecycle to help you quickly identify the relevant troubleshooting ...

                      • WMI Error Troubleshooting Guide

                        Overview This Knowledge Base provides troubleshooting guidance for commonly encountered Windows Management Instrumentation (WMI) errors that may occur while adding a Windows monitor or collecting metrics through WMI mode in Applications Manager. WMI ...

                      • WMI/RPC Communication Errors

                        Applicable WMI Error Codes 0x800706BE – The remote procedure call failed 0x80010002 – Call was canceled by the message filter Overview These errors occur when Applications Manager is unable to establish or maintain WMI/RPC communication with the ...

                      • Unable to Retrieve Data Through WMI Mode

                        Overview This article provides troubleshooting steps to identify and resolve data collection failures for Windows monitors configured in WMI mode. If one or more metrics are not being collected, the steps in this article will help determine whether ...
                      Related Products