OPERATIONAL DEFECT DATABASE
...
...
After changing the hostname of the Veeam Backup Server, the Veeam Backup & Replication Console fails to connect, displaying the error: No connection could be made because the target machine actively refused it 127.0.0.1. Make sure the backup server you are connecting with is X.Y version. The error message displayed by the Veeam Backup & Replication Console mentions a potential version incompatibility because the console assumes that it cannot contact port 9420 because the wrong version is installed. In fact, the reason it cannot reach port 9420 is that the Veeam Backup Service service has failed to start.
The Veeam Backup Service is failing to start and, consequently, preventing the Veeam Backup & Replication Console from connecting because the configuration database connection settings are set to connect to the SQL Server instance using the old hostname, which has been changed.
To correct this issue, follow the steps below to update the Veeam Backup & Replication configuration to use either localhost or the new hostname: Open the Configuration Database Connection Settings program, which should appear in the start menu of the Veeam Backup & Replication server. Within this program, select Veeam Backup and Replication, then click Next.(If Enterprise Manager is not installed, you will not be prompted to select a product.) Adjust the value specified in the Server name field to match the correct hostname.Note: Use either localhost or the new hostname. Click Next, and Veeam will connect to the database. Wait for this process to complete.
If you have any problems following these steps, please contact Veeam Support. Troubleshooting for issues opening the console when the hostname has not changed are available in KB2127. Hostname changes of other devices, such as hypervisors, repositories, or proxies, require additional steps covered in KB1905.
Click on a version to see all relevant bugs
Veeam Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
