Backup Exec Installation fails with the following error:
Failed to install SQL Express BKUPEXEC instance error 70045
Backup Exec installation fails and the install log (bkupinst.htm) reports following error:
04-24-2009,16:31:24 : ERROR: Failed to install SQL Express BKUPEXEC instance with error 70045. ***To search for information about this error, click here
04-24-2009,16:31:24 : Please review C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt for more details.
04-24-2009,16:31:24 : Failed to install third party products.
Backup Exec installation log (bkupinst.htm) file will be present under C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\Logs directory.
Summary.txt file located under C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Log folder shows following:
SERVERNAME : SQL Server Setup is unable to run on this node as it is unavailable due to a SCC failure or other reason.
SERVERNAME : SQL Server Setup is unable to run. Either the owning node or all nodes that are currently part of the virtual server are not available. Review any SCC failures and validate that all nodes are online.
Please note that Summary.txt file will be present under C:\Program Files(x86)\Microsoft SQL Server\90\Setup Bootstrap\Log directory on a 64bit Windows installation.
Running SQL express setup manually gives following pop up error:
SQL Server Setup is unable to run. Either the owning node or all nodes that are currently part of the virtual server are not available. Review any SCC failures and validate that all nodes are online.
1. Open registry editor on the server.
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
Either delete dword value 'AutoShareServer' under:
OR set it to 1.
: If the AutoShareServer
key is set to 0
, administrative shares (such as C$, D$, Admin$, and so on) cannot be created automatically. Refer to MS KB article http://support.microsoft.com/kb/318755
for additional information on AutoShareServer
2. Reboot the server and then re run the setup.