Backup Exec upgrade fails with error -2067920939 when installing the SQL Express BKUPEXEC instance
|Article:TECH216804|||||Created: 2014-04-18|||||Updated: 2014-11-12|||||Article URL http://www.symantec.com/docs/TECH216804|
Backup Exec upgrade fails with an error in the Bkupinst2014.htm log file when installing the SQL Express BKUPEXEC instance.
Backup Exec upgrade fails with the following error in the Bkupinst2014.htm log file:
V-225-53: ERROR: Failed to install SQL Express BKUPEXEC instance with error -2067920939.
Summary.txt file reports the following:
Exit code (Decimal): -2067920939
Exit message: The SQL Server service cannot be restarted; or for a clustered instance, the SQL server resource is not online.
The SQL Server health check fails because it cannot stop the MSSQL$BKUPEXEC service during the upgrade. There is a temporary mismatch between the requested control and the state of the service to be controlled. The service may be in a state of start-pending, stop-pending, or stopped.
The Service Control Manager reports the following when it attempts to stop running the service:
TITLE: SQL Server 2008 R2 Setup
The following error has occurred:
The service cannot accept control messages at this time.
Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.4000.0&EvtType=0x711E9E17%25400xC24842DB
Reboot the computer to reset the MSSQL$BKUPEXEC service state. This enables Backup Exec to upgrade SQL 2005 Express to SQL 2008 Express R2 SP2.
If the reboot does not solve the issue, please check the server's local security group called 'Debug programs' and make sure that the 'Administrators' security group is listed. To get to the setting, please click the Start button > Administrative tools > Local Security Policy. Then expand 'Local policies' and highlight 'User Rights Assignment'. Locate the 'Debug programs' security policy from the list and add the 'Administrators' group if it isn't present.(Figure 1.) If you do make changes to the security group please log out and then log back in for it to take effect, then try the install process again.
Article URL http://www.symantec.com/docs/TECH216804