'RPC Server Unavailable' Error: Solutions

The reason for many Windows service crashes is the RPC service. Explanation of abbreviation - remote procedure call, and in the original - Remote Procedure Call. In this article, we will talk about the version of this technology built into the Windows operating system that allows applications on different computers based on NT (including 2000 / XP / 2003/2008 / Vista / Seven) to exchange data streams through various protocols. At a high level, the interaction between applications is used for interoperability - DCOM (the so-called MSRPC). The transport layer is usually implemented using TCP / IP and UDP network protocols . The "RPC server unavailable" message associated with the RPC service issue may occur as a result of various actions. Most often it's installing printer drivers, trying to access a remote domain server, manipulating the video card driver, and so on.

First, we look at the event log (Start Menu, select the second row and Control Panel, and then click Administration, and here is Event Viewer). This often helps to identify the source of the problem. Sometimes the indicated malfunction has a floating character, that is, everything works in the evening, and in the morning the order is complete. Then be sure to check all computers on the network with the latest version of the antivirus package. Symptoms can be manifestations of the famous "malicious" Conficker exploiting the vulnerability of the RPC architecture. Try also to check the firewall configuration for passing packets through ports 135 through 445 (you can temporarily disable it with the sc sharedacess stop command) and update the system using patches from the Microsoft server (the "Automatic system update" service).

There is also a very simple way to eliminate the message "RPC server is unavailable" in the shortest possible time - replace the SYSTEM registry hive by obviously not having this problem. After all, the parameters of all services and drivers are stored there. A non-working service is a common cause of this problem. This can help if the virus has infiltrated as a service, rather than replacing the existing one, as often happens. It is best to do this operation through the Recovery Console. But you can also use the service "System Restore" (you can go to the Recovery Console using the distribution kit), specifying the date before the problem occurred, or through the Windows Recovery Console copy the SYSTEM file instead of the current one from the REPAIR folder. It should be noted that the last action will nullify the information about the equipment, which is fraught with the loss of time for the retirement of all devices of the system. Often this is the fastest and most effective way to deal with the difficulties associated with RPC, without having to delve into the problem and mess with non-performing services.

If for some reason you do not want to get rid of the message "RPC Server unavailable" in the above-mentioned way, then check using the sc query command dialed in the console (to call the console, select the "Start" menu> "Run" in the opened window, type Cmd), if DcomLaunch services are running. RpcSS, Spooler. If they are not in the list, try running them with the sc start commands DcomLaunch; Sc start RpcSS; Sc start Spooler. If everything went well and with the sc query command these services are displayed, you can now write them to the appropriate registry key using the sc config commands DcomLaunch start = auto; Sc config RpcSs start = auto, sc config Spooler start = auto.

Still showing an error "RPC Server Unavailable"? Check for the Spoolss.exe and Spoolss.dll files in the C: \ Windows \ SYSTEM32 directory. Use the sfc / scannow command to check system files and replace the damaged ones with original ones. After all, there could be damage to the file system. In addition to problems with terminal connection using RDP and printing, which are more typical for previous operating systems - Windows 2000 / XP / 2003/2008, there are often problems in the message "RPC Server Not Available" due to lack of sound in Windows 7 The difference between this operating system is that the Windows Audio service is directly connected to the "Power" service. That's why the error "Server RPC is unavailable" pops up. Windows 7, notice, has significant differences in the administration of the system, more significant than the differences, say, Windows XP and Winodws 2000. In addition, it is recommended to check the presence of the Spoolss.exe and Spoolss.dll files in the C: \ Windows \ SYSTEM32 directory.