Operational Defect Database
BugZero found this defect 3156 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb2065
RPC function call failed. Function name: [GetSvcVersion]
Last update date:
7/18/2023
Affected products:
Veeam Backup & Replication
Affected releases:
11
Fixed releases:
No fixed releases provided.
Description:
Challenge
Veeam Backup & Replication fails to communicate with a managed remote machine with the error:
Cause
Veeam Backup & Replication is unable to reach the Veeam Installer Service on the remote machine.
Solution
Managed Server Reinitilization Procedure To force Veeam Backup & Replication to reinitialize the connection to a managed server, edit the managed server within the Veeam Backup & Replication console and proceed through all steps of the Edit Server wizard. An error message at any step in the wizard may help indicate the underlying issue preventing communication. Edit the managed server listed in the error. Click Next through each step of the Edit Server wizard. If an error is shown, note what it says and refer to the Possible Errors and Causes list below. If no errors occur and the Apply tab successfully completes the infrastructure item update process, retest the task or job that initially displayed the GetSvcVersion error. Possible Errors and Causes The user name or password is incorrect. This error indicates that Veeam Backup & Replication was able to contact the guest OS of the remote machine, but the remote machine refused the connection reporting that the credentials provided were invalid. A supplied password or user name is incorrect. This error indicates that Veeam Backup & Replication was able to contact the guest OS of the remote machine, but the remote machine refused the connection reporting that the credentials provided were invalid. Network path not found, or invalid credentials supplied. Veeam Backup & Replication could not contact the remote machine's guest OS. Either it is not running, or a firewall is blocking communication. This error specifically indicates that the Veeam Backup Server was unable to contact the Veeam Installer Server on the remote machine over port 6160, and when that failed, it was also unable to connect to the admin$ share on the remote machine. Unable to establish connection to host <machine_name> on any IP address. This indicates that Veeam Backup & Replication could not reach the remote machine via SSH over port 22. This error may be expected when using a hardened Linux repository with SSH intentionally turned off. Failed to check whether remote Installer service is available. This error indicates that Veeam Backup & Replication was able to connect to the remote machine successfully. It found that the Veeam Installer Service was installed and was able to start the Service but was unable to connect to it. This may occur if another process is listening on port 6160 or a firewall is blocking communication. If an error other than these is shown, immediately collect the Satellite_Console.log from: C:\ProgramData\Veeam\Backup\Satellites\VBR\<user>\ Assuming the last action taken was having Veeam Backup & Replication attempt to connect to the managed server, the last few entries in the log will contain details about the attempted connection and why it failed. Please provide this log file to Veeam Support for assistance.
More Information
When creating a support case for assistance with this error, please manually collect logs from the remote machine and attach them to the case. If the Veeam Installer Service cannot be contacted, the log collection tool built-in to Veeam Backup & Replication will not be able to collect the logs itself. Windows Default Log Location: %programdata%\Veeam\Backup\ Linux Default Log Location: /var/log/VeeamBackup/
