For some reason, if you ended up using the Windows Logs in Event Viewer or trying to install SCCM 2012 R2 on your domain. You must have encountered Error 1723 The RPC Server Is Too Busy To Complete This Operation Error’. According to this error, when the RPC application tries to reach a server, it appears to be busy, or the server is lacking memory resources. The error is seen in the windows server. With this error, you can’t install or run a few of the essential apps and services of the system. Fortunately, we have gathered some methods that you can use to resolve this issue.
Causes of The RPC Server is too Busy to Complete this Operation Error:
As the introductory part clears out that due to a lack of memory resources, this error occurs. Apart from this third party application, viruses or unwanted background can cause this error. Error 1723 The RPC Server is too Busy to Complete this Operation error appears while installing SCCM, Event viewer, or Services.
- Multiple Background processes and services running
- Low RAM
- Malware or virus attack
- Third-party application
Similar Types of The RPC Server is too Busy to Complete this Operation Error:
- Event id 5014 error 1723
- The directory service is too busy to complete the replication
- Rpc server is unavailable server 2008
- Domain controller
- Remote shutdown
- 1723 event viewer
- Error 1723 The RPC Server is too Busy to Complete this Operation Bitlocker
- Error 1723 domain controller
- Event id 5014 error 1723
How to Fix & Solve The RPC Server is too Busy to Complete this Operation Error
To fix Error 1723 the RPC Server Is Too Busy To Complete This Operation Error. The following are the methods that you can use to fix the issue. In the first method, we will talk about some basic troubleshooting techniques. In the second method, we will make sure that essential services are up and running. In the third method, we will remove the error by tweaking the registry. Let’s proceed to each way in more detail.
1. Basic Troubleshooting –
Instead of jumping onto the other methods, make sure that you follow this Error 1723 The RPC Server is too Busy to Complete this Operation SBS 2008 method first. If you get this error, the first thing you need to do is to give your system a restart. Restarting will re-run the services and process. After that, stop all the unused and unwanted background processes. Thirdly perform a clean boot.
2. Starting the Remote Registry Service –
In this method, we will make sure that the remote registry service is running and up. Sometimes due to antivirus or third-party apps, the service gets closed or unresponsive, resulting in Error 1723 The RPC Server is too Busy to Complete this Operation avast error.
- STEP 1. Simultaneously hold Windows key + R to open the Run window
- STEP 2. Now, in the search field type services.msc and hit Enter
- STEP 3. Now in the services window Locate the Remote Registry service from the list
- STEP 4. Right-click on to the service and go to Properties
- STEP 5. Move to the Logon tab
- STEP 6. Now beside This Account field, put NT AUTHORITYLocalService
- STEP 5. Leave both the Password fields empty
- STEP 6. Finally, Click on Apply then OK
- STEP 7. Restart your system and check if avast The RPC Server is too Busy to Complete this Operation error still occurs
3. Tweaking the Registry Editor (GFI LanGuard Server) –
In this unable to start scan The RPC Server is too Busy to Complete this Operation error method; we will fix the issue with the registry. Make sure that you have tried all of the above methods. Be attentive while making changes in the registry wrong changes may lead to more errors and instability of the system.
- STEP 1. While in the GFI LanGuard server, open up the Registry Editor
- STEP 2. In the registry, window navigate to
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesLanmanWorkstationParameters
- STEP 3. Now Right Click on the Parameters and click Permissions
- STEP 4. In the Security tab make sure Everyone group has only read-only permissions
- STEP 5. Ultimately other than System account all other are set to read-only
- STEP 6. Make sure in the value valid character exists
- STEP7. Save all the changes and exit the registry window
- STEP 8. Finally, Reboot your system to get rid of remote shutdown The RPC Server is too Busy to Complete this Operation error.
Conclusion:
In this article, we have seen different methods by which we can fix Error 1723 The RPC Server Is Too Busy To Complete This Operation Error’. Furthermore, this article also gives brief information on the causes and how does it affect the system.
With this being the end of Error 1723 The RPC Server is too Busy to Complete this Operation error article; we conclude that by following the above methods, you can fix the issue in no time. For more troubleshooting articles follow us. Thank You!
- Remove From My Forums
-
Question
-
I have a applcation written in VC++6.0.
I have implemented the RPC mechanism.
I receive RPC error 1723.
I am trying to do the following thing:
Read the data of some file from Client computer and write it to server computer.
I have used threads here.
So that many clients can perform the above operation simulteneously on same server.
However, when 5-6 clients perform the above operation in loop(30 times).
Then the RPC Exception is thrown with error 1723.
Please help.
Regards,
Vishal
All replies
-
Open a Command Window (DOS window) and type «NET HELPMSG 1723».
What you’ll get will be «The RPC server is too busy to complete this operation.»
I’m not sure that’s tremendously informative but at least you know what 1723 is telling you.
-
You will get better help in the microsoft.public.platformsdk.networking newsgroup or in an appropriate forum in another web site such as CodeProject.com or CodeGuru.com. There are plenty of resources available about Network programming.
- Remove From My Forums
-
Question
-
We have a 2008 R2 server that is reporting RPC errors when trying to view the Windows Logs in Event Viewer. We have tried rebooting the server multiple times and when trying to clear the logs we receive a message saying «Event Viewer could not clear
the log. The following error occurred: The RPC server is too busy to complete this operation.» If we try to look at the Event Viewer remotely we see the error «The RPC server is too busy to complete this operation(1723)» When trying to log into
the server it takes MUCH longer to sign-in than usual. This is one of our domain controller servers. I have checked and replication is working without issue.
So, when running the Active Directory health script that is floating around, I noticed some concerning things. This is the result of the health check from the primary domain controller (DL-R710-01) (Yes, it’s an old server — but it’s under warranty and maintained and meets our needs:
And this is the results from the replication domain controller (DL-VM-01)
All very concerning! Everything is working, as far as I can tell and I’m not sure on how to go about best to resolve this. I’m still sort of new to debugging domain controllers themselves. Looking at Server Manager for the PDC I see the following errors:
Text
The DFS Replication service failed to contact domain controller to access configuration information. Replication is stopped. The service will try again during the next configuration polling cycle, which will occur in 60 minutes. This event can be caused by TCP/IP connectivity, firewall, Active Directory Domain Services, or DNS issues. Additional Information: Error: 160 (One or more arguments are not correct.)
AND:
Text
The DFS Replication service failed to communicate with partner DL-VM-01 for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server. Partner DNS Address: DL-VM-01.ad.mydomain.com Optional data if available: Partner WINS Address: DL-VM-01 Partner IP Address: 10.0.0.4 The service will retry the connection periodically. Additional Information: Error: 1722 (The RPC server is unavailable.) Connection ID: 6C1603C1-5EAE-40DD-B3AC-658837881BD4 Replication Group ID: 5CE4CB27-BF4F-4F10-A2A8-6727BE26C7D9
AND:
C++
The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.
Looking at Server Manager for the replication AD DC I see the following errors:
Text
The DFS Replication service is stopping communication with partner DL-R710-01 for replication group Domain System Volume due to an error. The service will retry the connection periodically. Additional Information: Error: 1723 (The RPC server is too busy to complete this operation.) Connection ID: D7277C3D-E8FB-425C-882C-B00B747A0D98 Replication Group ID: 5CE4CB27-BF4F-4F10-A2A8-6727BE26C7D9
AND: ——-
Text
The DFS Replication service encountered an error communicating with partner DL-R710-01 for replication group Domain System Volume. Partner DNS address: DL-R710-01.ad.mydomain.com Optional data if available: Partner WINS Address: DL-R710-01 Partner IP Address: 10.0.0.2 The service will retry the connection periodically. Additional Information: Error: 1726 (The remote procedure call failed.) Connection ID: D7277C3D-E8FB-425C-882C-B00B747A0D98 Replication Group ID: 5CE4CB27-BF4F-4F10-A2A8-6727BE26C7D9
AND: ——-
Text
The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error.
Both AD DC can ping each other, I don’t see any direct issues outputting GPOs or creating new accounts and authentication. Should I just promote a new VM replication AD DC and demote this one? I recently changed the timeservers because there was a time gap (using built in before) but other than that nothing has really changed.
Any help is appreciated!
-
#2
I’ve never seen that error message when trying to install Configuration Manager. What are the specifications of the server on which you are installing SCCM ?.
-
Thread Starter
-
#3
I followed your valuable tutorials and i succeeded for our LAB’s domain (windows 2012). and last week i try to install SCCM to my staff domain and then i am getting this error my Domain controller is windows 2008 R2. I used VM with 6 core processor , 16GB Memory, SAN storage, windows 2012 Datacenter
Thanks
Nirosha
-
#4
Most likely this can be issue with the storage. If you have got any other storage option you could give a try.
-
#5
Nirosha, Any update on Prajawal’s Suggestion ? Is that solved ?
-
Thread Starter
-
#7
final i finish it, just follow bellow steps if some one need to solve this problem
1.Type SERVICES.MSC in START or RUN dialog
2.Locate and double click on the REMOTE REGISTRY service from the list
3.Click On the LOG on tab
4.In the THIS ACCOUNT TEXT BOX,type in NT AUTHORITYLocal Service.
5. now, set the both password fields blank
6.Click APPLY,OK
Thanks
Nirosha
-
#8
Thanks Nirosha. Marking this thread as Solved.