Error Message

V-225-302: ERROR: Failed to install SQL Express BKUPEXEC instance with error XXXXXXXXXXX . ***To search for information about this error, click here 
Please review C:\Program Files (x86)\Microsoft SQL Server\120\Setup Bootstrap\LOG\Summary.txt for more details.

The return value for Microsoft SQL Express returned error code: XXXXXXXXXXX



Example(s):

Backup Exec Installation Log:  C:\Program Files\Veritas\Backup Exec\Logs\BKUPINST16.html

Error: - 2067922935

V-225-302: ERROR: Failed to install SQL Express BKUPEXEC instance with error --2067922935. ***To search for information about this error, click here 
Please review C:\Program Files (x86)\Microsoft SQL Server\120\Setup Bootstrap\LOG\Summary.txt for more details.


Summary.txt

C:\Program Files (x86)\Microsoft SQL Server\120\Setup Bootstrap\LOG\Summary.txt

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2067922935
  Exit facility code:            1214
  Exit error code:               9
  Exit message:                  SQL Server installation media on a network share or in a custom folder can cause installation failure if the total length of the path exceeds 260 characters. To correct this issue, utilize Net Use functionality or shorten the path name to the SQL Server setup.exe file.

Review the Backup Exec installation log for the returned error code from the SQL Express Installation.

V-225-302:  ERROR: Failed to install SQL Express BKUPEXEC instance with error:  xxxxxxxxxx

Note: There are potentially an infinite number of SQL installation error return codes. The following are examples are some of the specific SQL upgrade Error Codes and Return messages that have been reported to Veritas.

To understand which cause may apply to the problem being experienced, reviewing the Backup Exec installation log for the returned SQL Express installation error code  and SQL Summary.txt log.


Cause 1:
Error: 16389.
The installation path for the Backup Exec installation is longer that 65 characters.
The install path should be 65 characters or less.


Cause 2:
Error: -2067922935  (0x986DD6CB)
The installation path for the Backup Exec installation is longer that 84 characters.
The install path should be 65 characters or less.


Cause 3:
Error: -2067922935  (0x986DD6CB)
The installation path for the Backup Exec installation is longer that 84 characters.
The install path should be 260 characters or less.  <- Note: SQL Installation Return Message


Cause 4:
Error: -2061893606 (0x851A001A)
The upgrade from SQL Server 2005 Express instance to SQL 2008 R2 and then to SQL 2012 or SQL 2014 fails at the last steps when executing the SQL Express installation upgrade scripts.


Cause 5:
Error: -2068051813 (0x84BC089B)
The system variable "TMP" or "TEMP" has the invalid path.

Backup Exec 16 (FP1) Feature Pack 1 has introduced a new install path check during the installation or upgrade.
Previous Backup Exec versions used older versions of SQL Express,
newer versions of the SQL Express installer have path depth limitations. Due to Backup Exec's use of newer SQL Express versions, Backup Exec 16 FP1 and greater installations will fail if the install path is too deep.

For Backup Exec 16 FP1 and greater the install path must be less than 50 characters in length to prevent any potentioal Microsoft SQL Express installation path related errors.

Backup Exec 16 FP1 Install Log Message

Install Media Path: C:\Install Media ISOs\Application Software\Backup Exec\Bacup Exec 16\FP2\BE1142.1632RSP2\Install

The root of the Backup Exec installation media path cannot exceed 50 characters in length. You must shorten the path name, and then run the installation again. If this error persists, move the installation media to the root of a local drive and then run the install again.

V-225-01001001-4: Error initializing shared data ***To search for information about this error, click here
ERROR: Installation failed with error 1603. GetLastError = :0

 

 

Note: If the steps below do not resolve the issue, please contact Veritas Technical Support for  further assistance.


Solution for Cause 1: Error 16389
Mount the Backup Exec 16 Installation ISO or Extract the install media to a root folder and perform the Backup Exec 16 upgrade.


Solution for cause 2: Error -2067922935  (0x986DD6CB)
Mount the Backup Exec 16 Installation ISO or Extract the install media to a root folder and perform the Backup Exec 16 upgrade.


Solution for cause 3: Error -2067922935  (0x986DD6CB)
Mount the Backup Exec 16 Installation ISO or Extract the install media to a root folder and perform the Backup Exec 16 upgrade.


Solution for cause 4: Error: -2061893606 (0x851A001A)
The current workaround is to start the SQL BKUPEXEC service and re-run the Backup Exec 16 upgrade or Reboot the Backup Exec server and re-run the upgrade.


Solution for cause 5: Error: -2068051813 (0x84BC089B)
Confirm whether TMP or TEMP has the valid path in System variables in addition to User variables. (See Fig 1)

Fig 1.

 

SQL Server 2014 SP2 Express fails to upgrade from SQL Server 2005, 2008 R2, or 2012 Express during the Backup Exec 16 server upgrade.

UMI: V-225-302: UMI: V-225-01001001-4: