Backup Exec Device and Media Service fails to start with error 0xe0008144 and Event ID 33152 is logged in Event Viewer showing Adamm Database Event: Open Database Connection Failed

Article:TECH129977  |  Created: 2010-01-13  |  Updated: 2014-10-28  |  Article URL http://www.symantec.com/docs/TECH129977
Article Type
Technical Solution

Product(s)

Issue



Backup Exec Device and Media Service fails to start with error 0xe0008144 and Event ID 33152 is logged in Event Viewer showing Adamm Database Event: Open Database Connection Failed!.

 


Error



Error 0xe0008144 : 0xe0008144

Attempt to start Device and Media Service fails with the above mentioned error.
 

Following Event is seen in the Event Viewer:

Source : Backup exec 
Type : Error
Event ID : 33152
Description :
Adamm Database Event: Open Database Connection Failed!
Error = ERROR DATABASE_DOES_NOT_EXIST
Server = "LOCAL"
Active Node = ""
Instance = "BACKUPEXEC"
Database = "BEDB"
Connection String = "DRIVER=SQL Server:SERVER=LOCAL
\BACKUPEXEC:DATABASE=BEDB:App=BEWS PVL"
The Backup Exec Device and Media Service could not connect to the specified database. Ensure that the specified database is running.

Solution



1. Go To Registry hive HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\BEDatabase 
 
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. Check if "Database Server Name", "Database Instance Name" and " ODBC Driver Connection" Key Values are correctly set.
 
They should be set to:
  • "Database Instance Name"="BKUPEXEC" (Which is the instance of backup exec that is being used)
  • "Database Server Name"="SYMANTEC" (Server name that backup exec is residing on)
  • "ODBC Driver Connection"="DRIVER=SQL Server;SERVER=SYMANTEC\BKUPEXEC;DATABASE=BEDB" (With the previous entries server name that was used)
3. Sometimes the value of "PreviousDjmPrimaryServer" and the value of "Database Server Name" is the same as seen in the Event ID description above. This is because the media server was installed with CASO/MMS option and later it was not removed from CASO/MMS completely. To correct this problem,correct the registry values above with the proper ones and start the service.
 
4.  If all the registry values are correct and the same issue still occurs, please refer to the Related Document below and try the solutions in it.
 
5. Check with this registry values.

6.  If issues persists and media server is Windows 2003, then repair the Microsoft Data Access Components (MDAC) per the following technote:

www.symantec.com/docs/TECH53595

 


Supplemental Materials

SourceEvent ID
Value33152
Description

The Backup Exec Device and Media Service could not connect to the specified database. Ensure that the specified database is running


SourceError Code
Value0xe0008144
Description

Adamm Database Event: Open Database Connection Failed.



Legacy ID



352300


Article URL http://www.symantec.com/docs/TECH129977


Terms of use for this information are found in Legal Notices