Backup Exec Device and Media Service fails to start

book

Article ID: 100028913

calendar_today

Updated On:

Description

Error Message

Dbrecover Log :

 

OS ERROR: 0x80040e4d (-2147217843)
GetDatabaseStatus
OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=master;Data Source=ServerName\BkupExec;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x80040e4d
Error connecting to master database: hr = 0x80040e4d
OS ERROR: 0x80040e4d (-2147217843)
Status of database BEDB is unknown
File Exist Check: \\ServerName\C$\Program Files\Symantec\Backup Exec\Data\BEDB_dat.mdf
File Exist: FALSE
File Exist Check: \\ServerName\C$\Program Files\Symantec\Backup Exec\Data\BEDB.bak
File Exist: FALSE
File Exist Check: \\ServerName\C$\Program Files\Symantec\Backup Exec\Data\BEDB_dat.bak
File Exist: FALSE
Deinitialize...

-----------------------------
Process completed 

Status: DBU_ERROR_BASE_FILE_NOT_EXIST
 

Event Viewer reports :

 

Log Name: Application
Source: Backup Exec
Date: 
Event ID: 58068
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: ServerName
Description:
The Backup Exec Device and Media Service could not start because the database recovery has failed. Refer to the database recovery log for details

 

Log Name: Application
Source: MSSQL$BKUPEXEC
Date: 
Event ID: 18452
Task Category: (4)
Level: Information
Keywords: Classic,Audit Failure
User: N/A
Computer: ServerName
Description:
Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: IP Address]

 

Log Name: Application
Source: MSSQL$BKUPEXEC
Date:
Event ID: 17806
Task Category: (4)
Level: Error
Keywords: Classic
User: N/A
Computer: ServerName
Description:
SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: IP Address]

 

UDL Test to the Backup Exec Instance also fails 

UMI Code: V-379-58068

Resolution

1.Edit the registry using regedit. (start -> run ->Regedit )

 

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

 

2.Browse to : HKLM\System\CurrentControlSet\Control\LSA

 

3.Add a DWORD value called “DisableLoopbackCheck”

 

4.Set this value to 1

 

Perform the udl test with the Backup Exec instance and it should work. The Backup Exec Device and Media service should also start now

 

Issue/Introduction

Backup Exec Device and Media Service fails to start