Backup Exec Device and Media Service cannot start because the database recovery has failed

Problem

Backup Exec Device and Media Service cannot start because the database recovery has failed .

Error Message

UDL connectivity test with the Backup Exec Database also fails with "Cannot generate SSPI context"

How to perform a UDL test / a quick test connection to the Backup Exec SQL instance

UMI Code: V-379-58068

Solution

Follow these steps:

1. Click Start, click Run, type Adsiedit.msc, and then click OK.
2. In the ADSI Edit snap-in, expand Domain [DomainName], expand DC= RootDomainName, expand CN=Users, right-click CN= AccountName, and then click Properties.

Note :
 
DomainName is a placeholder for the name of the domain.
RootDomainName is a placeholder for the name of the root domain.
AccountName is a placeholder for the account that you specify to start the SQL Server service.
If you specify the Local System account to start the SQL Server service, AccountName is a placeholder for the account that you use to log on to Microsoft Windows.
If you specify a domain user account to start the SQL Server service, AccountName is a placeholder for the domain user account.

3. In the CN= AccountName Properties dialog box, click the Security tab. On the Security tab, click Advanced.
4. In the Advanced Security Settings dialog box, make sure that SELF is listed under Permission entries. If SELF is not listed, click Add, and then add SELF.
5. Under Permission entries, click SELF, and then click Edit.
6. In the Permission Entry dialog box, click the Properties tab.
7. On the Properties tab, click This object only in the Apply onto list, and then make sure that the check boxes for the following permissions are selected under Permissions:

Read servicePrincipalName
Write servicePrincipalName
Click OK three times, and then exit the ADSI Edit snap-in.

Run gpudate /force

Start the device and media server .

Reference : How to troubleshoot the "Cannot generate SSPI context" error message

Warning : If you use the Active Directory Service Interfaces (ADSI) Edit snap-in, the LDP utility, or any other LDAP version 3 clients and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require that you reinstall Microsoft Windows Server and / or Microsoft Exchange Server. We cannot guarantee that problems caused by incorrectly modifying the attributes of Active Directory objects can be resolved. Modify these attributes at your own risk.

Note :To grant the appropriate permissions and user rights to the SQL Server startup account, you must be logged on as a domain administrator, or you must ask your domain administrator to do this task. 

To configure the SQL Server service to create SPNs dynamically