How to troubleshoot the error "V-225-53: ERROR: Failed to install SQL Express BKUPEXEC Instance" that occurs when attempting to install Backup Exec

Article:TECH56006  |  Created: 2010-01-31  |  Updated: 2014-05-07  |  Article URL http://www.symantec.com/docs/TECH56006
Article Type
Technical Solution

Product(s)

Subject

Issue



When attempting to install Backup Exec, agent options, or licensing the installation fails with the error listed below. 


Error



Error

V-225-53: ERROR: Failed to install SQL Express BKUPEXEC Instance.

Installation may fail with any of the following error codes:

Error 2   Error 5   Error 102   Error 1332   Error 1388   Error 1402   Error 1603  
Error 1612   Error 1627   Error 1706   Error 2749   Error 2908   Error 15151   Error 15359  
Error 28062   Error 28086   Error 28111   Error 28115   Error 29508   Error 29552   Error 70045  

Solution



The installation failure of the SQL Express instance can be resolved by performing the steps from one or more of the solutions listed in the solution section below; click the coresponding error code seen below to quickly navigate to the solution for that specific error. Use the following utility to aid in troubleshooting this matter:  

The Backup Exec Pre install Environment Checker displays a warning that the Backup Exec installation may fail with WMI errors.

 www.symantec.com/docs/TECH49219

Error 2:

Cause:

This issue is encountered if AppData value is not copied correctly (or is missing) from HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\AppData to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\AppData when a user is created on a system.

Solution:

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.


1.To resolve this issue ensure that the Registry Key AppData is present in the location HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\AppData.

2.If the above mentioned key is not present in both the locations then create the Expandable String Value AppData with value %USERPROFILE%\Application Data

For more information about this error please refer:
http://www.symantec.com/docs/TECH64345

 

 

Error 5:

Cause:

Check the existence of a File Screen Template that could be avoiding the extraction of the SQL Express install files and uncheck System Files and Temporary Files groups. SQL Express self extractor by design look for the hard disk with the more available space to create a temporary folder to extract the installation files.

According to Microsoft Windows 2008 Server Help:
...A file screen template defines a set of file groups to screen, the type of screening to perform (active or passive), and (optionally) a set of notifications that will be generated when a user saves, or attempts to save, an unauthorized file. If you base your file screens on a template, you can automatically update all file screens that are based on a specific template by editing that template...

Solution:

1. On Windows 2008 Server go to Start --> All Programs --> Administrative Tools --> File Server Resource Manager
2. Select File Screens on File Screening Management node.
3. In the right pane, right click on File Screen templates that monitors HD and choose properties.
4. Uncheck System Files, Executable files and Temporary Files groups.
5. Re-attempt the Backup Exec setup/install.

For more information about this error please refer:
http://www.symantec.com/docs/TECH75090

 

Error 102:

Cause:

This is a Microsoft configuration issue which occurs because SQL Express was installed to an extended path. Error message when you install SQL Server 2005 SP2, SQL Server Express SP2, or SQL Server Express with Advanced Services SP2:

Solution:

SQL Server Setup failed to execute a command for server configuration. CREATE DATABASE failed

For more information about this error please refer:
http://support.microsoft.com/kb/935371

 

Error 1332:

Cause:

Upgrade to Backup Exec For Windows Server ( BEWS) 12.5 fails with Failed to install SQL Express BKUPEXEC instance Error 1332.

Solution:

-

For more information about this error please refer:
http://www.symantec.com/docs/TECH64580

 

Error 1388:

Cause:

Upgrade to Backup Exec for Windows Servers 12 or 12.5 fails with Failed to install SQL Express BKUPEXEC instance Error 1388.

Solution:

-

For more information about this error please refer:
http://www.symantec.com/docs/TECH64677

 

Error 1402:

Cause:

Existing SQL Native Client Installation May Cause Setup to Fail.

Solution:

Setup might fail and roll back with the following error message: An installation package for the product Microsoft SQL Native Client cannot be found. Try the installation again using a valid copy of the installation package 'Sqlncli.msi'. To resolve this issue, uninstall the SQL Native Client by using Add or Remove Programs. On a cluster, uninstall SQL Native Client from all nodes. Then, run the SQL Server Setup again.

For more information about this error please refer:
http://www.symantec.com/docs/TECH57660

 

Error 1603:

Cause:

After selecting an additional option in Evaluation Mode or entering a Backup Exec License/Product Activation Key, then clicking Next and attempting to complete the updated installation, Failed to install SQL Express BKUPEXEC instance with error 1603 occurs .

Solution:

1.  Launch Beutility.exe  located under X:\Programs Files\Symantec\ Backup Exec (Where X: is the location for Backup Exec Installation, by default it would be C:\)

2. Select File > New Server. Enter the Backup Exec server name, then select OK.

3. After adding the name, it will show under all media servers.  Right click on the server name.

4. Select Change Database Access from the drop down menu.

5. Grant access to the Backup Exec account and also the user account logged on to the server if different than the Backup Exec account .

6.  Re-run the installation and attempt to add the license again.

For more information about this error please refer:
http://www.symantec.com/docs/TECH73030

 

Error 1612:

Cause:

Installation of Backup Exec for Windows Servers (BEWS) fails with Failed to install SQL Express BKUPEXEC instance Error 1612.

Solution:

-

For more information about this error please refer:
http://www.symantec.com/docs/TECH65413

 

Error 1627:

Cause:

Installation of license keys/Agent in evaluation mode in Backup Exec fails with error Failed to install SQL Express BKUPEXEC instance: Error 1627.

Solution:

-

For more information about this error please refer:
http://www.symantec.com/docs/TECH69392

 

 

Installation of license keys/Agent in evaluation mode in Backup Exec fails with error "Failed to install SQL Express BKUPEXEC instance: error 1627

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


Installation of license keys in Backup Exec fails with "Failed to install SQL Express BKUPEXEC instance error 1627"

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

 

 

Error 1706:

Cause:

While installing Backup Exec, the installation of SQL Express 2005 may fail with the error Failed to install SQL Express BKUPEXEC instance with error 1706. if Backup Exec is installed on a server that has an existing MSDE or SQL instance already present.

Solution:

1. Uninstall the Microsoft SQL Server Setup Support Files by using Add or Remove Programs as shown below.
2. Run setup for Backup Exec again

For more information about this error please refer:
http://www.symantec.com/docs/TECH125334

 

 


Installation of SQL Express 2005 fails the error:


Failed to install SQL Express BKUPEXEC instance with error 1706.


Resolution:
 http://support.veritas.com/docs/286092
 

 

 

Error 2749:

Cause:

An older or incompatible vesion of Microsoft SQL Managemet Studio is installed on the media server, which prevents the installation of SQL Express with the Backup Exec 2012 installation.

Solution:

Using Control Panel, uninstall SQL Management Studio from the media server. Then Backup Exec installation should be successful.

For more information about this error please refer to:  

 

Error 2908:

Cause:

An older or incompatible vesion of Microsoft SQL Managemet Studio is installed on the media server, which prevents the installation of SQL Express with the Backup Exec 2012 installation.

Solution:

Using Control Panel, uninstall SQL Management Studio from the media server. Then Backup Exec installation should be successful.

For more information about this error please refer to:  

 

The Backup Exec installation log displays the following error:


V-225-53: ERROR: Failed to install SQL Express BKUPEXEC instance with error 2908.

Please review C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt for more details.

Failed to install third party products

Resolution:

SQL Express installation fails with Error 2908. The installer has encountered an unexpected error. The error code is 2908. Could not register component {1F3316BE-825B-4390-A9D2-AF3EECCAE9F6}.

 http://seer.entsupport.symantec.com/docs/301105.htm

 

 

Error 15151:

Cause:

The issue occurs because Active Directory contains any of the following groups: sa, Sa, sA, SA

Solution:


Change the Authentication Mode for SQL to mixed

OR

Rename the SA Group in Active Directory

Review the following Microsoft Article for more information:

Error message when you install SQL Server 2005: "Cannot alter the login 'sa', because it does not exist or you do not have permission"
 http://support.microsoft.com/kb/917827

 

 

 

 

Error 15359:

Cause:

This issue can occur when the date/time on the system have been have been set incorrectly.

Solution:

Make sure that the date/time and time zone are set correctly.
 
For more information about why this issue can occur when installing SQL for an application, review the following Microsoft Article:

SQL Failure Occurs During the Installation of HPC Pack 2008
http://support.microsoft.com/kb/2004738

 

For more information about this error please refer:
http://www.symantec.com/docs/TECH127171

 

Error 28062:

Cause:

This issue occurs if the installation is performed to a compressed folder.

Solution:

Verify that the folder to which the installation is being performed, is not a compressed folder, per the following steps:


1. Right-click the installation folder, and then click Properties.
2. Click the General tab, and then click Advanced.
3. Click to clear the Compress contents to save disk space check box.
4. Click OK two times.
The installation should now complete successfully.
  

 

The following error is reported in Backup Exec installation log (bkupinst.htm):


<V-225-53>: ERROR: Failed to install SQL Express BKUPEXEC instance with error 28062.

Please review C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt for more details.

Failed to install third party products.


The summary.txt log shows the following error:


Product : Microsoft SQL Server 2005 Express Edition

Install : Failed

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0009_SEIBER_SQL.log

Error String : SQL Server Setup cannot install files to the compressed or encrypted folder: C:\Program Files\Microsoft SQL Server\. To continue, make sure that your installation directories are not compressed or encrypted, or specify a different directory, and then run SQL Server Setup again.

 

 

Error 28086:

 

The following error is reported in Backup Exec installation log (bkupinst.htm):


<V-225-53>: ERROR: Failed to install SQL Express BKUPEXEC instance with error 28086.

Please review C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt for more details.

Failed to install third party products.


Cause:
An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.

 

Solution:

 


This usually occurs after an attempted manual uninstall of the previous version of Backup Exec, to completely remove the SQL instance, follow these steps:

1. Manual uninstall of 11d and 12.x:  http://support.veritas.com/docs/287320
2. Manual uninstall of 9.x and 10.x:  http://support.veritas.com/docs/250510

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.

3. Go to HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server
4. Remove BKUPEXEC from the REG_MULTI_SZ value named InstalledInstances
5. Look through all subhives named MSSQL.# for an entry including BKUPEXEC as the (Default) key in the subhive or expand to HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\MSSQL.#\MSSQLServer\SuperSocketNetLib\Np within the PipeName string value. (where # is any number)
6. Delete the subhive named MSSQL.# (where # is the number discovered from searching in step 5)
7. Delete the subhive named BKUPEXEC
8. Go to HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\Instance Names\SQL
9. Delete the value named BKUPEXEC
10. Delete the folder %ProgramFiles%\Microsoft SQL Server\MSSQL.# (where # is the number discovered from searching in step 5)

Install Backup Exec for Windows Servers. The installation should now complete successfully.


V-225-55: "A Release Candidate version of Microsoft .NET Framework was found on the Media Server. Remove it using Add/Remove programs, then restart the Backup Exec installation" occurs when attempting to install Backup Exec for Windows Servers.  http://support.veritas.com/docs/295712
 

`-

For more information about this error please refer to:  

 

Error 28111:

Cause:

 

An installation of SQL Express 2005 fails with


ERROR: Failed to install SQL Express BKUPEXEC instance with error 28111.


The Summary.txt file from the failed SQL installation contains the following information:


Last Action     : DetectExistingData

Error String    : SQL Server Setup cannot write system databases to C:\Program Files\Microsoft SQL Server\MSSQL$BKUPEXEC\Data\, because it contains files from a previous installation. To continue, move the databases from the specified folder, or specify a different installation folder. Then run SQL Server Setup again.

 

This is very similar to Error 28086 above where the previous installation of SQL Express was incorrectly or insufficiently uninstalled and

Solution:

Follow the directions listed above to thoroughly remove the previous installation and instance in order to resolve. In addition to the above instructions, if it can be confirmed that no other applications are using SQL Express-hosted databases, it is safe to uninstall all of the application from Add or Remove Programs and to remove the entire \Microsoft SQL Express folder.

 

Error 28115:

 

 

An upgrade of SQL Express 2005 fails with:


Failed to install SQL Express BKUPEXEC instance with error 28115" in the installation log.


Resolution:
 http://support.veritas.com/docs/289045

For more information about SQL 2005 Express, review the following Microsoft Article:

SQL Server 2005 Express Edition Readme
 http://support.microsoft.com/kb/910229

 

Error 29508:

Cause:

Installation of Backup Exec SQL Express Instance fails with error 29508

Solution:

1. Create a group account in Active Directory on the Domain Controller  by name SQLServer2005SQLBrowserUser$SERVERNAME where SERVERNAME is the name of the server on which you would be installing Backup Exec.

For example : If the name of the server on which you are installing Baclup Exec is BKUPSRV then the name of the group that you need to create would be SQLServer2005SQLBrowserUser$BKUPSRV

To create a group account in Active Directory on the Domain Controller

A.Click Start, point to Programs, point to Administrative Tools, and then click Active Directory Users and Computers.

B.In Active Directory Users and Computers window, expand <domain name>.com

C.In the console tree, right-click the folder in which you want to add a new group.

D.Click New, and then click Group.

E.Type the name of the new group. Use a name that you can easily associate with the role or service for which you are creating.

F.In the New Object - Group dialog box, do the following:

    In Group scope, click Global scope.

    In Group type, click Security.

G.Click Finish.

2. Run the Symantec Backup Exec Installation again.

 

For more information about this error please refer:
http://www.symantec.com/docs/TECH71380

 

Error 29552:

 

 

Upgrade from Backup Exec for Windows Servers 10d to 11d or above fails because the MSDE upgrade to SQL Express fails (Error 29552)

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


Upgrading Backup Exec fails to upgrade the named MSDE Instance of Backup Exec to SQL Express with "Failed to install SQL Express BKUPEXEC instance error 29552

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

 

 

Error 70045:

Installation Failed to install SQL Express BKUPEXEC instance error 70045

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

 


Supplemental Materials

SourceUMI
ValueV-225-53
Description

Failed to install SQL Express BKUPEXEC instance

 


SourceETrack
Value1167203
Description

INS: SQL: Install failed with error V- 225-53

 


SourceError Code
Value102
Description

Failed to install SQL Express BKUPEXEC Instance.


SourceError Code
Value1402
Description

An installation package for the product Microsoft SQL Native Client cannot be found.


SourceEvent ID
Value28062
Description

Failed to install SQL Express BKUPEXEC instance.


SourceEvent ID
Value28115
Description

Failed to install SQL Express BKUPEXEC instance.


SourceEvent ID
Value28086
Description

Failed to install SQL Express BKUPEXEC Instance.


SourceEvent ID
Value28111
Description

Failed to install SQL Express BKUPEXEC instance.


SourceError Code
Value2908
Description

Failed to install SQL Express BKUPEXEC instance.


SourceError Code
Value1706
Description

Failed to install SQL Express BKUPEXEC instance with error 1706



Legacy ID



294764


Article URL http://www.symantec.com/docs/TECH56006


Terms of use for this information are found in Legal Notices