RPC Server Exception RRS feed

  • Question

  • System.Management.ManagementScope ms = new System.Management.ManagementScope("\\\\" + stringMachineName + "\\root\\cimv2", co);

    oq = new System.Management.ObjectQuery("SELECT * FROM Win32_processor");

    query = new ManagementObjectSearcher(ms, oq);

    queryCollection = query.Get();

    return queryCollection;


    well guys i am trying to access remote system but in doing this some machines give mein following exception


    RPC SERVER IS unavailable (Exception from Hresult:0x800706BA)



    can u help me this how to solve this

    Tuesday, May 30, 2006 4:24 AM


  • We use a third-party firewall product that I was unaware of. When I configured it to allow my IP address access to the server, my problem went away.



    Monday, October 23, 2006 7:17 PM

All replies

  • This could have one of many reasons, namely the machine name is wrong etc.

    Check out this article.


    Wednesday, May 31, 2006 1:16 AM
  • JK,

    Did you ever get this resolved? I have the same problem...

    Wednesday, September 27, 2006 8:06 PM
  • no
    Thursday, September 28, 2006 10:07 AM
  • Make Sure the path and name to the Remote machine is correct and RPC services are running on that.

    Thursday, September 28, 2006 2:48 PM
  • Yes, I have verified that the RPC and WMI services are running on the remote computer. I am also able to ping the server. I have also verified that the server computer does not have the Microsoft Firewall enabled.

    The only thing I am not certain about is that the account I am using is found on a domain server (i.e., local accounts are not being used). Do I have to format the user ID I am passing in a particular way (e.g., domainName\userID)? Do I have to set any of the other properties on the ConnectionOptions class besides user name and password?

    I'm at a lost. Any help you can provide would be appreciated.



    Thursday, September 28, 2006 2:54 PM
  • The domain administrator have complete rights on the computer under that domain, so I think if you are providing correct username, password then it should work, But when I see your exception message it seems that problem is not here with Connection Crednitials.

    Anyways Try as much things as possible, See RPC and RCP locator services are up and running on the remote machine.

    Best of luck ;-)

    Thursday, September 28, 2006 3:00 PM
  • One important thing is that try searching google for this error "Hresult:0x800706BA" this will tell you the exact cause of the problem.

    Best Regards,

    Thursday, September 28, 2006 3:03 PM
  • Have a look here:

    I hope this will solve your problem:


    Best Regards and Best of Luck ;-)

    Thursday, September 28, 2006 3:06 PM
  • There's no firewall enabled on either machine. Consequently, I don't think this applies.
    Thursday, September 28, 2006 3:09 PM
  • Hello Jahangir,

    The Exceptoin: RPC SERVER IS unavailable (Exception from Hresult:0x800706BA) results from a "wrong" call to Your WMI Provider. Can you post Your connectionoptions (You used as Variable co ).

    If You run Your Application locally You may use the following:

    System.Management.ManagementScope ms = new System.Management.ManagementScope(\\\\ + "." + "\\root\\cimv2", co);

    (I replaced the string Variable which holds the computername with . - it represents the local Computer  WMI Provider.


    Wolfgang Zerzawy



    Monday, October 23, 2006 5:57 PM
  • We use a third-party firewall product that I was unaware of. When I configured it to allow my IP address access to the server, my problem went away.



    Monday, October 23, 2006 7:17 PM
  • This post is pretty old, but it's one of the first google search listings for this error.  I get this error when I run a powershell Get-WMIObject against a remote computer.   I'm running as domain admin, machine pings, firewall is off and Get-WMIObject USED TO WORK.  We installed IIS and .net (v2 in some cases, v3.5 in others).

    I found that I now have to use the FQDN as the computername or else I get the RPC error.

    Get-WMIObject win32_process -computername "myMachine"  <---- Fails with "Exception from HRESULT: 0x800706BA"
    Get-WMIObject win32_process -computername "myMachine.mydomain.com"  <---- Succeeds
    Friday, August 28, 2009 8:08 PM
  • Hi there, just to revive this old post.

    I've ensured that RPC, RCP, and both WMI services are running on both Server and Client.

    My server (for some reason) cannot perform WMI checks on the Client, whereas my Client can perform checks on my server.

    Both are connected via Domain.

    Is there any reason why this is happening? Please help!
    Wednesday, November 4, 2009 8:57 AM
  • Sorry cant help but post on this old 1....

    stuck in the same situation and found this link

    http://support.microsoft.com/kb/960007 still dont know what to do :P

    If any solution is available please reply.



    Wednesday, September 1, 2010 6:26 AM
  • A really helpful tool is the "Paessler WMI Tester V2" available at:  http://www.paessler.com/download/wmitester

    Once thing of note:  If you have IIS services running on the computer giving the RPC not available error, you will have to use the IIS manager to change "Authentication" to "Enabled" for ASP.NET Impersonation.  This happend to me on a Windows 7 box that was the only one in the domain that wouldn't allow WMI.

    Thursday, December 9, 2010 9:59 PM