System error 1722 rpc server unavailable. Meaning and elimination of the error "The RPC server is unavailable

Malfunctions of computers, laptop, tablet are very diverse and numerous. However, many of them in fact indicate not so much a breakdown or incorrect operation of the device as an error in communication or in access. The RPC server unavailable error falls into this category.

What will be discussed:

What is RPC Server

The functionality of any computer is determined by the quantity and quality of the programs used and, of course, by the version of the operating system. However, not all programs can be accommodated on one single device. It is much more rational to divide complex multi-stage tasks by distributing separate parts of it or even just frequently performed procedures in a common local space.

Sometimes this is not enough. In such cases, RPC services are used. This means that separate functions and procedures are located in different address spaces on remote computers. To get to them, contact the RPC server.

RPC technology has two components: a network protocol and an implementation language. Different implementations of remote procedure call have different architectures, use different protocols, but very rarely the HTTP protocol, since the latter is not transport. Accordingly, when transferring data from different machines using a different protocol, failures occur.

Features of the RPC

Implementing a remote call itself is more complex than calling local procedures. When setting up work both on the network and on individual computers, it is necessary to solve several different tasks:

when transferring data from different computers with different addresses, errors are always possible. The matter is aggravated if the machines use different operating systems - Windows 7, XP, or different architectures - big or big endian order. To compensate for the difference, the RPC parameters need to be copied from one machine to another and serialized;
a remote call assumes the use of a transport protocol, for example, TCP;
a procedure call both in local space and remotely for the user is implemented in one process. But in reality, the RPC server has 2 processes. As a result, if the calling procedure terminates abnormally, the called ones hang, which leads to the appearance of error 1722. If the called procedure terminates abnormally, the callers wait for a response to no avail. The "RPC server unavailable" option in Windows 7 most often has this origin;
the problem of compatibility of different operating environments, different data structures, different call structures has been broken so far. As a result, the "RPC server is unavailable" Windows is left with intermittent errors that you have to deal with yourself or with someone else's help.

What to do if there is no remote call?

First of all, you need to try to establish the reason for the refusal. This is not always possible, but if it works, it greatly facilitates the matter. The procedure is the same for all OS versions.

In the Start menu find "Control Panel".
Events are viewed in the administration tab. If the RPC server unavailable error was the last event, then the error code in the log is at the top of the list. In the photo - work in the OS to eliminate the failure.
On the network, the description of the event and the recommended actions to eliminate the failure are found by the code.

Checking the Windows XP system with an antivirus

If the problem cannot be eliminated in this way, checking the Windows XP system with an antivirus can help: in some cases, the failure of a remote call is associated with the activity of the Conficker worm.

This option occurs quite often. It is connected with the installation of the program - especially for working with printers, with updating the driver, sometimes it occurs when the system boots. In Windows XP, it occurs even when upgrading from SP2 to SP3. In version 7, the printer may be unavailable due to the lack of sound.

In particular, owners of Canon printers often complain about the appearance of error 1772.

In such cases, it is recommended to first check XP or another version for viruses. If the scan does not give any results, take the following actions.
Under the administrator account, the status of a number of services is checked:
- print manager;
- remote procedure call;
- nutrition;
- DCOM server launcher.
- You must enable all of these services if they have been disabled, then go to the Start menu, to the Run section and type services.mcs into the command line.
Thus, they go to the properties of all the services listed above, where you can change their parameters.
After completing all the checks, be sure to restart the computer. If, after a restart, printing continues and error 1722, the RPC server is not available does not occur. So the problem has been fixed.

Another possible option for OS versions from Windows Ultimate and higher is a failure due to attempts to encrypt through the Bitlocker utility. In this case, you need to download the fix from the website. Microsoft.

The RPC server is not available on Windows 10, 7 and 8 may be related to sound as the Audio service options are related to power service. In such cases, go through the "Start" in the "Control Panel", find the tab "Administrative Tools" and "Services". From here, the building of the service endpoints is started.

Restoration of performance

What to do if antivirus software does not help? This option is possible if the virus has infected the system after the last partition was saved. In such cases, you can try to reanimate the SYSTEM registry.

At the address Windows \ System32 \ Config are included in the directory of saved versions - RegBack. From here they copy the System file and place it in the Config folder, thus replacing the damaged one.

Windows 10 and 8 have a Recovery Console. With its help, you can restore the registry using the advanced options menu.

Sometimes you need to print an important document on a printer, and you receive the message "RPC server unavailable" for your print request, and more often specify error codes (1722, 0x800706ba, 0x000006ba). The most common crash occurs in Windows XP / 7/10 when printing to a printer or using ABBYY Finereader. Users should first understand the causes of such a conflict in order to understand what should be done to fix it.

Reasons for the error

The recent integration of the computer with a new device (printer, network connection) is becoming apparent. Apparently, when updating the drivers, something went wrong, as a result of which an error occurred during the exchange of protocols. You should also make sure that all databases of the RPC service are present, they can sometimes spontaneously shut down or become damaged during PC overloads. Other drivers with incorrect installation can also become a separate problem, more often it refers to the video card. Dangerous virus programs very often disguise themselves as an RPC service, disabling the main service, which makes it impossible to work in normal mode.

How to fix "RPC server is unavailable"

To correct a printing error, start with the simplest. We will show you how to step by step apply the most effective methods of solving the problem.

Disabled RPC service

The first option is to check if the RPC service is disabled. Sometimes the service simply shuts down in random order or is inactive by default. That is, all files are on the computer, but simply not available for the operating system when printing documents. Services must be activated using the command line.

Missing or broken files

RPC has two main files and a lot depends on how they work. One of them is Spoolss.dll, which is related to DLL libraries, and the other is Spoolss.exe (signed by spoolsv on the computer). If they do not work properly or have a changed state, the error will constantly appear. Changes could be accidentally made by users or a virus program that very often disrupts the normal operation of services.

You can use a similar Windows 7, for example. From it you need to extract the above files and insert them into your system along the path: Drive C - Windows - folder "SYSTEM32". The main thing is to make sure that the bitness of the OS is correct, because for x64 the Windows destination folder is "SysWOW64".

Also, these libraries can be found and downloaded on the Web:

And finally, a video instruction on how to solve the problem by changing the Windows startup options in the "System Configurations".

Conclusion

The appearance of an RPC server error in Windows XP / 7/10 (when printing or using ABBYY Finereader) does not require OS recovery or reinstallation and can be solved with quite easy methods. It is not necessary, but highly desirable to always scan your PC for Trojans. Install the latest official updates from the Microsoft website, which contain solutions to many bugs and system vulnerabilities.

Undoubtedly, many Windows 7 users have seen the error message "RPC server unavailable" on their monitor or laptop screen. What kind of failure it is and how to fix it will now be discussed.

Most Common RPC Server Failure Situation

When a message appears that the RPC server is unavailable, in general, it does not mean the server itself. This is actually a RPC service.

And, as a rule, this error most often appears when manipulating printers, for example, when trying to print a document or simply installing (adding) a new printer. And the point here is not even in the device itself, but in the service, which for some reason stopped working or is simply in a disabled state.

RPC Server Unavailable Error: DLL Issues

So let's see what we can do to fix the situation. First, you need to make sure that the system has the dynamic library file Spoolss.dll and the executable component Spoolss.exe. They should be located in the System32 directory of the main directory where the system is installed.

If such files are present, there can be at least two options for failure: either they are damaged, or the service is simply not started.

Failure with "RPC Server Unavailable" Windows 7: Start Service from Command Prompt

To begin with, the easiest way to fix the situation is to start the service from the command line. At this stage, we believe that everything is in order with the files themselves.

We call the command line (cmd) from the Run menu (Win + R) and then write the net start rpcss command there. If everything is fine with the service itself, after restarting the computer terminal (which, by the way, is mandatory), the problem will disappear, and the message that the RPC server is unavailable will no longer bother the user (to stop the service, a similar command is selected, only with the word stop) ... If the above method did not activate the service for some reason, you will have to go, so to speak, in a roundabout way.

Bug fix using original libraries

Now let's look at the situation when the above files are damaged or missing. In principle, you can do the simplest way: copy them from a similar system (from another computer), and then paste them into the System32 system folder.

However, after that, so that the message that the RPC server is unavailable does not appear again, you will need to take a few more important steps and first go to the services section. This can be done from the Control Panel, but it is much easier to use the special services.msc command, which is registered in the same Run menu.

In the editor itself, you should find the remote procedure call (RPC) service and click on autoload, then specify "Automatic" in the startup type. After saving the changed parameters, as in the first case, you will need to perform a complete reboot of the system for them to take effect.

Note: after rebooting, it is advisable to start the system update manually and install the latest update packages. This can play a key role in the correct activation of the service. Along the way, pay special attention to the system in which the original files will be copied, at least take into account its bit depth.

Complex solution using special utilities

Basically, if there is no way to copy or download the original files, you can do it in an easier way.

Utilities like DLL Suite will help to correct the situation, which automatically scan the system for damaged or missing components, and then independently integrate the missing objects into it. However, this cannot be limited only to this. At the end of the process, you will still need to make sure that the service is in an active state (enabled) and works without failures. This is done as shown above.

Conclusion

That's all there is to the problem with the RPC service. As you can see, there is nothing wrong with such a failure, and the solution to the issue looks quite simple. The only other thing worth noting is installing new or updating existing printer drivers. Of course, this is not a prerequisite, however, it would be very desirable to carry out such a procedure. This can be done either from the Device Manager, or using specially developed utilities like Driver Booster or something else.

As for correcting the situation with the service itself, issues related to scanning computer systems for viruses were not considered here. Also, methods of enabling (activating) the service were not provided, for example, in the settings of group policies or by changing the corresponding parameters of the system registry keys, since this technique is much more complicated than what was described above. And not every user wants to dig into them, otherwise, what good, you can "plant" the entire system.

Otherwise, no user should have any problems. How exactly to proceed, which method to use, everyone decides for himself, but, as practice shows, the easiest way is to activate the service from the command line (provided that the necessary files are in order). The method of restoring files and activating this system component from the services section can be used if the simplest method does not have any effect on the system. And, of course, if you find that the files are damaged or are simply missing from the system, it is better not to copy them from another device, but if you have an active Internet connection, use automatic utilities that will download the missing files and integrate them into the system without user intervention. Actually, this is exactly what they were developed for.

Undoubtedly, many Windows 7 users have seen the error message "RPC server unavailable" on their monitor or laptop screen. What kind of failure it is and how to fix it will now be discussed.

Most Common RPC Server Failure Situation

When a message appears that the RPC server is unavailable, in general, it does not mean the server itself. This is actually a RPC service.

RPC Server Unavailable Error: DLL Issues

If such files are present, there can be at least two options for failure: either they are damaged, or the service is simply not started.

Failure with "RPC Server Unavailable" Windows 7: Start Service from Command Prompt

To begin with, the easiest way to fix the situation is to start the service from the command line. At this stage, we believe that everything is in order with the files themselves.

Bug fix using original libraries

Complex solution using special utilities

Basically, if there is no way to copy or download the original files, you can do it in an easier way.

Conclusion

Third-party software can significantly expand the capabilities of the operating system, but even the most advanced programs cannot turn a computer into a universal device. There are tasks that cannot be performed with a single PC due to hardware limitations. For example, to output data to analog print, you need a fundamentally different device - a printer.

Therefore, to solve complex multistage tasks, computers and other devices are often combined into networks, where each component does its own part of the work. Such interaction can be carried out within the framework of different technologies, for example, the RPC technology, which will be discussed today. Rather, the conversation will be about the common error associated with it "RPC server is unavailable". But before proceeding directly to the analysis of solutions, let's say a few words about RPC itself.

What is RPC and how it works

RPC or remote procedure call can be described as a method of communication between devices, one of which is a client and the other is a server. Also, RPC is a network service designed to perform certain actions on remote devices or, as they say, other address spaces. Examples are sending data to and, which involves launching some programs on a managed computer.

RPC technology is represented by two basic components - a network protocol and a programming language that provides serialization of objects and structures. In this case, different protocols can be used, for example, the most common protocols are UDP and TCP. The interaction of devices within the framework of RPC occurs through the exchange of packets through the corresponding port. If this chain of actions fails, the service responds with an "RPC server unavailable" error.

When the RPC error appears

In most cases, the error occurs on the server side, but it is not uncommon for users of client machines to encounter it. You can determine the cause of the problem by analyzing the content. An error is often caused by an abnormal termination of the connection procedure, software incompatibility, difference in data structures, installation or updating of various programs and drivers, encryption, and disabling of a number of services.

The source of the problem can also be the blocking of traffic by a firewall or antivirus; it cannot be ruled out that a computer is infected with a virus. But let's take everything in order, consider the most common causes of the error in a little more detail.

How to find the reason

In general terms, the RPC server is unavailable. It is impossible to establish communication between devices, but what to do in such cases? As already mentioned, to find out the cause of the error, use the Event Log, which opens with the command eventvwr.msc... RPC-related crashes are located in the System section, and if you start viewing the Log immediately after the error appears, then its description will be at the very top. You can also use the search by filtering events by source. Further, it's a matter of technology - we look at the error code and search for a solution on the Internet.

The RPC server is unavailable. Error 1722

The most common RPC problem, usually occurring in Windows 7. Error 1722 The RPC server is unavailable in the G7, accompanied by no sound on the computer. Since there is a problem with a number of important services being disabled, the following solution is proposed. Open the Service Management snap-in, locate the Windows Audio Endpoint Builder service, and enable it if it is disabled. It is desirable to set the startup type to "Automatic".

At the same time, you should check the status of the services "Remote Registry", "Remote Procedure Call", "Power" and "Server". They should all work, and they should all be of the Automatic startup type. An error code 1722 appears with the description "RPC server is unavailable" not only in Windows 7, but also in Windows 10. The ways to fix it in different versions of the system are similar to those given above.

Printing errors

Error 1722 can also be associated with incorrect operation of applications that ensure the interaction of the computer with printers, which, again, is often caused by disabling services. If you receive the message “unable to print image RPC server unavailable” when printing, make sure you have Print Manager, DCOM Server Process Launcher, RPC, and Power Services enabled and running. ...

If everything is fine with the services, try disabling the firewall and antivirus for the duration of the session. It happens that the network connection is blocked by these protections. By the way, the "RPC server is unavailable" error with code 0x800706ba often indicates problems in the operation of a firewall between a computer and another device.

Conflict with FineReader

Cases of the error "RPC server unavailable" have been reported in Windows 10 and earlier versions of the system when the popular OCR application ABBYY FineReader is running. But it is not the application itself that is to blame, but rather its active background service, which somehow conflicts with the RPC mechanisms. Disable it for the duration of the session in the service management snap-in and check the result.

Virus infection

Infection of your computer with malware is another cause of an RPC server error. The fact that the PC is infected may be indirectly indicated by the absence of error records in the Windows Journal. The standard solution is to scan the computer with anti-virus applications.

Driver problems

If the RPC server becomes unavailable when printing after updating the drivers for the video or audio card, printer, etc., there may be a conflict with the RPC mechanisms. In this case, you should roll back to the previous working versions of the drivers.

Violation of file integrity

If the computer has experienced a crash or virus attack, you should check the status of the two main RPC files - spoolsv.exe and spoolss.dll located in the system directory System32... If the files are missing, you must copy them from another computer with the same version of the operating system and drop them into the System32 folder, and then start the remote call service manually from the service control snap-in. Alternatively, check the system for damaged and missing ones with the command sfc / scannow.

Damage to the registry

Sometimes problems are related to the registry. It is best to use a traditional rollback tool to fix the problem. Also you can copy from folder C: / Windows / System32 / config / RegBack the SYSTEM file and place it in the parent folder config with replacement. It is desirable to perform this operation from under the LiveCD.

conclusions

An RPC server unavailable error on local computers can usually be resolved by activating all necessary services or by restoring files and registry (if there were any failures). One of the solutions to the problem is also to update Windows to a newer version. As for the same error on servers, everything can be much more complicated here, however, ordinary users will hardly have to face a similar situation, since this business usually falls on the shoulders of system administrators.