Full Uninstalling Veeam Endpoint Backup Free

[ej_r]

I've been reading another subject about full uninstalling Veeam Endpoint Backup Free, however it's not really clear for me.

Reading the Help Center topics:

Uninstalling Veeam Endpoint Backup

The LocalDB and other prerequisite components installed and used by Veeam Endpoint Backup are not removed during the uninstall process. To remove each of the the remaining components, right-click it in the programs list and select Uninstall.

Installing Veeam Endpoint Backup in Unattended Mode

During the product installation, Veeam Endpoint Backup automatically sets up the following required prerequisite components:
▪Microsoft SQL Server System CLR Types for SQL Server 2012
▪Microsoft SQL Server 2012 Management Objects
▪Microsoft SQL Server 2012 Express LocalDB Edition

I've uninstalled the Veeam Endpoint Backup program.
- Can I just uninstall the Microsoft SQL programs (prerequisite components) without any issue?
- What about the LocalDB, can it be removed and if, how?

Thanks for the help!
Erik

[Dima P.]

Hi Eric,

Can I just uninstall the Microsoft SQL programs (prerequisite components) without any issue?

Yes, if you don’t have other applications using SQL components.

The leftovers can be found in C:\ProgramData\Veeam folder and if you want to clean up the registry, delete this registry branch HKEY_LOCAL_MACHINE\SOFTWARE\Veeam

P.S. Make sure that you don’t have other Veeam products installed on this machine. Thanks

[SoulSherpa]

I'd like a clean slate. Installing on 2012 R2.

I've followed the instructions in these posts:
http://forums.veeam.com/veeam-endpoint- ... ml#p133833
veeam-endpoint-backup-f33/full-uninstal ... 34855.html

Including:

• Uninstall Veeam
  Delete VeeamEndPoint SQL instance
  Uninstall SQL components
  Delete any remaining Veeam folders in Program Files and ProgramData
  Delete HKEY_LOCAL_MACHINE\SOFTWARE\Veeam
  Reboot

When I reinstall, all previous settings, job histories, registered USB devices, etc. remain present. What does it take to fully remove for a fully clean install?

What's the status of the built-in complete uninstall option announced on Feb 16, 2015?

Thank you.

[Dima P.]

Hi SoulSherpa,

Complete uninstall, including SQL components, may break other apps that rely on this components. May I ask why you want to completely reinstall VEB?

If you want to purge the job settings and backup sessions, follow the workaround described below:

1. Go to Control panel > Administrative Tools and run Services. Stop the Veeam Endpoint Backup service.
2. Run regedit.exe and locate the HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Backup key. Create the following value under this key:
Name = Recreatedatabase
Type = DWORD
Value = 1
3. Start Veeam Endpoint Backup service
4. Allow some time for the new database instance to be created (5 minutes should be enough).
5. Stop Veeam Endpoint Backup service
6. Run regedit.exe and delete the Recreatedatabase value from HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Backup key.

[SoulSherpa]

Thanks, Dima,

To answer your question: I'm testing and evaluating the product. Discovering what works well and what doesn't for my environment. Your product installed MS SQL Express, and is the only product using it.

Earlier this weekend, I did eventually find a reference to the registry key you've provided. It worked perfectly. I did notice that the registry key already existed with a value of "0" when I started the process, and that it reset itself to "0" after the db reset completed.

Please consider a more intuitive method to evoke this process. Thank you for your help; have a great week.

[Dima P.]

We will discuss the more convenient approach with the team for sure. Thanks for the feedback!

[tinkererguy]

I agree that it would be helpful if db resets were a little easier to do, especially since I found myself doing them often enough that I documented the process for myself, and for others, with a walk-thru video:
How to manually reset your Veeam Endpoint Backup FREE database
https://TinkerTry.com/veeam-endpoint-ba ... base-reset

[Dima P.]

Hi Paul,

Thanks for sharing, as usual well explained, perfectly written and makes total sense

[tinkererguy]

That could be because you wrote it.
Thanks, Dima. P!

[JChris]

Veeam should really implement a way to ENTIRELY remove Veeam and it's features/DBs. It's very troublesome to completely uninstall it -.-

[Vitaliy S.]

Usually DB is uninstalled in a separate process to allow migrations or complete re-install without any historical data loss, but thanks for the feedback!

[hnmr]

Hello,

once again I am experiencing troubles installing the current version of Veeam Agent for Microsoft Windows Free.
It is very similar to my previous issue from here: veeam-agent-for-windows-f33/unable-to-u ... 49966.html This time it is getting worse because I can't find the old installation file.

In short: I can't install the new version 3.0.2.1170 on my Windows 10 system. Neither the upgrade of the previous version worked. Then I removed the old version, but the installation of the new package neither worked.

I see the following lines in the installation log file:

Code: Select all

Action 01:08:17: VeeamEndpointValidateInstalledVersionAction. Checking upgrade possibility...
***Veeam***  Setup was unable to check installed version. Error code: 0x00000645.
Action 01:08:17: . 
CustomAction VeeamEndpointValidateInstalledVersionAction returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 01:08:17: VeeamEndpointValidateInstalledVersionAction. Return value 3.
MSI (c) (B4:A0) [01:08:17:254]: Doing action: SetupCompleteError

I can't remove the old versions of SharedManagementObjects, SqlLocalDB and SQLSysClrTypes, because the installer asks me to provide the msi packages that I don't have anymore. Although I could install the new versions of these 3 packages taken from them install directory of VeeamAgentWindows_3.0.2.1170_.zip in addition to the old ones. But it didn't help. Veeam fails to install.

Now I stuck. The worst thing is that I have already removed the previous version of Veeam Agent for Microsoft Windows Free (I am not sure but it should have been once from 2018). At the moment no backup and it makes me very concerned.
Any ideas?

Best regards
Hermann

[Egor Yakovlev]

Hi Hermann,
please check tricks above to have a cleanup on Agent components.
/Cheers!

[hnmr]

Hi Egor,

I couldn't find any helpful information in the other thread. I did find a similar error report in the forum, though.
What I have done now:
I have uninstalled everything SQL-related on the computer and cleaned up the registry as good as I could. Also I have removed everything under C:\ProgramData\Veeam but VeeamBackup.mdf and VeeamBackup_log.ldf in C:\ProgramData\Veeam.bak\EndpointData and thus renamed the directory in C:\ProgramData\Veeam.1. Rebooted.
The same result unfortunately.

The setup routine stops right after the start, the log file under C:\ProgramData\Veeam\Setup\Temp shows as much:

Code: Select all

2019-12-19 13:10:11 [INFO ] Bootstrapper execution - started.
2019-12-19 13:10:11 [INFO ] Commandline processing - started.
2019-12-19 13:10:11 [INFO ] Commandline option: SfxPackage; Value: c:\Users\hermann\Downloads\VeeamAgentWindows_3.0.2.1170.exe
2019-12-19 13:10:11 [INFO ] Commandline option: silent; Value: 
2019-12-19 13:10:11 [INFO ] Commandline option: accepteula; Value: 
2019-12-19 13:10:11 [INFO ] Commandline option: acceptthirdpartylicenses; Value: 
2019-12-19 13:10:11 [INFO ] Commandline processing - finished.
2019-12-19 13:10:11 [INFO ] Initializing.
2019-12-19 13:10:11 [INFO ] Initialization - finished. Starting bootstrap engine.
2019-12-19 13:10:11 [INFO ] Bootstrapper engine execution started.
2019-12-19 13:10:11 [INFO ] Checking required conditions.
2019-12-19 13:10:11 [INFO ] Performing condition check: Only this setup instance is running.
2019-12-19 13:10:11 [INFO ] Mutex1 = Global\5997E3B8-6B78-43E9-A7BC-F2F9C691E0A0, Mutex2 = Global\173C0D79-5D2D-41DF-A746-28D967D96EA0
2019-12-19 13:10:11 [INFO ] Condition check - passed.
2019-12-19 13:10:11 [INFO ] Performing condition check: Elevated privileges.
2019-12-19 13:10:11 [INFO ] Condition check - passed.
2019-12-19 13:10:11 [INFO ] Performing condition check: OS version.
2019-12-19 13:10:11 [INFO ] OS version check function execution started.
2019-12-19 13:10:11 [INFO ] Warning! Setup application should not be launched in compatibility mode.
2019-12-19 13:10:11 [INFO ] Condition check - passed.
2019-12-19 13:10:11 [INFO ] Performing condition check: Installed products.
2019-12-19 13:10:11 [UI MESSAGE] Message was suppressed due to silent mode. Message: Failed to initialize setup program. Refer to setup logs for details.
2019-12-19 13:10:11 [UI MESSAGE] Interaction result: OK
2019-12-19 13:10:11 [ERROR] Bootstrapper has encountered a problem. Error details: Dieser Vorgang ist nur für Produkte gültig, die zurzeit installiert sind.

If I run msiexec /i "Veeam_B&R_Endpoint_x64.msi" /l c:\temp\install.log writing the protocol in a log file, it says:

Code: Select all

=== Logging started: 19.12.2019  13:44:09 ===
Action 13:44:09: INSTALL. 
Action start 13:44:09: INSTALL.
Action 13:44:09: IsUserAdmin. 
Action start 13:44:09: IsUserAdmin.
Action 13:44:09: VmaIsUserAdmin. Verifing user's administrator group membership...
Action 13:44:09: . 
Action ended 13:44:09: IsUserAdmin. Return value 1.
Action 13:44:09: ISSetAllUsers. 
Action start 13:44:09: ISSetAllUsers.
InstallShield 13:44:09: Begin SetAllUsers()
InstallShield 13:44:09: Getting records from Upgrade table
InstallShield 13:44:09: UpgradeCode: {77AC4198-A66C-45EB-A79C-4708A954ED71}	MinVersion: 	MaxVersion: 3.0.2.1170	Language: 	Attributes: 257
InstallShield 13:44:09: Checking related product {B642A42A-CF16-4FF8-8C19-CE1CB812B1C1}
InstallShield 13:44:09: 		{B642A42A-CF16-4FF8-8C19-CE1CB812B1C1}			 ***Related***
InstallShield 13:44:09: No related products for UpgradeCode {77AC4198-A66C-45EB-A79C-4708A954ED71} found
InstallShield 13:44:09: UpgradeCode: {77AC4198-A66C-45EB-A79C-4708A954ED71}	MinVersion: 3.0.2.1170	MaxVersion: 	Language: 	Attributes: 2
InstallShield 13:44:09: Checking related product {B642A42A-CF16-4FF8-8C19-CE1CB812B1C1}
InstallShield 13:44:09: No related products for UpgradeCode {77AC4198-A66C-45EB-A79C-4708A954ED71} found
InstallShield 13:44:09: End SetAllUsers()
Action ended 13:44:09: ISSetAllUsers. Return value 1.
Action 13:44:09: AppSearch. Searching for installed applications
Action start 13:44:09: AppSearch.
AppSearch: Property: DOTNETVERSION20, Signature: DotNet20
AppSearch: Property: RECOVERYMEDIAVERSION64, Signature: RecoveryMediaVersion_x64
Action ended 13:44:09: AppSearch. Return value 1.
Action 13:44:09: VeeamEndpointProcessSettingsAction. 
Action start 13:44:09: VeeamEndpointProcessSettingsAction.
Action 13:44:09: VeeamEndpointProcessSettingsAction. Loading registry values…
Action 13:44:09: . 
Action ended 13:44:09: VeeamEndpointProcessSettingsAction. Return value 1.
Action 13:44:09: VeeamEndpointValidateInstalledVersionAction. 
Action start 13:44:09: VeeamEndpointValidateInstalledVersionAction.
Action 13:44:09: VeeamEndpointValidateInstalledVersionAction. Checking upgrade possibility...
***Veeam***  Setup was unable to check installed version. Error code: 0x00000645.
Action 13:44:09: . 
CustomAction VeeamEndpointValidateInstalledVersionAction returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 13:44:09: VeeamEndpointValidateInstalledVersionAction. Return value 3.
Action 13:44:09: SetupCompleteError. 
Action start 13:44:09: SetupCompleteError.
Info 2898.For Tahoma8 textstyle, the system created a 'Tahoma' font, in 1 character set.
Info 2898.For TahomaBold10 textstyle, the system created a 'Tahoma' font, in 1 character set.
Action 13:44:09: SetupCompleteError. Dialog created
Action ended 13:44:11: SetupCompleteError. Return value 2.
Action ended 13:44:11: INSTALL. Return value 3.
=== Logging stopped: 19.12.2019  13:44:11 ===
MSI (c) (5C:B0) [13:44:11:832]: Product: Veeam Agent for Microsoft Windows -- Installation operation failed.

MSI (c) (5C:B0) [13:44:11:833]: Windows Installer installed the product. Product Name: Veeam Agent for Microsoft Windows. Product Version: 3.0.2.1170. Product Language: 1033. Manufacturer: Veeam Software Group GmbH. Installation success or error status: 1603.

Again, it is absolutely not clear to me, what happens and why the install program keeps failing.
Please advise.

Regards
Hermann

[hnmr]

opened a support case: #03920303.

[ONServ]

How does-it end because I have the same issue : can't upgrade or uninstall from v1.5 :-/

[Egor Yakovlev]

Self-resolved by resetting Windows 10 (option to "Keep applications and personal data").
/Thank!