Backup exec 2010 R2 to 2010 R3 failed, even uninstall failed!

[vicom147]

Hi, I'm trying to update my backup exec from 2010R2 to 2010R3 but it fails.

when it is allmost finished the setup is doing rollback.

I'm getting the following error: (I changed the servername)

10-30-2011,16:05:12 : m_bUseNativeClient = 1
10-30-2011,16:05:12 : Executing SQL_GetServicePack.
10-30-2011,16:05:12 : DRIVER={SQL Native Client};SERVER=SERVER01\MICROSOFT##SSEE;Trusted_Connection=Yes
10-30-2011,16:05:27 : V-225-206: SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. Login timeout expired ***To search for information about this error, click here
10-30-2011,16:05:27 : V-225-226: Unable to connect to SQL Server. ***To search for information about this error, click here
10-30-2011,16:05:29 : m_bUseNativeClient = 1
10-30-2011,16:05:29 : AgentSeqDlgs::Misc_BE_CommonOps
10-30-2011,16:05:29 : GetClusterUpgradeState returning 0

and a further in the log file:

10-30-2011,16:10:06 : SQL version returned: 9
10-30-2011,16:10:06 : DRIVER={SQL Native Client};SERVER=SERVER01\BKUPEXEC;Trusted_Connection=Yes
10-30-2011,16:10:06 : Unable to prep database instances for upgrade.
10-30-2011,16:10:06 : V-225-134: Error Migrating BEDB ***To search for information about this error, click here
10-30-2011,16:10:06 : V-225-134: Error Migrating BEDB ***To search for information about this error, click here
10-30-2011,16:10:06 : CustomAction Migrate_BEDB returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
10-30-2011,16:10:06 : Action ended 16:10:06: InstallExecute. Return value 3.
10-30-2011,16:10:06 : Action 16:10:06: Rollback. Rolling back action: 10-30-2011,16:10:06 : SQL version returned: 9
10-30-2011,16:10:06 : DRIVER={SQL Native Client};SERVER=SERVER01\BKUPEXEC;Trusted_Connection=Yes
10-30-2011,16:10:06 : Unable to prep database instances for upgrade.
10-30-2011,16:10:06 : V-225-134: Error Migrating BEDB ***To search for information about this error, click here
10-30-2011,16:10:06 : V-225-134: Error Migrating BEDB ***To search for information about this error, click here
10-30-2011,16:10:06 : CustomAction Migrate_BEDB returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
10-30-2011,16:10:06 : Action ended 16:10:06: InstallExecute. Return value 3.
10-30-2011,16:10:06 : Action 16:10:06: Rollback. Rolling back action:
10-30-2011,16:10:06 : Migrate_BEDB
10-30-2011,16:10:06 : RB_RollbackBEDB
10-30-2011,16:10:06 : Rolling back BEDB files during upgrade rollback in UPG_RollbackBEDB
10-30-2011,16:10:06 : GetClusterUpgradeState returning 0
10-30-2011,16:10:07 : m_bUseNativeClient = 1

I also tried to uninstall the 2010R2 but that fails to, even update using Live update does not work.
I tried the solution with the dvd quote error.

How can I solve this without re-install the server?
 

[newsolutionBE]

Hi

Please take the backup of your data & catalog for version 2010 r2 & using the link below uninstall BE 2010 R2 manually

http://www.symantec.com/docs/TECH50720

Once done please install BE 2010 R3 as fresh install

Then use the below link to migrate

http://www.symantec.com/docs/TECH49757

Thanks

[pkh]

READ THE POST CAREFULLY.  The OP is looking for a solution which does not involve re-installation.

[pkh]

@vicom147 - Can you still run BE?  If so, use the same id that you used to run BE to upgrade it.  Don't use an id with lower priviledges.  

Also, where is be BEDB located?  If you are using a remote instance, make sure that you can access the instance.  Your problem is because the BEDB cannot be accessed.

See whether this document helps

http://www.symantec.com/docs/TECH55836

[CraigV]

Hi vicom,

Came across the link below...whether or not it was pulled directly from a Symantec TN or not is another story, but this is a direct upgrade from BE 2010 R1 --> R2. So it might actually be the same thing you're experiencing...

Take a look and before doing anything, grab a copy of your registry:

https://www-secure.symantec.com/connect/blogs/refer-tip-if-you-faced-error-during-unable-prep-databa...

Just for interest's sake, the OP below had the solution...so the guy above plagiarised it!

https://www-secure.symantec.com/connect/forums/upgrade-backup-exec-2010-r2-fails

Thanks!

[vicom147]

Hi, yes I can run backup exec normally the BEDB is locally installed with the default SQL2005 express from the cd. If I use the sql server tool to get access to the database I can access it. As far as I know it is installed with the administrator account.

I've seen in the log file that it fails on the microsoft##SSEE instance.

this part of the log file sais that it is succesfully attached.:)

 Connected to SQL Server.
10-30-2011,18:11:12 : Unsuccessful return code from SQL statement: select filename from master..sysdatabases where name='BEDB'
10-30-2011,18:11:12 : Attaching BEDB to SQL Server.
10-30-2011,18:11:12 : EXEC sp_attach_db 'BEDB',@filename1 = N'C:\Program Files\Symantec\Backup Exec\Data\BEDB_Dat.mdf', @filename2 = N'C:\Program Files\Symantec\Backup Exec\Data\BEDB_Log.ldf'
10-30-2011,18:11:18 : BEDB has been succesfully attached to SQL Server.
10-30-2011,18:11:18 : Change BEDB owner to SA user.
 

As far as I know microsoft##SSEE is an instance from WSUS or Sharepoint and NOT from backup exec. so why is backup exec setup trying to contact to that instance?

[pkh]

10-30-2011,18:11:12 : Unsuccessful return code from SQL statement: select filename from master..sysdatabases where name='BEDB'

This is the failure.  It is unable to get the BEDB.  If you can access the BEDB using the SQL tool, run this query and see what is the result.

[vicom147]

Hi, when I execute that query it returns the filepath to the database with file "BEDB_dat.mdf"

Throught the explorer I found the file, only different is that the filename is "bdcb_dat.mdf" the result of query is "BEDB_dat.mdf"

[pkh]

The normal name for the BEDB is bedb_dat.mdf and the file is located in the Data directory under the BE installation directory.  Where did you find bdcb_data.mdf?

[vicom147]

in the default installation path (i'm not on the server now but i believe) C:\program files\symantec\backup exec\data\bedb_dat.mdf

(sorry for the bDCb_dat.mdf that was a mistyping)