Repair VBR Installation

[Joao Izidoro]

Hello! I know I shouldn't have done this.

Support case: 07855583

I have (had) VBR community installed in one of our VMs, when suddenly after a restart the Veeam Backup Service couldn't start anymore.
I figured I should reinstall VBR, since previously I had tried upgrading it from 12.3.2.3617 to the latest release and it also kept failing, which gave me the impression of some sort of corruption.

I tried uninstalling it via control panel, however it kept giving this error "The feature you are trying to use is on a CD-ROM or other removable disk that is not available".
I tried running the newest ISO and getting the plugins that were missing from there however it didn't work, so I tried deleting Veeam manually.

I erased most folders containing Veeam files, like "program files/veeam", "program data/veeam", "program files/common files/veeam", "program files x86/common files/veeam". I also tried running Microsoft's uninstall troubleshooter, which helped me delete some other stuff but not everything.
As a last resort I tried removing the registry keys containing Veeam, or some sort of Product Code I got from running the ISO's "/backup/Server .64.msi" with logging.

Now when I run the ISO's Setup.exe I get the error "An error has occurred: This action is only valid for products that are currently installed", and when I run the Server msi I get "Failed to execute .NET assembly" and then "In-place ugprade is supported starting from version 11a or later". I can install some stuff, like the catalog, but I can't get it to reinstall Veeam.

Am I missing some files or registry keys? Is there a way to log those missing files from a run? I know I should have contacted support before I tried doing things manually, but I didn't think about this then.

[Mildur]

Hi João,

Unfortunately, we cannot provide technical assistance for such issues through this forum.
If it still doesn’t work on the original VM, consider deploying a new Windows VM with the latest backup server version.
You can import the existing backup files and map them to new backup jobs to continue your backup chains.

Thank you,
Fabian