RPC server unavailable



Getting error while executing flow. “RPC server unavailable”, How to resolve this error

RPC server is unavailable error

Can you provide more details on when this error occurs for you?
It doesn’t sound related to UiPath.

For starters you can check:



Yes i also thinks that it is related with virtual machines and remote machines remote procedure call errors.so please check logs and also tell us error what you are getting?
In what scenario you are working like on remote machines or local systems? Explain little bit more :slight_smile:



This problem occurs because of a mismatch in the computer name and the name that the RPC service expects.

Possible Solution - Cross verify the name of Virtual Machine with the one in UiPath


Getting this error while ececuting the Macro Activity. Any solution ?


Also receiving error “The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)” when executing the Excel Application Scope activity.

Error only appeared today after creating a new Excel Application Scope in my exiting workflow. Other Excel Application Scope activities in the workflow work fine.

UiPath is installed on a Windows 2012 R2 Amazon AWS EC2 instance.

Unsure why the new Excel Application Scope activity produces this error while the other same activities in the workflow do not.



I faced the same issue and I tried putting a delay of 3 seconds between two activities. It worked for me.
You can try it once too. :slight_smile:

Excel scope RPC server error

This worked for me as well.

Thanks for tip!


Same here ! Solved my problem, thanks for the tip.

Any other way to work around the problem without delaying the flow ?


The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

@CBahim @pavelhotovec @nesachdeva @BoCoNdOn @rupeshkumar.shah @Vikas.Jain @aksh1yadav @andrzej.kniola @srupesh1906

Hi all, we have been encountering this error today and the delay wasn’t working between scope activities. If you are encountering it when trying to interact with multiple files sequentially, the solution is to add a “close application” activity between each scope. This should eliminate the error - UI Path was struggling to close each file before opening the next and causing some sort of server clash.