Salta al contenuto principale

Back Up & Recovery & Universal Restore; Crashed - cannot re-install

Thread needs solution

I had a fully licensed Backup & Recovery Universal Restore 10 running under Windows 7 Professional.

I regularly had issues re License keys not being recognised and followed recommended fix each time but last time it did not work.

Acronis support told me support had run out but as this was a regular issue he agreed to help fix it remotely. After nearly two hours of getting the same error I had, he (with my agreement) deleted the system in order to re-install.

This needed a re-boot so he exited and left me to re-install.

License Management installed OK and recognised the two licenses - then tried to instally the rest but got error message as attached and installa tion failed.

Acronis Support followed up the remote session with an email referenced ref:00D3Zcb.5005DzOOO:ref but my replies explaining I could not complete the installation have had no response so I am left with no back up system in operation.

Can anyone suggest how to overcome the installtion error? Any assistance will be greatly appreciated.

Thanks,

Brian

Allegato Dimensione
acronis_111007_installation_error.docx 129.16 KB
0 Users found this helpful

Hi Brian

First off I see you are running ABR10 and guess it must be the advanced edition as the error message seems to be related to a SQL error.

What might be best to do is to ensure you are ABR10 build 13762, release notes can be found here: http://www.acronis.com.au/my/products/changes.html?p=5399

As you currently have not got ABR10 installed and are trying to perform a fresh install what might be best is to wipe away any traces of ABR10 including the SQL database as well as running the ABR10 cleanup utility on your system.

Here are the steps I would recommend to start a fresh:
- Uninstall/remove any Acronis SQL databases
- Run ABR10 clean up utility as per: http://kb.acronis.com/content/6177
- Install ABR10 using build 13762 (or later)

Thank you for your suggestions - Acronis Support have now fixed this remotely - it was as you suggested an SQL issue which was beyond my level of understanding!

Thanks again.