Backup agent for Microsoft Windows servers and workstations (formerly Veeam Endpoint Backup FREE)
Geko Service
Lurker
Posts: 1
Liked: never
Joined: Nov 10, 2016 10:45 am
Full Name: Pierre-Edouard Hunkeler
Contact:

Re: RPC Service not aviable

Post by Geko Service » Nov 10, 2016 10:48 am

mrburritoman wrote: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
Service Provider
Posts: 8
Liked: 1 time
Joined: Oct 17, 2014 8:03 am
Full Name: J.Mai
Contact:

Re: RPC Service not aviable

Post by jmai » Dec 09, 2016 12:37 pm

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.
Veeam Software
Posts: 8590
Liked: 634 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: RPC Service not aviable

Post by Dima P. » Dec 09, 2016 1:12 pm

Hi jmai,

Did you open a support case?

jmai
Service Provider
Posts: 8
Liked: 1 time
Joined: Oct 17, 2014 8:03 am
Full Name: J.Mai
Contact:

Re: RPC Service not aviable

Post by jmai » Dec 09, 2016 1:17 pm

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

Dima P.
Veeam Software
Posts: 8590
Liked: 634 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: RPC Service not aviable

Post by Dima P. » Dec 09, 2016 3:20 pm

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
Service Provider
Posts: 8
Liked: 1 time
Joined: Oct 17, 2014 8:03 am
Full Name: J.Mai
Contact:

Re: RPC Service not aviable

Post by jmai » Dec 16, 2016 8:32 am

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
Novice
Posts: 6
Liked: never
Joined: Feb 08, 2017 9:27 pm
Full Name: Jean-Sébastien Dumont
Contact:

Re: RPC Service not aviable

Post by jsdumont » May 18, 2017 2:29 pm

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
Veeam Software
Posts: 24
Liked: 4 times
Joined: Feb 12, 2015 12:36 pm
Full Name: Sergey Kochetkov
Contact:

Re: RPC Service not aviable

Post by skochetkov » May 18, 2017 3:20 pm

jsdumont wrote: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.
Novice
Posts: 9
Liked: 1 time
Joined: Jun 07, 2017 8:45 pm
Contact:

Re: RPC Service not aviable

Post by Fabian C. » Jun 17, 2017 5:53 am 1 person likes this post

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.
Veeam Software
Posts: 8590
Liked: 634 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: RPC Service not aviable

Post by Dima P. » Jun 18, 2017 7:40 pm

Hi Fabian,

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

Fabian C.
Novice
Posts: 9
Liked: 1 time
Joined: Jun 07, 2017 8:45 pm
Contact:

Re: RPC Service not aviable

Post by Fabian C. » Jun 19, 2017 6:51 am

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

Driehl
Influencer
Posts: 10
Liked: never
Joined: Apr 20, 2017 6:03 pm
Full Name: Dave Riehl
Contact:

Re: RPC Service not aviable

Post by Driehl » Nov 28, 2017 5:09 am

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
Veeam Software
Posts: 4853
Liked: 509 times
Joined: Feb 08, 2013 3:08 pm
Full Name: Mike Resseler
Location: Belgium
Contact:

Re: RPC Service not aviable

Post by Mike Resseler » Nov 28, 2017 6:38 am

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

Post Reply

Who is online

Users browsing this forum: No registered users and 16 guests