Backup Exec 2010 R2 Installation failing

[ECB]

Hey there

Using a Small Business Server 2003
Had Backupexec 2010 trial version on,when the trial ceased we attempted to install the Backup Exec 2010 R2 however the installation failed with the following error:

"The install failed with an unexpected error:Object reference not set to an instance of an object."



After this I tried uninstalling the Trial BE 2010 and Liveupdate,and also repairing and reinstalling the dot Net packages 2.0 3.5 and 4

Any ideas?

[ECB]

Moved to right section and updated tags

[Ben_L_]

Can you post the install log from the install?

[ECB]

Log follows:

Symantec VxLogServer

08-31-2010,13:06:16 : Loading XML from:
08-31-2010,13:06:16 : E:\Backupexec Install\BE\WinNT\Install\BE32\Install\IFProducts.xml
08-31-2010,13:06:16 : RawsDlgSequence::CheckInstMode
08-31-2010,13:06:16 : BEOperations::BE_GetInstalledProdCodeVersion()
08-31-2010,13:06:17 : Launching UI Install
08-31-2010,13:06:17 : MDAC 2.82.3959.0 is installed on this system.
08-31-2010,13:06:17 : m_bUseNativeClient = 1
08-31-2010,13:06:17 : MDAC 2.82.3959.0 is installed on this system.
08-31-2010,13:06:18 : BeSeqDlgs::DlgBERemoteConfig
08-31-2010,13:06:18 : CopySupportFiles
08-31-2010,13:06:18 : Saved support files to C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\Logs\InstallSummary
08-31-2010,13:06:18 : AgentSeqDlgs::Misc_BE_CommonOps
08-31-2010,13:06:18 : Executing BE_SetSQLxLangVersion. Setting language version of SQL Express BKUPEXEC instance.
08-31-2010,13:06:18 : NLS (0) version of SQL instance found on this system.
08-31-2010,13:06:18 : BKUPEXEC SQLx setup file is SQLEXPR32.EXE.
08-31-2010,13:06:24 : Typical install value is set to : False
08-31-2010,13:06:24 : Typical install value is set to : False
08-31-2010,13:06:25 : Typical install value is set to : False
08-31-2010,13:06:40 : m_bUseNativeClient = 1
08-31-2010,13:06:41 : Executing SQL_GetServicePack.
08-31-2010,13:06:41 : DRIVER={SQL Native Client};SERVER=EVERSERV01\MICROSOFT##SSEE;Trusted_Connection=Yes
08-31-2010,13:06:41 : Connected to SQL Server.
08-31-2010,13:06:41 : EVERSERV01\MICROSOFT##SSEE is a SQL Server Product Level: 'SP2'
08-31-2010,13:06:41 : Executing SQL_GetServicePack.
08-31-2010,13:06:41 : DRIVER={SQL Native Client};SERVER=EVERSERV01;Trusted_Connection=Yes
08-31-2010,13:06:41 : Connected to SQL Server.
08-31-2010,13:06:41 : EVERSERV01 is a SQL Server Product Level: 'SP3'
08-31-2010,13:06:41 : Executing SQL_GetSQLServerEdition.
08-31-2010,13:06:41 : There is no MSSQL$MSSQLSERVER Service
08-31-2010,13:06:41 : V-225-226: Unable to connect to SQL Server. ***To search for information about this error, click here
08-31-2010,13:06:41 : Executing SQL_GetServicePack.
08-31-2010,13:06:41 : DRIVER={SQL Native Client};SERVER=EVERSERV01;Trusted_Connection=Yes
08-31-2010,13:06:41 : Connected to SQL Server.
08-31-2010,13:06:41 : EVERSERV01 is a SQL Server Product Level: 'SP3'
08-31-2010,13:06:41 : Executing SQL_GetServicePack.
08-31-2010,13:06:41 : DRIVER={SQL Native Client};SERVER=EVERSERV01\REPORTS;Trusted_Connection=Yes
08-31-2010,13:06:41 : Connected to SQL Server.
08-31-2010,13:06:41 : EVERSERV01\REPORTS is a SQL Server Product Level: 'RTM'
08-31-2010,13:06:41 : Executing SQL_GetSQLServerEdition.
08-31-2010,13:06:41 : DRIVER={SQL Native Client};SERVER=EVERSERV01\REPORTS;Trusted_Connection=Yes
08-31-2010,13:06:41 : Connected to SQL Server.
08-31-2010,13:06:41 : Executing SQL_GetServicePack.
08-31-2010,13:06:41 : DRIVER={SQL Native Client};SERVER=EVERSERV01\REPORTS;Trusted_Connection=Yes
08-31-2010,13:06:41 : Connected to SQL Server.
08-31-2010,13:06:41 : EVERSERV01\REPORTS is a SQL Server Product Level: 'RTM'
08-31-2010,13:07:26 : m_bUseNativeClient = 1
08-31-2010,13:07:26 : AgentSeqDlgs::Misc_BE_CommonOps
08-31-2010,13:07:26 : OS Version=5.2; OS Service Pack=Service Pack 2
08-31-2010,13:08:30 : Currently executing as ECB\administrator
08-31-2010,13:08:30 : Install is executing as the service account.
08-31-2010,13:08:30 : EUserName value successfully written to the registry.
08-31-2010,13:08:30 : EPassword value successfully written to the registry.
08-31-2010,13:08:30 : EDomain value successfully written to the registry.
08-31-2010,13:17:54 : m_bUseNativeClient = 1
08-31-2010,13:17:54 : Could not determine the version of sql for instance
08-31-2010,13:17:54 : DRIVER={SQL Native Client};SERVER=EVERSERV01;Trusted_Connection=Yes
08-31-2010,13:17:54 : Connected to SQL Server: EVERSERV01
08-31-2010,13:17:54 : SQL Server version 9
08-31-2010,13:17:54 : SQL version returned: 9
08-31-2010,13:17:54 : Successfully connected as sysadmin/dbcreator.
08-31-2010,13:17:54 : Unsuccessful return code from SQL statement: select filename from master..sysdatabases where name='BEDB'
08-31-2010,13:17:54 : DRIVER={SQL Native Client};SERVER=EVERSERV01;Trusted_Connection=Yes;DATABASE=master
08-31-2010,13:17:54 : SQL Server version 9
08-31-2010,13:17:54 : SQL version returned: 9
08-31-2010,13:17:54 : Executing SQL_GetServicePack.
08-31-2010,13:17:54 : DRIVER={SQL Native Client};SERVER=EVERSERV01;Trusted_Connection=Yes
08-31-2010,13:17:54 : Connected to SQL Server.
08-31-2010,13:17:54 : EVERSERV01 is a SQL Server Product Level: 'SP3'
08-31-2010,13:17:54 : Executing SQL_GetSQLServerEdition.
08-31-2010,13:17:54 : DRIVER={SQL Native Client};SERVER=EVERSERV01;Trusted_Connection=Yes
08-31-2010,13:17:54 : Connected to SQL Server.
08-31-2010,13:17:54 : EVERSERV01 is a SQL Server Standard Edition
08-31-2010,13:17:54 : DRIVER={SQL Native Client};SERVER=EVERSERV01;Trusted_Connection=Yes;DATABASE=
08-31-2010,13:17:54 : Connected to SQL Server.
08-31-2010,13:17:54 : SQL Server version 9
08-31-2010,13:17:54 : Connected to SQL Server.
08-31-2010,13:17:54 : Registry key name for instance MSSQL.1, has been obtained.
08-31-2010,13:17:54 : DRIVER={SQL Native Client};SERVER=EVERSERV01;Trusted_Connection=Yes;DATABASE=
08-31-2010,13:17:55 : Connected to SQL Server.
08-31-2010,13:17:55 : SQL Server version 9
08-31-2010,13:17:55 : Connected to SQL Server.
08-31-2010,13:17:55 : Registry key name for instance MSSQL.1, has been obtained.
08-31-2010,13:17:56 : m_bUseNativeClient = 1
08-31-2010,13:17:56 : To back up Microsoft Exchange Server 2007, you must install the Exchange Management Tools for Microsoft Exchange Server 2007 on this computer. The Management Tools can be installed during a custom install of Microsoft Exchange Server 2007. To support individual mailbox message and folder restores from Information Store backups, you must also download and install the Microsoft Exchange Server MAPI Client and Collaboration Data Objects package version 06.05.7888 or later on the Exchange 2007 server. This package can be found on the Microsoft Web site.
08-31-2010,13:18:01 : m_bUseNativeClient = 1
08-31-2010,13:18:01 : To back up Microsoft Exchange Server 2007, you must install the Exchange Management Tools for Microsoft Exchange Server 2007 on this computer. The Management Tools can be installed during a custom install of Microsoft Exchange Server 2007. To support individual mailbox message and folder restores from Information Store backups, you must also download and install the Microsoft Exchange Server MAPI Client and Collaboration Data Objects package version 06.05.7888 or later on the Exchange 2007 server. This package can be found on the Microsoft Web site.
08-31-2010,13:18:02 : Terminal Services enabled.
08-31-2010,13:18:02 : Terminal Services server has been set to Install mode.
08-31-2010,13:18:02 : Checking for .Net Framework 3.5 SP1.
08-31-2010,13:18:53 : Executing InstallLiveUpdate.
08-31-2010,13:19:05 : The return value for Symantec LiveUpdate returned error code: 0
08-31-2010,13:19:05 : Installing Microsoft Report Viewer Redistributable 2005
08-31-2010,13:19:06 : The return value for Microsoft Report Viewer Redistributable 2005 returned error code: 0
08-31-2010,13:19:06 : Starting Install
08-31-2010,13:19:06 : AgentSeqDlgs::Misc_BE_CommonOps
08-31-2010,13:19:06 : AgentSeqDlgs::Misc_BE_CommonOps
08-31-2010,13:19:18 : The install failed with an unexpected error:Object reference not set to an instance of an object.
08-31-2010,13:19:18 : at e.a(String& A_0) at e.a() at Symantec.IFrameSDK.Iframe2.ProductInstaller.StartInstall(BaseDialog dlg) at e.a(BaseDialog A_0) at Symantec.IFrameSDK.Iframe2.MultiProductInstaller.Install_Product_Thread() at System.Threading.ThreadHelper.ThreadStart_Context(Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart()
08-31-2010,13:19:18 : If this install is being run from a network share, copying the media locally and retrying the install may resolve this issue.

[Ben_L_]

This looks like the same error a few others have reported.  Since this is an issue support is already looking into this issue, you're best bet is going to be to call in to work with support.

[ECB]

Got a central thread or mail contact to use? I'm unable to log into the support site as I'm not receiving my email validation key and this is becoming quite bothersome,spending this amount of money on 2010 R2 when 2010's trial was working fine and being left without backups

[AmolB]

Hello

  Do you have Backup Exec System Recovery installed on the same server ?

[RRE]

Hello

You can refer the following technote to resolve the issue

http://support.veritas.com/docs/351697



Regards
Ratish

[ECB]

No BESR on the server :)

Thanks i'll look at that note and report back

[ECB]

That technote refers to installation files on a network location,I copied the DVD to the c:\ drive hoping to resolve this using the method described yesterday :)

Problem persists

[ECB · Accepted solution]

Got the install to complete succesfully

There were db files and catalogues for the BESR2010 in c:\program files\symantec\backupexec

Upon deleting the folder entirely the installation completed without a hitch

[Gary_Karasik]

I had the same error message, and your response gave me the clue to the solution: I had installed, then uninstalled, BESR2010, and although there were no BESR files in the folder you mention, there was a BESR entry left in the registry under HKLM/SOFTWARE/Symantec. Removing that entry allowed the install to proceed.

GaryK

[Berrebi]

like Gary and ECB said remove registry entry for system BESR

thanks guys