Veeam Agent for Microsoft Windows fails to start due to a port conflict

KB ID: 2332
Product: Veeam Agent for Microsoft Windows | 2.0 | 2.1 | 2.2 | 3.0.2 | 4.0 | 5.0
Published: 2017-09-07
Last Modified: 2021-08-05
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

Veeam Agent for Microsoft Windows backup job ​with the following error message:
Error: The remote procedure call failed and did not execute RPC function call failed. Function name: [GetSvcVersion]. Target machine: [xxx.xxx.xxx.xxx]

Cause

This error message relates to a failure to establish communication with the Veeam Agent for Microsoft Windows service. If the Veeam Agent for Microsoft Windows service is confirmed as running, there may be a firewall issue.

This article specifically documents a situation in which the Veeam Agent for Microsoft Windows service cannot start, or gets stuck starting, due to a port conflict.

The Veeam Agent for Microsoft Windows service default is port 6183. As the service starts it will check if that port is in use, and if in use the service will increment and check again (6184,6185, etc.). It will attempt to increment up to 10 times before failing. (Logging example available below)

A much rarer scenario is one in which the port Veeam Agent for Microsoft Windows service attempts to start on is registered in RPC Endpoint mapper by another process but is not actively in use. The service will not detect the port as in use and attempt to start, it will fail to start and will not increment the port it attempts to start on.

Veeam Agent for Microsoft Windows service log location and example

Logging for the Veeam Agent for Microsoft Windows service can be found in:

%ProgramData%\Veeam\Endpoint\Svc.VeeamEndpointBackup.log

Below is an example of the service attempting to start on port 6183 and retrying 10 times to find an available port.

Info     [EpSystemTransportService] Trying to find usable port.
Info     [EpSystemTransportService] Trying to open tcp channel on port = 6183.
Info     [EpSystemTransportService] Unable to open tcp channel on port = 6183. Only one usage of each socket address (protocol/network address/port) is normally permitted
Info     [EpSystemTransportService] Retrying 1/10
Info     [EpSystemTransportService] Trying to open tcp channel on port = 6184.
Info     [EpSystemTransportService] Unable to open tcp channel on port = 6184. Only one usage of each socket address (protocol/network address/port) is normally permitted
Info     [EpSystemTransportService] Retrying 2/10
Info     [EpSystemTransportService] Trying to open tcp channel on port = 6185.
Info     [EpSystemTransportService] Unable to open tcp channel on port = 6185. Only one usage of each socket address (protocol/network address/port) is normally permitted
Info     [EpSystemTransportService] Retrying 3/10
Info     [EpSystemTransportService] Trying to open tcp channel on port = 6186.
Info     [EpSystemTransportService] Unable to open tcp channel on port = 6186. Only one usage of each socket address (protocol/network address/port) is normally permitted
Info     [EpSystemTransportService] Retrying 4/10
Info     [EpSystemTransportService] Trying to open tcp channel on port = 6187.
Info     [EpSystemTransportService] Unable to open tcp channel on port = 6187. Only one usage of each socket address (protocol/network address/port) is normally permitted
Info     [EpSystemTransportService] Retrying 5/10
Info     [EpSystemTransportService] Trying to open tcp channel on port = 6188.
Info     [EpSystemTransportService] Unable to open tcp channel on port = 6188. Only one usage of each socket address (protocol/network address/port) is normally permitted
Info     [EpSystemTransportService] Retrying 6/10
Info     [EpSystemTransportService] Trying to open tcp channel on port = 6189.
Info     [EpSystemTransportService] Unable to open tcp channel on port = 6189. Only one usage of each socket address (protocol/network address/port) is normally permitted
Info     [EpSystemTransportService] Retrying 7/10
Info     [EpSystemTransportService] Trying to open tcp channel on port = 6190.
Info     [EpSystemTransportService] Unable to open tcp channel on port = 6190. Only one usage of each socket address (protocol/network address/port) is normally permitted
Info     [EpSystemTransportService] Retrying 8/10
Info     [EpSystemTransportService] Trying to open tcp channel on port = 6191.
Info     [EpSystemTransportService] Unable to open tcp channel on port = 6191. Only one usage of each socket address (protocol/network address/port) is normally permitted
Info     [EpSystemTransportService] Retrying 9/10
Info     [EpSystemTransportService] Trying to open tcp channel on port = 6192.
Info     [EpSystemTransportService] Unable to open tcp channel on port = 6192. Only one usage of each socket address (protocol/network address/port) is normally permitted
Info     [EpSystemTransportService] Retrying 10/10
Info     [EpSystemTransportService] Trying to open tcp channel on port = 6193.
Info     [EpSystemTransportService] Unable to open tcp channel on port = 6193. Only one usage of each socket address (protocol/network address/port) is normally permitted

Solution

The following registry value may be used to force the Veeam Agent for Microsoft Windows service to start on a specific port.

This registry value should be created on the machine where Veeam Agent for Microsoft Windows is installed.

Key Location: HKLM\SOFTWARE\Veeam\Veeam Endpoint Backup\
Value Name: EndPoint_Rpc_Transport_Port
Value Type: DWORD (32-bit) Value
Value Data(Dec): <available_port>*

*For the Value data, specify an available idle port.

Start the Veeam Agent for Microsoft Windows service after putting the registry value in place.
If the service is stuck in a starting state, forcibly stop the service process.

Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.