Host-based backup of Microsoft Hyper-V VMs.
Post Reply
mkaec
Veteran
Posts: 484
Liked: 146 times
Joined: Jul 16, 2015 1:31 pm
Full Name: Marc K
Contact:

Detecting previously installed components Timeout

Post by mkaec »

After updating B&R from 12.x to the latest version of 13.x the backup server could not upgrade the components on two of the Hyper-V servers. I was getting timeouts in both the upgrade wizard and in the Properties of the Hyper-V Server in Backup infrastructure. The message was slightly different in each. One was Detecting previously installed components. I don't remember what the other variation of the message was.

The solution was to stop the Veeam Installer Service service on each Hyper-V server with the problem and then run the following in an elevated command prompt:

Code: Select all

sc delete VeeamDeploymentService
I didn't have to do anything after that. B&R must have been in a loop trying to remotely upgrade the components. Once the service was deleted, it came back (with newer file dates) and the servers disappeared from the Needs Upgrade and Unavailable categories.

I guess the Veeam Installer Service was old and v13 of B&R didn't want to talk to it (or vice versa).
david.domask
Product Manager
Posts: 3416
Liked: 809 times
Joined: Jun 28, 2016 12:12 pm
Contact:

Re: Detecting previously installed components Timeout

Post by david.domask »

Hi mkaec,

Sorry to hear about the challenges and thanks for sharing the solution.

Looks like it's similar to the issue described in KB2263, so solution is valid. The timeouts are unexpected however as this process should have been automated; if root cause analysis is required, please open a Support Case and export logs from the Backup server itself for review.
David Domask | Product Management: Principal Analyst
Post Reply

Who is online

Users browsing this forum: No registered users and 4 guests