Backup Exec Device & Media Service Error #1065
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing the backup exec device & media service service terminated with service specific error 536928979 Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange the backup exec device and media service could not start because the database recovery has failed Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet The Backup Exec Device and Media Service terminated with service-specific error 536928979 Article:000033398 Publish: Article URL:http://www.veritas.com/docs/000033398 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem The Backup Exec Device and Media Service terminated with service-specific error 536928979 Error Message Backup Exec Device and Media Service fails to start with error 536928979 Windows System Event log error: Event Type: ErrorEvent Source: Service Control ManagerEvent Category: NoneEvent ID: 7024Date: 3/20/2008Time: 3:01:36 PMUser: N/A Description:The Backup Exec Device and Media Service terminated with service-specific error 0x2000e2d3 (536928979). For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Cause This error occurs when the Backup Exec Device and Media Service is unable to communicate successfully with Backup Exec SQL Instance. Solution Possible Solutions: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. Please follow the steps mentioned below t
Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Backup Exec service fails to start with error 1065: the database specified does not exist Want to Advertise Here? Solved Backup Exec service fails to start with error 1065: the database specified does not exist Posted on 2007-12-19 Storage Software SBS 1 Verified Solution 2 Comments 5,314 Views Last Modified: https://www.veritas.com/support/en_US/article.TECH59527 2013-12-01 I've just installed Backup Exec 10d on a server and when I try to start the "Backup Exec Device & Media Service" I get the error: "Could not start the Backup Exec Device & Media Service on Local Computer. Error 1065: The database specified does not exist". I've verified that the "MSSQL$BKUPEXEC" service is running. I've also tried different logons for the service - Local System, and an AD account I created https://www.experts-exchange.com/questions/23034807/Backup-Exec-service-fails-to-start-with-error-1065-the-database-specified-does-not-exist.html in the appropriate groups called s-backupexec. This is on Small Business Server 2003 Standard. Any ideas? Thanks, Daniel 0 Question by:djMundy Facebook Twitter LinkedIn Google LVL 7 Best Solution bydjMundy I figured this out myself. I found this link on Symantec's knowledgebase: http://seer.entsupport.symantec.com/docs/274102.htm To detach and re-attach the Backup Exec Database using OSQL If the Backup Go to Solution 1 Comment LVL 7 Overall: Level 7 SBS 2 Storage Software 1 Message Accepted Solution by:djMundy2007-12-19 I figured this out myself. I found this link on Symantec's knowledgebase: http://seer.entsupport.symantec.com/docs/274102.htm To detach and re-attach the Backup Exec Database using OSQL If the Backup Exec (tm) Device and Media Service does not start, with the error "Database specified does not exist," there might be a communication issue with the Backup Exec Database (BEDB) and Backup Exec. The Backup Exec Database can be detached and re-attached to recover the connection. This alerted me to the fact that my database was missing. The following files were missing from C:\Program Files\VERITAS\Backup Exec\NT\Data BEDB.bak BEDB_dat.bak BEDB_dat.mdf BEDB_log.ldf They should all be created by the Backup Exec install process, but weren't. I copied the first two files from another server which had the same version of Backup Exec, and used beutility.exe (in C:\Program Files\VERITAS\Backup Exec\NT) to recover the database to it's default state: 1
Join INTELLIGENT WORK FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your http://www.tek-tips.com/viewthread.cfm?qid=906765 Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140val-all.htm e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code backup exec below into your site. Symantec: Backup Exec back-up Forum at Tek-Tips HomeForumsServer RackBack-up SystemsSymantec: Backup Exec back-up Forum ERROR 1065 DB does not exist thread481-906765 Forum Search FAQs Links MVPs ERROR 1065 DB does not exist ERROR 1065 DB does not exist IT4UATDLC (IS/IT--Management) (OP) 26 Aug 04 08:17 I am installing Veritas BUE 9.1 on an intel server and everything appears to install correctly and the install in fact completes.However, when backup exec device I try to start the program it tells me it has not connected to the media server.After looking into why I noticed the service for devices and media will not start.The error the service returns is Error 1065 The database specified does not exist.The BackupExec SQL server service has started and both dependent services MSSQL$BKUPEXEC and RPC have started.Anyone have any ideas as to where I can look next or what the problem is?Thanks RE: ERROR 1065 DB does not exist Mthales (TechnicalUser) 9 Nov 04 12:19 Have you had any luck resolving this issue because I have a the same problem going on.M RE: ERROR 1065 DB does not exist paulmcw (TechnicalUser) 30 Nov 04 11:10 Although I didn't encounter the error under the exact same circumstances, I have seen error 1065 occur on some of my media servers after they have been running successfully for months. I've consulted Veritas, and so far haven't been able to pinpoint the root cause of the 1065 error. Veritas suggested running the MDAC checker on the media server to fix mismatched dll's.To date, I've found that the only reliable fix is to launch the Backup Exec "repair" option on the affected server. This always fixes the 1065 problem. In addition, all backup jobs & history are still there!HTH R
is important to note that the items on this list are cryptographic modules. A module may either be an embedded component of a product or application, or a complete product in-and-of-itself. If the cryptographic module is a component of a larger product or application, one should contact the product or application vendor in order to determine how the product utilizes the embedded validated cryptographic module. There may be a larger number of security products or applications available which use an embedded validated cryptographic module, than the number of modules which are found in this list. In addition, other vendors, who are not found in this list, may incorporate a validated cryptographic module from this list embedded into their own products.When selecting a module from a vendor, verify that the module is either the product or application itself (e.g. VPN, SmartCard, USB memory token, etc.) or the module is embedded in a larger product or application (e.g. toolkit, etc.). If the module is embedded in a product or application, ask the product or application vendor to provide a signed letter or statement affirming that the unmodified validated cryptographic module is integrated in the solution; the module provides all the cryptographic services in the solution; and provide reference to the modules validation certificate number from this listing.NOTE1: Module descriptions are provided by the module vendors and have not been verified for accuracy by the CMVP. The descriptions do not imply endorsement by the U.S. or Canadian Governments or NIST. Additionally, the descriptions may not necessarily reflect the capabilities of the modules when operated in the FIPS-Approved mode. The algorithms, protocols, and cryptographic functions listed as "other algorithms" (e.g. allowed or non-FIPS-Approved algorithms) have not been tested through the CMVP.NOTE2: The operator of a cryptographic module is responsible for ensuring that the algorithms and key lengths are in compliance with the requirements of NIST SP 800-131A.NOTE3: All questions regarding the implementation and/or use of any module located on the CMVP module validation lists should first be directed to the appropriate vendor point-of-contact (listed for each entry).Please contact the CMVP if any errors are discovered or comments with suggestions for improvement of