RPC Service not aviable

[jmai]

Hi,

we installed yesterday Veeam Endpoint Backup on our Exchange Server. It is running at 11pm but he show an error when its try to run.
We are not using the Backup and Recovery Repository as a target for Endpoint Backup.

Endpoint Backup shows:
Error: Der RPC-Server ist nicht verfügbar RPC function call failed. Function name: [GetSvcVersion]. Target machine: [127.0.0.1].

Translation:
Error: RPC Server is not available RPC function call failed. Function name: [GetSvcVersion]. Target machine: [127.0.0.1].

On other server it is running without any problem.

Greetings,
J.M.

[agolubnichy]

Hi J.M.,

I trust the RPC service is actually running? Also, is there any antivirus software installed on the affected machine?

You are welcome to create a support case from Veeam Endpoint Backup UI > Support > Technical Support. Our technicians will analyze your logs and contact you with troubleshooting recommendations.

Kind regards,
Alexey

[Mike Resseler]

Hi J.M.,

I know it is an exchange server so you likely won't like to do it, but did you already restarted? I have seen cases where we got this error after installation but the problem (RPC) was there already for a longer time. A simple reboot can fix this in many cases. (but not always). In that case, following Alexey's advice is the best you can do

Cheers

Mike

[jmai]

I've restarted the server two times without any effect. But it looks like that the server means that he has no internet access, which is wrong. At the moment the backup ist working, but i've changed nothing...so it looks like magic

[Dima P.]

I am glad to hear you are up and running now. Next time please do not forget to create a support case - it will help us to identify the root cause of the issue and further improve the solution

[mrburritoman]

I am also having this issue on an Exchange server.

Operating System: Server 2012 R2
Exchange 2013

Code: Select all

Full Error:
3/30/2016 11:24:55 PM :: Error: The RPC server is unavailable RPC function call failed. Function name: [GetSvcVersion]. Target machine: [127.0.0.1]. 

No amount of restarts have been able to get this server to backup.

Anyone have an idea?

[Vitaliy S.]

Do you see any RPC related errors in the Windows Event log?

[Dima P.]

Hi mrburritoman,

In addition, this might be possible solution. If that does not help, kindly, open a support case via Control Panel > Support > Technical Support. Thanks.

[mrburritoman]

Do you see any RPC related errors in the Windows Event log?

Nothing in the event log.

Hi mrburritoman,

In addition, this might be possible solution. If that does not help, kindly, open a support case via Control Panel > Support > Technical Support. Thanks.

Checking this link out, how do I determine if the Veeam Transport component is missing?

I will open a support case and report back what is done to resolve this.

[Dima P.]

mrburritoman,

Thanks for the heads up. Do not forget to share the case ID.

[mrburritoman]

Case # 01748343

[mrburritoman]

I forgot to mention that I have initially tried these steps:
1. Open up regedit
2. Locate the Path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Backup 3. Add the following DWORD: EndPoint_Rpc_Transport_Port and change the value to 6183 (decimal).
4. Close regedit and restart the Veeam Endpoint service.

And the backup job has run successfully. I will monitor this over the next week to ensure that it remains stable.

[Dima P.]

Hi mrburritoman,

Thanks for the heads-up. I'll talk to the support team - probably we should create a KB article for future references.

[mrburritoman]

An update, this has been running properly for the past few weeks and it failed last night with the same error.

Restarting the service seems to have resolved it for now, just be aware that this pops up at random times...

[Mike Resseler]

Hi Mrburritoman,

Thanks for the heads up, we will pass this additional (valuable) information to our support teams

Thanks

Mike

[Geko Service]

I forgot to mention that I have initially tried these steps:
1. Open up regedit
2. Locate the Path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Backup 3. Add the following DWORD: EndPoint_Rpc_Transport_Port and change the value to 6183 (decimal).
4. Close regedit and restart the Veeam Endpoint service.

And the backup job has run successfully. I will monitor this over the next week to ensure that it remains stable.

Great, this solution worked for me on an Exchange server 2013 running on 2012 r2 server.
Thank you very much !!

[jmai]

Hi there,

the problem is back, nd nothing has helped yet to bring the backup to running succeful.

We updates our Exchange 2013 Server with the CU14 update, since them the Veeam Backup isnt working.

In the Eventlog we get two errors:

Code: Select all

[b]ID 190 - Source Veeam Endpoint Backup[/b]
EndpointBackup job 'Backup Job EXCHANGE' finished with Failed.
Job details: Error: Der RPC-Server ist nicht verf�gbar
RPC function call failed. Function name: [GetSvcVersion]. Target machine: [127.0.0.1].
Job has been stopped with failures. Name: [Backup Job EXCHANGE], JobId: [a2d5a3d2-7e31-4d26-96a2-ea2ebc41b6b7] Error: Der RPC-Server ist nicht verf�gbar
RPC function call failed. Function name: [GetSvcVersion]. Target machine: [127.0.0.1].

[b]ID 1020 - Source MSExchangeFrontEndTransport[/b]
The account 'NT AUTHORITY\ANONYMOUS LOGON' provided valid credentials, but is not authorized to use the server; failing authentication.

The Error with the ID 190 is coming 5sec after the one with the ID1020. Everytime when i try to get a backup this happens.
We havent changed the permission fo the Account NT AUTHORITY\ANONYMOUS LOGON.

Get-ReceiveConnector "Default Frontend EXCHANGE (25)" | Get-ADPermission -User "NT-AUTORITÄT\ANONYMOUS-ANMELDUNG" shows the following:
EXCHANGE\Default ... NT-AUTORITÄT\ANON... False False
EXCHANGE\Default ... NT-AUTORITÄT\ANON... False False
EXCHANGE\Default ... NT-AUTORITÄT\ANON... False False
EXCHANGE\Default ... NT-AUTORITÄT\ANON... False False
EXCHANGE\Default ... NT-AUTORITÄT\ANON... False False
EXCHANGE\Default ... NT-AUTORITÄT\ANON... False True
EXCHANGE\Default ... NT-AUTORITÄT\ANON... False True
EXCHANGE\Default ... NT-AUTORITÄT\ANON... False True
EXCHANGE\Default ... NT-AUTORITÄT\ANON... False True

Regards...

[Dima P.]

Hi jmai,

Did you open a support case?

[jmai]

Net yet, last time i resolved the problem without it.

[Dima P.]

If previously suggested solution to add DWORD: EndPoint_Rpc_Transport_Port with 6183 (decimal) value does not help, kindly, open a case and share the case ID in this thread. Thanks

[jmai]

I've opend a case (02008566), but after some windows updates and a new restart of the server the problem is gone and the backup is working again.

[jsdumont]

I got the same problem after installing Veeam Agent for Microsoft Windows (2.0.0.700) and found out the service hostcontrollerservice.exe (which is an Exchange service) is already listening on port 6183. We are at Exchange version 2016 U4. I know I can change the port VEB is listening but since 6183 is already taken by Exchange, which one I can use?

Thanks

[skochetkov]

I got the same problem after installing Veeam Agent for Microsoft Windows (2.0.0.700) and found out the service hostcontrollerservice.exe (which is an Exchange service) is already listening on port 6183. We are at Exchange version 2016 U4. I know I can change the port VEB is listening but since 6183 is already taken by Exchange, which one I can use?

Thanks

Hello!

You can use 6184 for example if it's not used by another process.

[Fabian C.]

Hello,

I had exactly the same problem with the port 6183 it was used by Exchange 2016 RC5 !
At the installation time to port 6183 was not in use, but after a restart this port was used by exchange 2016 U5.

Had to change it to 6184 for the Veeam service to start.

May be worth checking Exchange 2016 TCP port range in use to avoid "random" lock of the engine after a server restart.

Regards,

[Dima P.]

Hi Fabian,

Thanks, a lot for sharing your solution with the community. Thumbs up!

[Fabian C.]

The exchange 2016 service that is listening to the port 6183 is Microsoft.Exchange.Search.Service.exe

[Driehl]

I just ran into this issue on a 2012 R2 server running Exchange 2016 CU5. 6183 and 6184 did not work. I managed to get it working on 6185. Is there any issue using 6185?

[Mike Resseler]

Hi Dave,

No, if 6185 is free then you can use that. Could you find out what service is using 6184? (Just to see if we need to take into account another exchange service...)

Thanks
Mike