Also worth mentioning that clicking ‘Refresh’ when it displays the list of components to be upgraded, before clicking ‘Apply’ shows a slightly different (but I think related) error : “rServer] Failed to search installed package. This action is only valid for products that are currently installed”.

I would first try a clean install to see if that works and then restore your configuration backup if needed.   If that does not work then I would go directly to support to open a case. They will be able to help easier and check all the logs.  Let us know how it goes.

Thanks Chris, 

Yea I tried a clean install, uninstalled all veeam components, related files and folders, cleaned registry, restarted backup server, then restored config from the configuration backup and got same error. Also tried adding the managed server before restoring the config backup and got “Failed to search components”. 

I’ll try and raise a case with Veeam support, and update here if I get a response, thanks.

So is the issue the server you’re trying to add to VBR then?...and, in wanting to upgrade the compnents (Services) on it? Or, are you having trouble upgrading VBR itself?

If just having issue upgrading/installing a Managed Server, if you have it...try reinstalling whatever older version of the Transport/Data Mover and Installer Services on it directly from the ISO, then see if you can add it to VBR and/or Upgrade it. Once the older versioned ISO is unpacked, the standalone installers should be in the Packages folder → VeeamInstallerSvc.msi ; VeeamTransport.msi 

Hopefully that helps. Let me know if I misunderstand where the issue it.

Best.

Thanks ​@coolsport00 ,

So yea I previously had veeam 10 installed on both backup and managed servers. Then I upgraded to version 12.3 and selected to automatically upgrade components on the managed server as well. Then I started getting the error when launching the veeam console and upgrading components on the managed server. I also did a clean reinstall on the backup server but no difference. 

Are you suggesting downgrading components on the managed server back to version 10 ? I thought might be an issue with the version mismatch, but I can certainly give that a try.

You cannot go to 12 from 10 you need to hit a v11 version first.  That is more than likely your issue.

Hi Chris,

Yes I read that from documentation. So I did the upgrade to v11 and started getting the error there. Then did a backup of the configuration and uninstalled everything as suggested here . Then installed v12.3 and restored the backup configuration. And still got the error. 

Hi ​@VeeamStormguard -

At this point, since you’ve done about all we can suggest to do...i.e. even to the point of clean (re)install, it’s best to get ahold of Support. If you’re not able to uninstall the components on the managed server(s) and install the ‘old Veeam components’, then upgrade them. Something in your config DB (it appears) may be causing the issue. Maybe Support can help with a script of sorts to traverse your config DB to remove the problem table(s)/components in there to then enable you to add your managed server(s) properly.

Keep us posted.

Best.

Yes but I am not sure that a v10 configuration backup can restore to v12 either.  Again you need the previous release.  As Shane stated we have helped as best we can so support is the best step now.

No worries. Yea I’ve launched a case with support. Just waiting to hear from them.. then I’ll update here, thanks.

Hopefully they get you sorted out let us know. Good luck. 

https://www.veeam.com/kb4661

Should help if it’s really about Windows desktop edition instead of Server.

Thanks ​@ddomask ,

Gave it a try and still getting the error, though I agree might be OS related (windows 10).

I just installed this standalones to my server and everything worked perfectly, thank you!

Glad my suggestion worked for you ​@ITstg 

Great to hear that worked for you ​@ITstg