Windows

Fix: The RPC Server is Unavailable on Windows 7, 8 and 10

RPC is also known as Remote Procedure Call. It is a technology present since the emerging of computers and utilizes the interprocess communication technique. Its primary purpose is to enable a client and a server to communicate with each other over the network. Same can be said about devices.

The RPC Server is Unavailable
The RPC Server is Unavailable

In simple terms, whenever you are sharing data or information over any network, RPC comes into play does all the work for you. RPC also plays a major role in managing devices over the network and also used in controller peripherals such as scanners or printers.

What causes the error ‘The RPC Server is Unavailable’?

Since RPC is the communication of different devices, there are several different modules which may be responsible for causing the error message. With that said, here are some of the culprits who might be responsible in your case:

  • One or more services required by RPC are disabled – In most cases, this particular issue will occur when one or more computers involved in the connection has one (or more) mandatory services disabled. If this scenario is applicable, you can resolve the issue by using the Services utility to force start the disabled services.
  • Remote assistance is disabled by Firewall – Windows Firewall and a few other 3rd party equivalent are known to block the Remote Assistance connection by default. If this is the culprit triggering the issue, you can resolve the problem by establishing an exception for this type of connection.
  • IPV6 or File Printer Sharing is disabled – Certain types of RPC servers will require both IPV6 and File PRinter Sharing to be enabled on the current network connection. Several users struggling to resolve this particular issue have reported that the issue was resolved after they enabled both from Network Properties.
  • The IP address is crashing the RPC server – An ambiguous IP can also trigger this particular error message. If this scenario is applicable, you can resolve the issue by flushing and then renewing the IP address.
  • RPC services are disabled via Registry – Certain utilities or manual user intervention my force some services required by an RPC server to remain disabled. Users finding themselves in a similar scenario have reported that the issue was resolved after they used the Registry Editor to force-start the services used by the RPC component.

Before you start going over the solutions, make sure that you have an active internet connection and are logged in as an administrator on your computer. Furthermore, if you are using the computer in a work environment, it is best that you consult your network administrator. Each work environment has its separate configuration of the network and the PCs.

Solution 1: Checking RPC service on your computer

The first thing which the users should check if they encounter this error is the RPC service on your computer. Conflicts with other third-party applications or changing the system systems might force the RPC service to go from the default (Automatic) value to manual. This means that RPC might not start automatically when needed.

  1. Press Windows + R, type “services.msc” in the dialogue box and press Enter.
  2. Once in the services window, search for the following processes:
Remote Procedure Call (RPC)

RPC Endpoint Mapper or Remote Procedure Call (RPC) Locator

DCOM Service Process Launcher

Right-click on each service one by one and select Properties.

Services associated with RPC
Services associated with RPC
  1. Once in properties, make that the service is Started and the Startup type is set as Automatic.
Changing startup type and status of RPC services
Changing the startup type and status of RPC services
  1. Save changes and exit. Restart your computer and check if the error message is fixed.

Solution 2: Enabling Remote Assistance in Firewall

Remote Assistance is a mechanism which allows other users or computers see the screen of your computer and even control it if you choose to. Remote assistance might also come into play in the case of RPC servers since the client and server are also exchanging information on a much larger and complicated scale. If your firewall isn’t configured properly, you will the error under discussion.

If you belong in an organization, you should contact the network administrator to look into the issue. While troubleshooting the network, shutting down the main firewall is a way to troubleshoot where the trouble lies. In this demo, we will only go through on what you (the user) can do at his own personal firewall on his computer.

  1. Press Windows + R, type ‘control’ in the dialogue box and press Enter.
  2. Once the control panel pops up, search for Firewall in the search bar at the top-right side of the screen. From the results, click on Allow an app through Windows Firewall which is a subcategory underneath Windows Firewall.
Windows Firewall - Control panel
Windows Firewall – Control panel
  1. Click on Change settings and make sure that entries enforcing RPC are enabled such as Remote Assistance.
Enabling Remote Assistance - Firewall
Enabling Remote Assistance – Firewall
  1. Restart your computer and check if this solved the error message under discussion.

Solution 3: Disabling Selective Startup

The selective startup is a booting method which allows your computer to turn on with a minimal number of items loaded. This is usually done when troubleshooting issues with your computer which might involve other third-party applications. However, whenever you boot using selective startup, your computer will also not load all the RPC components onto your computer. We will select the normal startup and see if this fixes the issue.

  1. Press Windows + R, type “msconfig” in the dialogue box and press Enter.
  2. Once in the startup configuration, select the tab General and choose the option Normal startup.
Selecting normal startup - Boot configuration on Windows 10
Selecting normal startup – Boot configuration
  1. Press Apply to save changes and exit. Now you will be prompted for a restart. Restart immediately using the popped up window and check if the error message is resolved.

Solution 4: Enabling IPV6 and File & Printer Sharing for the connected network

In some cases, you might encounter the Error 1722: The RPC server is unavailable issue in instances where there’s a network connection interruption caused by one or multiple settings. Several affected users have reported that in their case, the issue was resolved after they discovered that Printer Sharing for Microsoft Networks and Protocol Version 6 (TCP / IPv6) were both disabled from their connected Network properties.

Upon enabling these two options back, most affected users have reported that the issue was resolved. Here’s a quick guide on how to do this:

  1. Press Windows key + R to open up a Run dialog box. Then, type “ncpa.cpl” and press Enter to open up the Network Connections window.
  2. Inside the Network Connections window, right-click on the network that you’re currently connected to and hit Properties.
  3. Once you get to the Properties of your network connection, go to the Networking tab and scroll down through the list of items.
  4. Locate File and Printer Sharing for Microsoft Networks and Internet Protocol Version 6 (TCP/IPv6) and make sure that both associated boxes are checked. Then, click Ok to save the changes.
  5. Restart your computer and see if the issue is resolved at the next startup.

If you’re still encountering the Error 1722: The RPC server is unavailable issue, move down to the next method below.

Solution 5: Flushing DNS & Renew

Some affected users have reported that they managed to resolve the issue after using an elevated Command Prompt to Flush the DNS and renew the connection. But in order for this fix to be effective, you need to ensure that the services involved in the RPC connection are running (follow Method 1).

If you’re certain that the required services are running, here’s a quick guide on flushing the DNS and Renewing the connection:

  1. Press Windows key + R to open up a Run dialog box. Next, type “cmd” and press Ctrl + Shift + Enter to open up an elevated Command Prompt. If prompted by the UAC (User Account Control), click Yes to grant administrative privileges.
    Running CMD using the Run Dialog Box
  2.  Inside the elevated Command prompt, type the following command and press Enter to flush the current IP Config:
    ipconfig /flushdns
  3. Once the command is successfully registered, type the following command and press Enter to renew the IP Configuration:
    ipconfig /renew
  4. Once the IP has been renewed, close the elevated Command Prompt and recreate the steps that were previously triggering the Error 1722: The RPC server is unavailable issue to see if the issue has been resolved.

If the same problem is still occurring, move down to the next method below.

Solution 6: Using Registry Editor to force RPC services to start

Some affected users have reported that they managed to resolve the issue after using an elevated Command Prompt to Flush the DNS and renew the connection. But in order for this fix to be effective, you need to ensure that the services involved in the RPC connection are running (follow Method 1).

If you’re certain that the required services are running, here’s a quick guide on flushing the DNS and Renewing the connection:

Here’s a quick guide on how to do this:

  1. Press Windows key + R to open up a Run dialog box. Then, type “regedit” and press Enter to open up the Registry Editor. If you’re prompted by the UAC (User Account Control), click Yes to grant administrative privileges.
  2. Inside the Registry Editor, use the left-hand pane to navigate to the following location:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RpcSs

    Note: You can either get there manually by using the left-hand pane or you can paste the exact address directly into the navigation bar and press Enter. With the RpcSs key selected, move down to the right-hand pane and double-click on Start.

  3. Inside the Edit Dword Value associated with Start, set the Base to Hexadecimal and the Value data to to enable the Remove Procedure Call (RPC).
  4. Use the left-hand pane or the navigation bar at the top to navigate to this location:
    Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DcomLaunch
  5. Once you get to that location, double-click on Start from the right-hand pane. Then, set the Base to Hexadecimal and the value data to 2 in order to enable the DCOM Server Process Launcher.
  6. Navigate to the following location by using the navigation bar at the top or by using the left-hand pane:
    Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RpcEptMapper
  7. Move over to the right-hand pane and double-click on Start. Then, set the Base to Hexadecimal and the Value Data to 2.
  8. Close the Registry Editor, restart your computer and see if the issue has been resolved at the next system startup.

In addition to the above solutions, you can also find more workarounds regarding the error ‘RPC Server is Unavailable’ by reading our article Fix: The remote procedure call failed. Both the error cases are almost the same and same fixes can be tried in both cases.

Leave a Reply

Your email address will not be published.

Expert Tip

Fix: The RPC Server is Unavailable on Windows 7, 8 and 10

If the issue is with your Computer or a Laptop you should try using Reimage Plus which can scan the repositories and replace corrupt and missing files. This works in most cases, where the issue is originated due to a system corruption. You can download Reimage by clicking the Download button below.

Download Now

I'm not interested

Close