cancel
Showing results for 
Search instead for 
Did you mean: 

Backup Exec 2012 SQLExpress Installation Fails v-225-53 error 70011

Andrew_Elliott
Level 3

Server 2008R2 with Backup Exec 2010R3 installed and operational

Microsoft SQL 2005 (With SP4)

Trying to install Backup Exec 2012 and it fails with:

 

+ 08-04-2012,05:44:29 : V-225-53: ERROR: Failed to install SQL Express BKUPEXEC instance with error 70011. ***To search for information about this error, click here 

No success following the link or searching for examples of this error.  Any suggestions on where to look for clues?  The entire set of warnings and errors is shown below:

 

 

 + 08-04-2012,05:23:23 : Could not load resdll
+ 08-04-2012,05:23:23 : Failed to Read Install Registry Value (Software\Symantec\Backup Exec For Windows\Backup Exec\14.0\Install\Path: )
+ 08-04-2012,05:25:31 : V-225-206: Connection attempt 1 failed: 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
+ 08-04-2012,05:25:51 : V-225-206: Connection attempt 2 failed: 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
+ 08-04-2012,05:26:11 : V-225-206: Connection attempt 3 failed: 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
+ 08-04-2012,05:26:11 : V-225-226: Unable to connect to SQL Server. ***To search for information about this error, click here
+ 08-04-2012,05:32:34 : Backup Exec 2012 features a new user experience and a new backup paradigm. Symantec strongly recommends that you read the Migration Report shown on the Migration Progress dialog to see how your existing jobs have been affected and visit the technical support knowledge base at http://support.veritas.com/UMI/V-225-284 for details.
+ 08-04-2012,05:43:46 : SQL registry subkey SQLGroup under SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Setup could not be deleted.
+ 08-04-2012,05:43:46 : SQL registry subkey FTSGroup under SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Setup could not be deleted.
+ 08-04-2012,05:44:29 : V-225-53: ERROR: Failed to install SQL Express BKUPEXEC instance with error 70011. ***To search for information about this error, click here
+ 08-04-2012,05:44:29 : Please review C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt for more details.

 

1 ACCEPTED SOLUTION

Accepted Solutions

Andrew_Elliott
Level 3

Resolved, guessing my Server 2005 Express environment was messed up internally somehow.  Not going to try undersanding it further.  With Symantec Support help the solution I used was:

  1. Download and install 2008 SQL Express with Tools, create a new instance
  2. Used TECH37752 procedure to move the backup exec database from my 2005 SQL Express instance to the new 2008 SQL Express instance
  3. Ran the 2010 to 2012 upgrade succesfully.

View solution in original post

5 REPLIES 5

Backup_Exec1
Level 6
Employee Accredited Certified
Hi Pleas check link below, http://www.symantec.com/docs/TECH186401 Also ensure if any Antivirus may be try disblaing it too Thanks

CraigV
Moderator
Moderator
Partner    VIP    Accredited

Hi,

 

Make sure the account you're using is an admin account, and if you have an AV on that server, turn it off while the installation runs.

If this still doesn't work, try installing SQL Express manually off the DVD first, and then run through the installation.

Thanks!

Andrew_Elliott
Level 3

No success.  Verified accounts access with BEUTILITY

Turned off AV

Repair installed SQL Express from BE 2010

Ran upgrade install from BE 2012, SQL Express install fails.

Backup_Exec1
Level 6
Employee Accredited Certified

Hi

You can also do one thing ,

 

1 Please grab the copy of data and catalogs folder & symantec shared folder and place it on one drive.(please note to copy data and catalog folder SQL service must be stopped & symantec shared folder location is in C-porgram data-application data ,if it is win2008)

2 Once done do complete uninstall of Backupexec 2010 & SQl too , Uninstall SQL only if it used by backup exec & not used by any other application. If SQl is also used by some other application then please don't uninstall it (if you dont uninstall SQL completely then before installing BE 2012 please install SQL manually with some name like bkupexec1 or some customize name & during install of BE 2010 please point to to SQL you have installed manually ,for same check link below)

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

3 Then install BE 2012 ,from BE 2010 sp1a ISO which has sp1a in it & then using live update ensure you patch it up to sp1a & 2 updates to fully update it

4 Then by stopping SQL service again take backup of data and catalog to different drive & by doing cut and paste & then copy the data & catalog folder from BE 2010

5 Finally please peform migration using the following link to see if that helps.

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

 

Thanks

 

Andrew_Elliott
Level 3

Resolved, guessing my Server 2005 Express environment was messed up internally somehow.  Not going to try undersanding it further.  With Symantec Support help the solution I used was:

  1. Download and install 2008 SQL Express with Tools, create a new instance
  2. Used TECH37752 procedure to move the backup exec database from my 2005 SQL Express instance to the new 2008 SQL Express instance
  3. Ran the 2010 to 2012 upgrade succesfully.