So the other day I blogged about the Veeam v8 upgrade, and as mentioned my Enterprise Manager didn’t work, giving the error;

The Access Control List is not in canonical form and therefore cannot be modified.

So I logged a call with Veeam to get it fixed.

Error Logs

Basically giving logs such as the below.

=== Logging stopped: 10/11/2014 13:39:22 ===
MSI (s) (98:14) [13:39:22:826]: Note: 1: 1708 
MSI (s) (98:14) [13:39:22:826]: Product: Veeam Backup Enterprise Manager -- Installation operation failed.

MSI (s) (98:14) [13:39:22:826]: Windows Installer installed the product. Product Name: Veeam Backup Enterprise Manager. Product Version: 8.0.0.817. Product Language: 1033. Manufacturer: Veeam Software AG. Installation success or error status: 1603.

MSI (s) (98:14) [13:39:22:826]: Deferring clean up of packages/files, if any exist
MSI (s) (98:14) [13:39:22:826]: MainEngineThread is returning 1603
MSI (s) (98:78) [13:39:22:826]: No System Restore sequence number for this installation.
MSI (s) (98:78) [13:39:22:842]: User policy value 'DisableRollback' is 0
MSI (s) (98:78) [13:39:22:842]: Machine policy value 'DisableRollback' is 0
MSI (s) (98:78) [13:39:22:842]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (98:78) [13:39:22:842]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
MSI (s) (98:78) [13:39:22:842]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
MSI (s) (98:78) [13:39:22:842]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (98:78) [13:39:22:842]: Destroying RemoteAPI object.
MSI (s) (98:0C) [13:39:22:842]: Custom Action Manager thread ending.
MSI (c) (88:00) [13:39:22:842]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (88:00) [13:39:22:842]: MainEngineThread is returning 1603
=== Verbose logging stopped: 10/11/2014 13:39:22 ===

The fix provided by Veeam

I logged a call with Veeam, and their response was

Thanks for your logs and screenshot.
According to your screenshot. You have an issue with your .acl file.
1) Please import configuration file and then use it.
2) Install Veeam 7 from scratch.
3) After that you should be able to install Veeam 8 with a fresh installation.
4) Apply the configuration file if needed.

Yep I was surprised too, I queried it with them over the phone, apparently this behavior has been seen in a few upgrades recently, and this is the quickest way to fix the fault, rather than trying to troubleshoot it.

Notes on this workaround

When you uninstall everything and reinstall v7 (Veeam B+R and Ent Mgr), it leaves the SQL database behind, which means you cannot install v7 onto the same DB, as the versions mismatch. This is fine, you can install using another DB name, and then restore the configuration over the old DB name. See my below screenshots.

1. Open Veeam B+R, go to File, then Configuration Backup, then Restore.

1a. You can also initiate this manually from,

C:\Program Files\Veeam\Backup and Replication\Backup\Veeam.Backup.Configuration.Restore.exe

2. Set your Backup file location, and your DB name

3. Add in your passwords for your accounts again

4. Start restoring

If you get;

Error Unable to restore database VeeamBackup. Invalid column name 'os_platform'." 

Then this is more than likely because your Veeam install is at a different patch level to your Restore Configuration.

5. Finally, upgrade your Veeam install to Version 8, starting with Enterprise Manager first.

 

Regards

 

Dean
Follow @saintdle