Forum Discussion

Lucano99's avatar
Lucano99
Level 3
7 years ago

cannot install BE 2016

Hello, anybody had an issue and solved within this error message?

we are running BE 2015 and trying 2016 version (becuase it should have a support for QNAP NAS device)

<br
+ 08-21-2018,14:28:44 : V-225-302: ERROR: Failed to install SQL Express BKUPEXEC instance with error -2068709374. ***To search for information about this error, click here
+ 08-21-2018,14:28:44 : Please review C:\Program Files (x86)\Microsoft SQL Server\120\Setup Bootstrap\LOG\Summary.txt for more details.
08-21-2018,14:28:45 : The return value for Microsoft SQL Express returned error code: 2226257922
08-21-2018,14:28:45 : Clean up Symantec installer keys.
08-21-2018,14:28:46 : Terminal Services enabled.
08-21-2018,14:28:46 : Failure Detected during Install Progress
08-21-2018,14:28:46 : Running BE_RollbackBEDB
08-21-2018,14:28:46 : Param file C:\ProgramData\Veritas\Backup Exec\{FB3C7BA9-7D12-4B6D-9260-F5488D7056B4}\BEInstParams.prm is not available.
08-21-2018,14:28:46 : Executing BE_DetachDB.
08-21-2018,14:28:46 : Executing Detach_BEDB.
08-21-2018,14:28:46 : SQL_GetServiceName. GetComputerName
08-21-2018,14:28:46 : CZPRWS0002
08-21-2018,14:28:49 : The SQL server CZPRWS0002\BKUPEXEC with service name of MSSQL$BKUPEXEC has been started
08-21-2018,14:28:49 : DRIVER={SQL Server Native Client 11.0};SERVER=CZPRWS0002\BKUPEXEC;Trusted_Connection=Yes
08-21-2018,14:28:49 : Unsuccessful return code from SQL statement: SELECT state_desc DatabaseStatus_sysDatabase FROM sys.databases WHERE name = 'BEDB'
08-21-2018,14:28:49 : Stopping BEDB SQL service
08-21-2018,14:28:49 : Upgrade rollback. Replace damaged BEDB with backed up version of previous BEDB mdf and ldf files.
08-21-2018,14:28:49 : BEDB file C:\Program Files\Symantec\Backup Exec\Data\BEDB_dat.mdf has been updated with C:\Program Files\Symantec\Backup Exec\Data\DataBackup2018-08-21-02-25-29\Data\BEDB_dat.mdf.
08-21-2018,14:28:49 : BEDB file C:\Program Files\Symantec\Backup Exec\Data\BEDB_log.ldf has been updated with C:\Program Files\Symantec\Backup Exec\Data\DataBackup2018-08-21-02-25-29\Data\BEDB_log.ldf.
08-21-2018,14:28:49 : Running BE_AttachDB
08-21-2018,14:28:49 : GetClusterUpgradeState returning 0
08-21-2018,14:28:49 : Param file C:\ProgramData\Veritas\Backup Exec\{FB3C7BA9-7D12-4B6D-9260-F5488D7056B4}\BEInstParams.prm is not available.
08-21-2018,14:28:49 : Executing Attach_BEDB.
08-21-2018,14:28:49 : SQL_GetServiceName. GetComputerName
08-21-2018,14:28:49 : CZPRWS0002
08-21-2018,14:28:49 : DRIVER={SQL Server Native Client 11.0};SERVER=CZPRWS0002\BKUPEXEC;Trusted_Connection=Yes
08-21-2018,14:28:50 : Connected to SQL Server.
08-21-2018,14:28:50 : Unsuccessful return code from SQL statement: SELECT state_desc DatabaseStatus_sysDatabase FROM sys.databases WHERE name = 'BEDB'
08-21-2018,14:28:50 : Attaching BEDB to SQL Server.
08-21-2018,14:28:50 : 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'
08-21-2018,14:28:50 : BEDB has been succesfully attached to SQL Server.
08-21-2018,14:28:50 : Change BEDB owner to SA user.
08-21-2018,14:28:50 : Successfully changed BEDB owner to sa.
08-21-2018,14:28:50 : Installer will start the BE services
08-21-2018,14:28:51 : Successfully started service - bedbg. Elapsed time: 1295 ms.
08-21-2018,14:28:51 : Successfully started service - MSSQL$BKUPEXEC. Elapsed time: 0 ms.
08-21-2018,14:29:00 : Successfully started service - BackupExecAgentAccelerator. Elapsed time: 9204 ms.
08-21-2018,14:29:08 : Successfully started service - BackupExecDeviceMediaService. Elapsed time: 7551 ms.
08-21- : Successfully started service - BackupExecDeviceMediaServiCService. Elapsed time: 16302 ms.
08-21-2018,14:29:26 : Successfully started service - BackupExecAgentBrowser. Elapsed time: 1513 ms.
08-21-2018,14:29:37 : Successfully started service - BackupExecManagementService. Elapsed time: 11357 ms.
08-21-2018,14:29:38 : Successfully started service - BackupExecJobEngine. Elapsed time: 1529 ms.
08-21-2018,14:29:38 : ERROR: Failed to start service - elementmgr. Elapsed time: 0 ms. Error: Service handle null.
08-21-2018,15:29:18 : Skipping push of remote servers and agents due to failed local install.
08-21-2018,15:29:18 : BeSeqDlgs::DlgInstallComplete
08-21-2018,15:29:18 : AgentSeqDlgs::Misc_BE_CommonOps
08-21-2018,15:29:18 : Dialog Sequence Returning errorlevel -2068709374
08-21-2018,15:29:18 : Setting up failed completion dialog.
08-21-2018,15:29:18 : Setting up failed completion dialog (Install).
08-21-2018,15:29:18 : Initialize the telemetry items on the dialog
08-21-2018,15:29:18 : GetClusterUpgradeState returning 0
08-21-2018,15:29:18 : GetClusterUpgradeState returning 0
08-21-2018,15:29:18 : Skipping push of remote servers and agents due to failed local install.



16
Windows Server 2008 R2

4 Replies

Sort By
  • P_Jeal's avatar
    P_Jeal
    Moderator
    7 years ago

    Having checked the HCL for BE15, that version already supports the QNAP Business NAS devices (TS-809 series, TS-x39 series, TS-x59 series, TS-x69 series, TS-x79 series), but it does not appear that BE16 or BE20.x supports any additional devices besides those. Please see BE15 HCL https://www.veritas.com/content/support/en_US/doc/BE_15_HCL (page 30)  and BE16 HCL  https://www.veritas.com/content/support/en_US/doc/BE_16_HCL  (page 37).

    As to this error, the actual cause for the SQL failure will likely be shown earlier than in the BKUPINST16.html  log or in the C:\Program Files (x86)\Microsoft SQL Server\120\Setup Bootstrap\LOG\Summary.txt  file mentioned, as the error shown here is only the resulting failure.

    • Lucano99's avatar
      Lucano99
      Level 3
      7 years ago

      Hi,

       

      we need to connect the BE with the TS-1273U...

       

      do you think it will be possible?

      • P_Jeal's avatar
        P_Jeal
        Moderator
        7 years ago

        Unfortunately that device does not appear to be one mentioned in any of the Backup Exec HCL. It may work with Backup Exec, but there are no guarantees that you might not encounter some issues, especially if planning to use that for Deduplication storage or with GRT data sets.

        That said, it is still recommended that your version of Backup Exec is upgraded to either BE16 or preferably BE20, as BE15 went into End of Standard Support late last year and we will stop supporting that completely in November next year. See article https://www.veritas.com/support/en_US/article.100038900.html