RPC Error 1722: RPC Server Unavailable

[gabe.lorusso]

I started this trip down the road of migrating from StorageCraft to Veeam Agent for Windows. After installing and setting up a case with Veeam (case: 02309618) I'm unable to get any backup job to complete due to the RPC service being unavailable. I have confirmed that RPC and it's dependencies are running and functional, Domain services are healthy, registry matches other clean servers and still no answer. I have created an online support case with Microsoft which directed me to this forum. The below are the the links I have followed for troubleshooting and still cannot backup my server.

post252677.html?hilit=RPC%20unavailable#p252677
https://www.veeam.com/kb1174
https://www.drivereasy.com/knowledge/rp ... -10-fixed/
https://social.technet.microsoft.com/wi ... lable.aspx

In hopes that it was a transport problem I decided to install the full B&R on the server to have the transport service installed but that even fails due to RPC problems.

Any help or suggestions would be greatly appreciated.

[Mike Resseler]

Hi Gabriel,

First: Welcome to the forums!
Second: I see you have created a support case, but that it is waiting for your acceptance but it is obviously not . It will be rather difficult for us here to troubleshoot this (RPC errors can really be a lot of things...) so I would advise you to take that support ID you have, and maybe escalate it. You shouldn't be afraid of doing this

Hope it helps
Mike

[gabe.lorusso]

Thank you Mike for the advice and I have just replied to the case owner to have the ticket escalated.

[gabe.lorusso]

Mike,

Adam with support was able to assist me in resolving this problem. It appears that the problem was "Direct Access" was enabled on this server since it is a server that has the Essentials Role installed and functioning. Direct Access uses the port range of 6001-47000 which is within the range that the Veeam Agent uses.

To resolve we change the registry key "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Agent Endpoint Backup\EndPoint_Rpc_Transport_Port" to 47002 and the job is now running successful now.

The KB article is https://www.veeam.com/kb2332 if you wanted the official information.

[u19208]

Looks like that case is once more supporting my Feature request to Change the Default port: veeam-agent-for-windows-f33/feature-req ... 45457.html
All that registry edits are just Workarounds, why not providing a real solution?