#1 Global Leader in Data Protection & Ransomware Recovery

Veeam Backup & Replication Console Fails to Open After a Hostname Change

KB ID: 2350
Product: Veeam Backup & Replication | 10 | 11
Published: 2017-10-05
Last Modified: 2022-10-04
mailbox
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.

Article Applicability

This article is specifically regarding the Veeam Backup & Replication console failing to connect after the Veeam Backup Server's hostname has been changed.

The error shown in the Cause section of this article may occur due to other reasons, which are documented in KB2127.

Challenge

After changing the hostname of the Veeam Backup Server, the Veeam Backup & Replication Console fails to connect, displaying the error:
Failed to connect to the Veeam Backup & Replication server:
No connection could be made because the target machine actively refused it <IP>:9392
Screenshot of console error

When this occurs, the Veeam Backup Service will be stopped and cannot be started. The diagnostic logging on the Veeam Backup Server will contain the following messages, which show that the server is attempting to connect to the previous hostname.

%programdata%\Veeam\Backup\Svc.VeeamBackup.log:

Info [DB] Connecting to SQL Server (CurrentUser=[NT AUTHORITY\SYSTEM], ServerInstance=[<OldHostname>\<SQLInstanceName>], Options=[Direct])
Info [DB|ERROR] Failed to connect to server

Solution

To correct this issue, update the Veeam Backup & Replication configuration with the current hostname by following these steps:

  1. Open the Configuration Database Connection Settings program, which should appear in the start menu of the Veeam Backup & Replication server.
  2. 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.)
  3. Adjust the value specified in the Server name field to match the correct hostname.
  4. Click Next, and Veeam will connect to the database. Wait for this process to complete.
Screenshot of DB Config Tool
  1. Click Next, and the Veeam service will be started. When this has been completed, click Finish, then try accessing the Veeam Backup & Replication console.

More Information

  • 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.

To submit feedback regarding this article, please click this link: 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.

You have selected too large block!

Please try select less.

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.