RPC Server is Unavailable Error 0x800706BA Fix

Updated July 2024: Stop getting error messages and slow down your system with our optimization tool. Get it now at this link
  1. Download and install the repair tool here.
  2. Let it scan your computer.
  3. The tool will then repair your computer.


Cause: This error is most likely caused by an RPC port blocking between the servers involved in the communication or the server you are trying to work with. Background: RPC is classified as an X11 protocol and is in the port range 6001 to 6032.

Check all computer logs (network, antivirus) of your firewalls to see if the log is blocked.
Restart the remote computer to ensure that all RPC services are running correctly.

Restart the RPC server.
Clean up your computer at startup to exclude third-party applications.
Check the connection to the network settings.
Change your firewall settings.
Change the registry settings.
Use System Restore on your computer.


Error 0x800706ba “The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)” can occur when executing PowerShell scripts with a WMI request. RPC is classified as X11 protocol and is in the port range 6001 to 6032, usually 6007, which is blocked in this case.


The error code 0x800706BA indicates that the RPC (Remote Procedure Call) server is not available. This problem occurs when the client computer under Windows XP releases the remote COM+ object. About 20 seconds to 30 seconds after the client computer shares the remote COM+ object, the RPC ports used by DCOM on the server are closed. If the network connection is disconnected immediately after the client computer releases the Remote COM+ object, the RPC ports used by DCOM on the server remain open for several hours. This can lead to the exhaustion of connections. Future requests from the client computer to the remote COM+ object fail.

You can test the RPC connectivity of the server on which you are located to another computer/server by using the following command:

Get-WmiObject Win32_ComputerSystem –ComputerName OTHERSERVER

Possible cause of error 0x800706ba:

  1. This error is most likely caused by blocking RPC ports between the servers associated with the communication or server process you are trying to terminate.
  2. The RPC service is stopped on the remote server.
  3. The Endpoint Mapper on port 135 couldn´t is accessible on the remote server.

July 2024 Update:

You can now prevent PC problems by using this tool, such as protecting you against file loss and malware. Additionally it is a great way to optimize your computer for maximum performance. The program fixes common errors that might occur on Windows systems with ease - no need for hours of troubleshooting when you have the perfect solution at your fingertips:

  • Step 1 : Download PC Repair & Optimizer Tool (Windows 10, 8, 7, XP, Vista – Microsoft Gold Certified).
  • Step 2 : Click “Start Scan” to find Windows registry issues that could be causing PC problems.
  • Step 3 : Click “Repair All” to fix all issues.


Configure the Windows Firewall service to allow incoming remote management connections.

Open the Group Policy Object Editor (gpedit.msc) to change the Group Policy Object (GPO) used to manage Windows firewall settings in your organization.

Open Computer Configuration, open Administration Templates, open the network, Network Connections, open Windows Firewall, and then open the default domain profile or profile, depending on the profile you want to configure.

Enable the following exceptions: “Allow exception for remote administration” and “Allow exception for file and printer sharing”.

Check the firewall settings

Start Firewall Manually

To solve your problem, follow these steps:

Disable the Windows Firewall service (or a third-party firewall) on the problem server.


If you are using a third-party firewall, configure it to allow connections to the following TCP and UDP ports: 135, 445.

Modify the DCOM access group

Modify the DCOM access group

This problem may have several solutions, but in most cases, the cause of the problem is that your computer is a member of the DCOM access group (DCOM access to certificate service) or that the wrong authorization is granted. Follow these steps:

In the controller domain on which the certification service is provided, you must ensure that there is a group of domains CERTSVC_DCOM_ACCESS or Certificate Service DCOM Access ;
Add the following domain groups to the CERTSVC_DCOM_ACCESS/Certificate Service DCOM Access group: domain users, domain controllers, domain computers ;
Use the commands to update the DCOM security settings on the server with the CA role:

certutil -setreg SetupStatus -SETUP_DCOM_SECURITY_UPDATED_FLAG

net stop certsvc & net start certsvc

On a server with the supplied CA, check the COM security permissions. Remote access and remote activation permissions should be allowed for this group.

Then try restarting the computer and check that the certificate has been issued.


Expert Tip: This repair tool scans the repositories and replaces corrupt or missing files if none of these methods have worked. It works well in most cases where the problem is due to system corruption. This tool will also optimize your system to maximize performance. It can be downloaded by Clicking Here