Backup Exec 2010 V3 Installation failed with error -529697949

[A_Bohren]

Hi All,

I wanted to Upgrade my Backup Exec 2010 Installation to V3.

As mentioned by the Article below, i uninstalled Backup Exec because i have only a small List of Jobs running.

http://www.symantec.com/business/support/index?page=content&id=TECH159557&key=15047&basecat=INSTALLI...

After a Reboot i tried to install Backup Exec 2010 V3 - it comes up with the error below.

I have already tried a lot (Clean up Filesystem from Backup Exec Folders, Cleaned Registry from Backup Exec Keys, etc.) But this has not been sucessful so far. Any Ideas?

Symantec Backup Exec (TM) 13 Installation Log

06-27-2011,23:48:33 : EnumProcesses Counts: 89
06-27-2011,23:48:33 : Windows Operating System Version: 6.1
06-27-2011,23:48:33 : GetProductInfo returned success. Checking for CORE OS values.
06-27-2011,23:48:35 : Executing managed _Setup:
06-27-2011,23:48:35 : C:\Install\BE\WinNT\Install\BEx64\Install\_Setup.exe
06-27-2011,23:48:35 : Loading XML from:
06-27-2011,23:48:35 : C:\Install\BE\WinNT\Install\BEx64\Install\IFProducts.xml
06-27-2011,23:48:35 : RawsDlgSequence::CheckInstMode
06-27-2011,23:48:35 : BEOperations::BE_GetInstalledProdCodeVersion()
06-27-2011,23:48:36 : Launching UI Install
06-27-2011,23:48:36 : MDAC 6.1.7601.17514 is installed on this system.
06-27-2011,23:48:36 : m_bUseNativeClient = 1
06-27-2011,23:48:36 : MDAC 6.1.7601.17514 is installed on this system.
06-27-2011,23:48:36 : BeSeqDlgs::DlgBERemoteConfig
06-27-2011,23:48:36 : CopySupportFiles
06-27-2011,23:48:36 : Saved support files to C:\ProgramData\Symantec\Backup Exec\Logs\InstallSummary
06-27-2011,23:48:36 : AgentSeqDlgs::Misc_BE_CommonOps
06-27-2011,23:48:36 : Executing BE_SetSQLxLangVersion. Setting language version of SQL Express BKUPEXEC instance.
06-27-2011,23:48:36 : BKUPEXEC SQLx setup file is SQLEXPR.EXE.
06-27-2011,23:48:47 : Typical install value is set to : False
06-27-2011,23:48:47 : Typical install value is set to : False
06-27-2011,23:48:48 : Typical install value is set to : False
06-27-2011,23:48:50 : m_bUseNativeClient = 1
06-27-2011,23:48:50 : m_bUseNativeClient = 1
06-27-2011,23:48:50 : DRIVER={SQL Native Client};SERVER=ICESRV02;Trusted_Connection=Yes
06-27-2011,23:48:50 : Executing SQL_GetServicePack.
06-27-2011,23:48:50 : DRIVER={SQL Native Client};SERVER=ICESRV02;Trusted_Connection=Yes
06-27-2011,23:48:50 : Connected to SQL Server.
06-27-2011,23:48:50 : ICESRV02 is a SQL Server Product Level: 'SP2'
06-27-2011,23:48:50 : Executing SQL_GetSQLServerEdition.
06-27-2011,23:48:50 : There is no MSSQL$MSSQLSERVER Service
06-27-2011,23:48:50 : V-225-226: Unable to connect to SQL Server. ***To search for information about this error, click here
06-27-2011,23:48:50 : Executing SQL_GetServicePack.
06-27-2011,23:48:50 : DRIVER={SQL Native Client};SERVER=ICESRV02;Trusted_Connection=Yes
06-27-2011,23:48:50 : Connected to SQL Server.
06-27-2011,23:48:50 : ICESRV02 is a SQL Server Product Level: 'SP2'
06-27-2011,23:49:01 : The install failed with an unexpected error:External component has thrown an exception.
06-27-2011,23:49:01 : at Symantec.BackupExec.BeSeqDlgs.DlgValidationSummary.ValidateComputer(String szXMLPath) at Symantec.BackupExec.BeSeqDlgs.DlgValidationSummary.LaunchValidation(String sourceDir, String targetDir) at Symantec.BackupExec.BeSeqDlgs.DlgValidationSummary.CreateSummary() at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart()
06-27-2011,23:49:01 : If this install is being run from a network share, copying the media locally and retrying the install may resolve this issue.
06-27-2011,23:49:04 : ERROR: Installation failed with error -529697949. GetLastError = :0

Regards

Andres Bohren
 

[AmolB]

Install SQL instance manually and then proceed with the installation of Backup Exec.

During installation select custom install and then link the SQL instance with Backup Exec.

Refer to  http://www.symantec.com/docs/TECH87111

[Idimple]

Hello,

Please check out the below document

A fresh installation of Backup Exec fails with 'The install failed with an unexpected error:Object reference not set to an instance of an object'

http://www.symantec.com/business/support/index?page=content&id=TECH138620&actp=search&viewlocale=en_...

http://www.symantec.com/business/support/index?page=content&id=TECH156616&actp=search&viewlocale=en_...

[pkh]

What is the version of BE that you are upgrading from?

[A_Bohren]

SQL Instance is already installed for other Applications

06-27-2011,23:48:50 : Connected to SQL Server.
06-27-2011,23:48:50 : ICESRV02 is a SQL Server Product Level: 'SP2'

The connection to the Database works fine.

Regards Andres
 

[A_Bohren]

Hi

I have checked these two Articles. But none of them did exactly match or did help resolve the Problem.

Regards Andres

[A_Bohren]

Hi

I wanted to Upgrade my Backup Exec 2010 (RTM i guess - with all the Updates that comes with Live Update) to Backup Exec 2010 V3.

Regards Andres

[pkh]

I am surprised that you are using a RTM version.  If you are really using a RTM version, you should uninstall it and then install R3.  Earlier, there were some users who reported problems when they tried to upgrade from a RTM version to an official release.  Prior to uninstalling the RTM version, you should stop all the BE services and the BE SQL instance and make a copy of the Data and Catalog directories under the BE installation directory.  After you have installed R3, you can then replace the Data and Catalog directories with the saved copies.  This way, you don't have to re-define your jobs or re-catalog your media.

It is not recommended that you use an existing production SQL instance for BE.  This is because you might on occasions need to stop the BE database and this will interfere with your production systems.  You should create a separate named SQL instance for BE.

[A_Bohren]

Hi pkh

As i wrote in the starting Post - i did uninstall Backup Exec and Rebooted the Server bevore trying to install the new Version of Backup Exec 2010 V3. So this is not an upgrade Problem. It is an installing Problem witch can have its cause by an unclean uninstall of the previous version of Backup Exec 2010.

I have only made a Copy of the Catalog Directories. I did not expect to have Problems by uninstalling and reinstalling...

I am aware of the Problems regarding the use of a shared SQL DB. But that is not the cause of the Problem i am running into right?

Regards Andres

[pkh]

From the error log that you have posted, it appears that you have problems connecting to the SQL instance that you want to use for your SQL DB.  It could be that the id that you used during the installation does not have the necessary permissions for the database.

I think you are trying to use the default instance of SQL instance on the server which does not have a name.  I have never managed to use the default nameless instance for BE.

[A_Bohren]

Hi PHK

I have some experience with SQL. This  is a custom Installation - where i will be able to select the SQL Server. But i don't even reach that. The error comes when Backup Excec makes the Environement check. If i run the Environement check standalone - then everything liiks fine.

The Connect to the SQL DB works fine - it gets even the Service Pack Level.

06-27-2011,23:48:50 : Executing SQL_GetServicePack.
06-27-2011,23:48:50 : DRIVER={SQL Native Client};SERVER=ICESRV02;Trusted_Connection=Yes
06-27-2011,23:48:50 : Connected to SQL Server.
06-27-2011,23:48:50 : ICESRV02 is a SQL Server Product Level: 'SP2'
 

Regards Andres

[A_Bohren]

The Error is thrown while WMI Checks are running.

OS: Windows 2008 R2 Standard EN SP1 x64

Regards Andres

[A_Bohren · Accepted solution]

Hi all,

Remote Install from another Server was sucessful and solved the Problem.

Regards Andres