Installation of SQL Express fails with the error: "Failed to install SQL Express BKUPEXEC instance with error 1706." or "The installation package for product cannot be found."
"Failed to install SQL Express BKUPEXEC instance with error 1706."
The following error message will appear in BKUPINST.LOG:
ERROR: Failed to install SQL Express BKUPEXEC instance with error 1706. ***To search for information about this error, click here.
<time stamp>: Please review C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt for more details.
<time stamp>: Failed to install third party products.
You may also see:
Error 87: Unable to get SQL version info for SQL instance
The return code is: 1602
The C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt will give the error:
Machine : servername
Product : SQL Server Setup Support Files
Error String : An installation package for the product Microsoft SQL Server Setup Support Files cannot be found. Try the installation again using a valid copy of the installation package 'sqlsupport.msi'.
Error Number : 1706
The SQL Upgrade check may pass, but the SQL Express Installer Check will fail with a pop up message:
The installation package for product cannot be found. Until this issue is resolved, SQL Express cannot be installed.
1. Uninstall the Microsoft SQL Server Setup Support Files by using Windows Add or Remove Programs.
2. Try to use the information in the following Microsoft KB articles:
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
The Windows Installer Cache Verifier may indicate the operating system needs to be rebuilt. If the registry keys associated with the problematic missing cache files do not have any subkeys (i.e. there are no + signs next to them in the HKEY_CLASSES_ROOT\Installer\Products hive as the other products in the hive will have), then the keys may safely be deleted and resolve the issue, without the need to rebuild the operating system. The product codes in the report, without the brackets or dashes, will match the name of the key to remove. Always back up or export the registry before making any changes.
Run setup for Backup Exec again after attempting any of the solutions above.