“RPC server is unavailable” - causes and solutions to the error. "RPC Server Unavailable" Error on Windows - What to Do Replication Error 1722

Undoubtedly, for many users the seventh Windows versions Have you ever seen the error message “RPC server is unavailable” on your monitor or laptop screen? What kind of failure this is and how to fix it will now be discussed.

The 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 remote procedure call service.

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

"RPC Server Unavailable" Error: Problems with Dynamic Libraries

So, let's see what can be done to correct 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 in which the system is installed.

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

Crash with "RPC Server Unavailable" message Windows 7: Starting a service from the command line

To begin with, the most simple method The solution to the situation is to start the service from command line. At this stage, we believe that everything is fine with the files themselves.

Call the command line (cmd) from the “Run” menu (Win + R) and then write there net command start rpcss. If everything is fine with the service itself, after rebooting 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, select a similar command, only with the word stop) . If the above method for some reason did not activate the service, you will have to take, so to speak, a roundabout route.

Fixing the error using original libraries

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

However, after this, 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. You can do this from the Control Panel, but it is much easier to use special team services.msc, which is listed in the same “Run” menu.

In the editor itself, you should find the remote procedure call (RPC) service and click on startup, then select “Automatic” in the startup type. After saving the changed parameters, as in the first case, you will need to completely reboot the system for them to take effect.

Note: After rebooting, it is advisable to run the system update in manual mode and install the latest update packages. This can play a key role in the correct activation of the service. Along the way Special attention pay attention to the system in which the original files will be copied, at least take into account its capacity.

Comprehensive solution using special utilities

Basically, if you can copy or download original files no, you can do it in a simpler way.

Utilities like DLL Suite will help correct the situation, which automatically scans the system for damaged or missing components, and then independently integrates the missing objects into it. However, we cannot limit ourselves to this alone. At the end of the process, you will still need to make sure that the service is in an active state (enabled) and running smoothly. This is done as was shown just above.

Conclusion

That's all there is to it regarding 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 the Driver Booster program or something else.

As for correcting the situation with the service itself, issues related to verification were not considered here computer systems for viruses. Also, methods for enabling (activating) the service were not provided, for example in the settings 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 will want to delve into them, otherwise, what good, the entire system can be “imprisoned.”

Otherwise, no user should have any problems. Everyone decides for themselves exactly what to do and which method to use, 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 applied if the simplest way has no effect on the system. And, of course, if you discover that files are damaged or 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, which will download the missing files and integrate them into the system without user participation. In fact, this is exactly what they were developed for.

RPC is a way of exchanging information between processes or between a client (the device that initiates the RPC communication) and a server (the device that communicates with it) on a network or system. Many built-in Windows components use RPC, which uses different ports as the starting point for communication between systems. If a problem occurs, the message "RPC Server Unavailable" appears.

Solving the "RPC Server Unavailable" error.

In a typical RPC session, the client contacts the mapper endpoints server on TCP port 135 and for the specified service requires specific number dynamic port. The server responds by sending the IP address and port number for which the service is registered in the RPC after it has started, and then contacts the client with the specified IP address and port number. Possible reasons The "RPC Server is unavailable" errors are as follows:

Stopping the RPC service – when the RPC service on the server is not running.
Name resolution problems - The RPC server name may be associated with an incorrect IP address. This means that the client is contacting the wrong server or is trying to contact an IP address that is not currently in use. Perhaps the server name is not recognized at all.
Traffic blocked by firewall—A firewall or other security application on the server, or a device firewall between the client and server, may be preventing traffic from reaching the server's TCP port 135.
Connectivity Issues – This could be the reason why there is no connection between the client and the server.

Solutions

When you run or install some programs, you may receive the message “The RPC Server is unavailable.” This is often due to the time synchronization required to run the program. Without this, some applications may not work correctly or may not launch at all. We'll look at what to do to stop the message from appearing again below.

Error code 1722

Error 1722 "PRC Server Unavailable" may occur when using network printer or sound devices in the seventh version of Windows. The reason may be an antivirus program blocking communication ports - to eliminate it, you need to find the settings for managing trusted programs in the antivirus settings.

Also, the error may occur due to the fact that the virus itself is present in the system - it is worth checking the system and disk using a different antivirus program than currently used. To resolve, click Start/Settings/Control Panel. Then open Administration/Services. A window will appear in which you will find “Server” on the right side. On “Server”, check if the automatic startup type is enabled. Change the setting if necessary and restart your computer.

Disable Windows Firewall

If you receive an "RPC Server Unavailable" error when printing in Windows 7, the problem may be a firewall issue. It is responsible for blocking access to a computer on an internal or external network by unauthorized persons or applications, which eliminates the possibility of controlling the PC. Below are some tips that will allow you to disable (in case you want to use another application for this) and enable the integrated Windows Firewall. Change the computer name using Settings:

This is one of the easiest ways to disable your network firewall. To do this, use the "System Settings" tab.
From the list available options select Network & Internet.
Go to the Ethernet tab and select "Windows Firewall" on the right side of the window.
Choose to turn the firewall on or off.
From the list of available operations, select the Turn off Windows Firewall option (not recommended).
Click OK. The firewall is turned off.

The next method is the Local Group Policy Editor (GPO):

Press Win + R keys and enter "gpedit.msc". The Local Group Policy Editor will open.
The setting responsible for disabling the firewall is located at

“Computer Configuration” – “Administrative Templates” – “Network” – “Network Connections” – “Standard Profile” – “Windows Firewall: Protect all network connections.”

Change the setting status to "OFF".
Once you click OK or Apply, Windows Firewall will stop working.

For more advanced users, the above script can be executed using Registry Editor.

click start and type “regedit”, run the application as administrator;
in the editor window find the directory

HKLM\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile;

find the EnableFirewall parameter and change its value from 1 to 0;
in the same way edit the EnableFirewall key in the following directory

HKLM\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\PublicProfile;

and the last directory with the EnableFirewall key

HKLM\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile.

Close Registry Editor and restart your computer. From this point on, Windows Firewall is disabled. To enable the firewall again using Registry Editor, simply change the above values called EnableFirewall from 0 to 1, and restart your computer.

Manually running the services.msc task

When you run or install some programs, you may receive the message “The RPC Server is unavailable.” This is often due to the time synchronization required to run the program. Without this, some applications may not work correctly or may not launch at all. If the function is unavailable, a crash may occur; to fix it, you need to enable the synchronization service:

First, click the “Start” menu and type “Run” in the search bar, press “Enter”;
in the next window, enter services.msc and confirm with the “OK” button;
Find the item “Windows Time Service” in the list;
double click this service. A menu will open in which you must click the “Run” button.

From now on, the “RPC server is unavailable” message should not appear.

Troubleshooting Windows

The built-in system troubleshooter will help you fix the error in Windows 10. Restart your computer and after the beep sounds, press the F8 button once per second until the boot options menu opens. The first one will be “Troubleshoot your computer.” Select this action and wait for the operation to complete.

Error in FineReader

The problem may occur in Windows 8 and higher and when trying to start the ABBYY FineReader Licensing Service. To check the status in the list of services (how to find it is described above), select ABBYY FineReader Licensing Service. In the Properties window, make sure the Startup Type option is set to Automatic. Change it if necessary, close the editor with the "OK" button and restart your computer.

Virus check

In Windows XP and higher, the error message may be caused by a virus. Scan your PC with antivirus program, following the instructions of the master. In Windows 10, you can use the standard Defender. To do this, click right click mouse on the “Shield” icon near the clock and select “Open”. Run a virus scan by clicking the corresponding button in the window.

As you can see, there are many ways to get rid of the error. This list contains the most likely options for fixing the error. If necessary, you will have to reinstall the operating system using the installation disk.

Hello.

the problem is this
there is a server running Windows Server 2008 Std
The server performs the role of AD and DNS

there are errors in the logs

" Error processing Group Policy. The computer name could not be resolved. Possible reasons:

a) Name resolution error on the current domain controller.
b) Active Directory replication lag (created on another domain controller Account has not yet replicated to the current domain controller)."

"The DNS server is unable to listen on the TCP socket at 192.168.1.75. The event data contains an error code. IP address 0.0.0.0 may indicate a valid "any address" in which all configured IP addresses for the computer are available for use.
Restart your DNS server or restart your computer."

What to look for? Thank you

c:\>dcdiag

Directory Server Diagnostics

Performing initial setup:
Trying to find the main server...
Main server= MATRIX1
Directory binding error 1722:
The RPC server is unavailable.
This may limit some of the checks that can be performed.
* AD forest identified.
Initial data collection is complete.

Perform mandatory initial checks

Run test: Connectivity
DsBindWithSpnEx() function failed with error 1722,
The RPC server is unavailable..
........................ MATRIX1 - Connectivity check failed

Performing Basic Checks

Verification Server: Default-First-Site-Name\MATRIX1
Skipping all checks because MATRIX1 server is not responding
directory services.

Performing partition checks on: ForestDnsZones

CheckSDRefDom

........................ ForestDnsZones - verified
CrossRefValidation

Perform partition checks on: DomainDnsZones
Run the check: CheckSDRefDom

CheckSDRefDom
Running the validation: CrossRefValidation
........................ DomainDnsZones - verified
CrossRefValidation

Performing partition checks on: Schema
Run the check: CheckSDRefDom
........................ Schema - CheckSDRefDom check passed
Running the validation: CrossRefValidation
........................ Schema - check passed
CrossRefValidation

Performing partition checks on: Configuration
Run the check: CheckSDRefDom

CheckSDRefDom
Running the validation: CrossRefValidation
........................ Configuration - verification passed
CrossRefValidation

Perform partition checks on: EGAIS
Run the check: CheckSDRefDom
........................ EGAIS - CheckSDRefDom check passed
Running the validation: CrossRefValidation
........................ EGAIS - verified by CrossRefValidation

Performing enterprise checks on: EGAIS.local
Running a check: LocatorCheck
........................ EGAIS.local - LocatorCheck passed
Running a scan: Intersite
........................ EGAIS.local - Intersite check passed

C:\Users\Administrator>ipconfig /all

Setting up the IP protocol for Windows

Computer name. . . . . . . . . : MATRIX1
Primary DNS suffix. . . . . . : EGAIS.local
Node type. . . . . . . . . . . . . : Hybrid
IP routing is enabled. . . . : No
WINS proxy is enabled. . . . . . . : No
Order in which DNS suffixes are viewed. : EGAIS.local

Ethernet adapter Connection via local network 2:

n#2
Physical adress. . . . . . . . . : 00-1E-67-22-91-D1
DHCP is enabled. . . . . . . . . . . : Yes

Ethernet adapter Connection via local network:

DNS suffix of the connection. . . . . :
Description. . . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connectio
n
Physical adress. . . . . . . . . : 00-1E-67-22-91-D0

Auto-tuning is enabled. . . . . . : Yes
IPv4 address. . . . . . . . . . . . : 192.168.1.75(Main)
Subnet mask. . . . . . . . . . : 255.255.255.0
Main gate. . . . . . . . . : 192.168.1.1
DNS servers. . . . . . . . . . . : 192.168.1.75
NetBios over TCP/IP. . . . . . . . : Included

Tunnel adapter LAN connection* 8:

Media condition. . . . . . . . : Media disabled
DNS suffix of the connection. . . . . :
Description. . . . . . . . . . . . . : isatap.(746B47FD-7AB0-4B0D-98FE-4DB2E19EC
1DB)

DHCP is enabled. . . . . . . . . . . : No
Auto-tuning is enabled. . . . . . : Yes

Tunnel adapter LAN connection* 9:

Media condition. . . . . . . . : Media disabled
DNS suffix of the connection. . . . . :
Description. . . . . . . . . . . . . : isatap.(D3F5E70A-76D0-4007-B912-38442938A
700}
Physical adress. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP is enabled. . . . . . . . . . . : No
Auto-tuning is enabled. . . . . . : Yes

Sometimes you need to print an important document on a printer, and when you print a request, you receive the message “RPC Server is unavailable,” and clarifying error codes are also often indicated (1722, 0x800706ba, 0x000006ba). The most common failure occurs in Windows XP/7/10 when printing to a printer or using the ABBYY Finereader application. Users should first understand the causes of such a conflict in order to understand what should be done to correct it.

Reasons for the error

It becomes obvious that the computer has recently been integrated with a new device (printer, network connection). Apparently, something went wrong when updating the drivers, resulting in an error when exchanging protocols. You should also make sure that all RPC service databases are available; they can sometimes spontaneously turn off or become damaged during PC overloads. Other drivers with incorrect installation may also become a separate problem, most often this applies to the video card. Dangerous virus programs very often disguise themselves as an RPC service, disabling the main service, which makes it impossible for it to work normally.

How to fix "RPC Server Unavailable"

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

Disabled RPC service

The first option is to check whether the RPC service is disabled. Sometimes the service is simply turned off randomly or is inactive by default. That is, all the files are on the computer, but are simply not accessible to operating system when printing documents. Services must be activated using the command line.

Missing or broken files

RPC has two most important files and a lot depends on their operation. One of them is Spoolss.dll, related to DLLs, and the other is Spoolss.exe (spoolsv is signed on the computer). If they work incorrectly or are in a changed state, the error will constantly appear. Changes may have been accidentally made by users or virus program, which very often disrupt 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 – “SYSTEM32” folder. The main thing is to make sure that the OS bit depth matches, because for x64 the folder Windows destinations- "SysWOW64".

Also, library data can be found and downloaded on the Internet:

And finally, video instructions for solving the problem by changing options Windows startup in "System Configurations".

Conclusion

The appearance of an RPC server error in Windows XP/7/10 (when printing or the ABBYY Finereader application) does not require restoring or reinstalling the OS and can be completely resolved easy methods. It is not necessary, but it is highly advisable to always scan your PC for Trojans. Install from the site Microsoft latest official updates, which contain solutions to many bugs and system vulnerabilities.

Undoubtedly, many users of the seventh version of Windows have seen the error message “RPC Server is unavailable” on their monitor or laptop screen. What kind of failure this is and how to fix it will now be discussed.

The 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 remote procedure call service.

"RPC Server Unavailable" Error: Problems with Dynamic Libraries

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

Crash with "RPC Server Unavailable" message Windows 7: Starting a service from the command line

To begin with, the easiest method to correct the situation is to start the service from the command line. At this stage, we believe that everything is fine with the files themselves.

Call the command line (cmd) from the “Run” menu (Win + R) and then enter the command net start rpcss there. If everything is fine with the service itself, after rebooting 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, select a similar command, only with the word stop) . If the above method for some reason did not activate the service, you will have to take, so to speak, a roundabout route.

Fixing the error using original libraries

However, after this, 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 command services.msc, which is written in the same “Run” menu.

Note: after rebooting, it is advisable to run 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 capacity.

Comprehensive solution using special utilities

In principle, if there is no way to copy or download original files, you can do it in a simpler way.

Conclusion

As for correcting the situation with the service itself, issues related to scanning computer systems for viruses were not considered here. Also, methods for enabling (activating) the service were not provided, for example, in group policy settings or by changing the corresponding parameters of system registry keys, since such a technique is much more complicated than what was described above. And not every user will want to delve into them, otherwise, what good, the entire system can be “imprisoned.”

Otherwise, no user should have any problems. Everyone decides for themselves exactly what to do and which method to use, 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 discover that files are damaged or 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 participation. In fact, this is exactly what they were developed for.