Aug 29, 2019 Most RPC server errors occur within one computer, but the cause of the problem can be something on that computer or something in the network as a whole. I’ll show you how to figure out both kinds of problems in this article. RPC server unavailable errors. So what would cause an “RPC server unavailable” error? If you are a Windows user, there is a high probability you have encountered an “RPC server is unavailable” error. Here is how to fix it.
I have observed the similar situation couple of times in the past one year. Everything is normal from event viewer, server component state, service status, database copy health but the database activation will fail every time when I try to activate it from one of the nodes in 4 node DAG cluster. The databases are easy to do all possible operations in other 3 nodes, but one node. The issue occurs after a reboot, but will not resolve even if we wait for so longer or do another round of reboot.
Errors received are listed below,
An Active Manager operation failed. Error: The database action failed. Error: An error occurred while trying to validate the specified database copy for possible activation. Error:
SERVER:
A server-side administrative operation has failed. The Microsoft Exchange Replication service may not be running on server server.domain.local. Specific RPC error message: Error 0x6ba (The RPC server is unavailable) from cli_RpcsGetCopyStatusWithHealthState [Server: server.domain.local]
Failed to mount database ' DB01'. Error: An Active Manager operation failed. Error: The database action failed. Error: The Microsoft Exchange Replication service may not be running on server server.domain.local. Specific RPC error message: Error 0x6ba (The RPC server is unavailable) from cli_AmMountDatabaseDirect3 [Database: DB01, Server: PAM Server]
The error is very common, and you will be flooded with multiple resolutions however all will have longer procedure such as (not limited to),
- Verify the health of AD
- Look at the event log for AD replication errors
- Check the integrity of database
- Verify the cluster quorum status
- And so on
Solution Worked for me (both occasions):
Try to move the PAM to different healthy node available in the DAG (not to the activation failed server), and try to repeat the operations. When you only have 2 node DAG, you may have no choice other than trying other possible solutions as we mentioned earlier this post. However, it is worth checking if you have more than one IP assigned to the DAG members in the production network range.
Move-ClusterGroup 'Cluster Group' -Node NODENAME
Verify the PAM role has moved post the above command,
Once you confirm that the PAM role is currently hold by another healthy node, try to mount/activate database on server where we observed issues. It should just work fine!
Additional Info: I found this when we use more than one IP Address assigned a single network card on Exchange for relay/HA purposes. If we reassign the IPs to other nodes of the cluster, a communication gap between PAM and the node can occur. But, there are no harm in moving the PAM before you take major steps to make the cluster communication restored.
-Praveen
When you attempt to run the System File Checker (sfc.exe /scannow command) to restore missing or corrupted system files, the following error message may be seen:
Windows File Protection could not be initiate a scan of protected system files.
The specific code is 0x000006ba [The RPC Server is unavailable.]
This happens if the Windows File Protection (WFP) is disabled in the registry.
Editor’s Note: If you’ve used nLite to build custom Windows installation package, you may have enabled the Disable SFC (File Protection) checkbox, which disables WFP and the System File Checker.
Enable the System File Checker
Use the following steps to re-enable WFP.
1. Click Start, Run. Type Regedit.exe and press ENTER.
2. Navigate to the following branch:
HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows NT CurrentVersion Winlogon
3. Double-click SFCDisable and set its Value data to 0
4. Exit the Registry Editor and restart Windows.
Registry Fix
Download sfcenable.zip and run the attached REG file. Restart Windows for the change to take effect.
One small request: If you liked this post, please share this?
One 'tiny' share from you would seriously help a lot with the growth of this blog.Some great suggestions:
Pin it!
Share it to your favorite blog + Facebook, Reddit
Tweet it!
So thank you so much for your support, my reader. It won't take more than 10 seconds of your time. The share buttons are right below. :)
You'd like to read these articles:
About the author
Ramesh Srinivasan founded Winhelponline.com back in 2005. He is passionate about Microsoft technologies and he has been a Microsoft Most Valuable Professional (MVP) for 10 consecutive years from 2003 to 2012.