Beuility is a gui now. Join our community for more solutions or to ask questions. Cool! Submit your e-mail address below. this contact form
Ensure to enable the Advanced Open File Option (AOFO) from the backup job properties under "Settings" and "Advanced Open File". Check "Use Advanced Open File Option". (If AOFO is already enabled, Privacy Load More Comments Forgot Password? Start Download Corporate E-mail Address: You forgot to provide an Email Address. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Backup Exec Device and Media service fails to start with the message
Please wait...12-14-2007,08:43:06 : DISABLECANCEL12-14-2007,08:43:06 : Installing BE services.12-14-2007,08:43:06 : Setting BEWS SQL service credentials.12-14-2007,08:43:11 : Error returned from OpenSCManager: 172212-14-2007,08:43:11 : Error returned from OpenSCManager: 172212-14-2007,08:43:11 : SQL Service credentials are Please run the chkdsk utility on the volume
Go back to the main beutility window and right clicked on the new media server name and hit start services. I think it may have actually worked!starting Backup Exec....Wow, it did. Contact TechTarget at 275 Grove Street, Newton, MA. recovering from backups Load More View All Manage Four data copy management misconceptions that affect your business What are some flat backup misconceptions?
Open beutility.exe 2. Right click the server and choose "Recover Database" 6. Please examine your job log or catalogs to ensure this directory tree was backed up in its entirety. To fix such error, ensure that the listed resource is available and OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=master;Data Source=atlhr;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x0 Database BEDB does not exist Fixing up any database linkage problems for 'BEDB' Execute command: declare @@stemp
Create a SymAccount now!' The error "The database specified does not exist" is displayed when trying to start the Backup Exec Device And Media service after the installation or upgrade of Get 1:1 Help Now Advertise Here Enjoyed your answer? Solution Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Thanks BajanDude, that saved me hours.
In some cases, it can be related to a problem with the Microsoft .NET Framework. Email Address (Optional) Your feedback has been submitted successfully! TCP Port 10000 for Network Data Management Protocol (NDMP) that Backup Exec uses is being shared or block by another application on the remote machine. 4. Another backup software is running SearchITChannel New SUSE partner program offers product training, rebates SUSE's new channel program offers rebates of up to 30% to partners who train and certify their sales and engineering personnel on...
Join & Ask a Question Need Help in Real-Time? weblink Right-click on the BEDB database 3. It is a good idea to initially check for updates to the .NET Framework. Backup Exec database is offline, turn it on and then restart the Backup Exec Services." Correcting this error can sometimes be as simple as entering Services.msc at the server's Run prompt
Changes made in Active directory or workgroup with regards to the User name or password used by Backup Exec (Service Account or Logon Account). 3. Thank you for your feedback! The upgrades center on data recovery, workflow ... http://onlinetvsoftware.net/backup-exec/backup-exec-unknown-database-error-12.php This Article Covers Backup software RELATED TOPICS Archiving Virtual server backup Cloud backup Looking for something else?
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. Nothing will be saved from my previous installation will it? 0 LVL 28 Overall: Level 28 Storage Software 28 MS SQL Server 2005 3 Message Accepted Solution by:honmapog2009-02-15 Try the Click OK to Perform analysis of your machine and automatically determine the release version.
I recommend downloading and installing the latest device drivers for your tape drive. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.HKLM\Software\Symantec\Backup Exec for Windows\ADAMM\Check the Database Server Name key to verify server Thank You! Sometimes Error 1053 is related to a permissions problem that keeps the database or one of the Backup Exec Services from starting.
Symantec Backup Exec has been around in one form or another since the early 1990s and has a reputation as one of the more reliable backup products on the market. Thank you! 0 Kudos Reply Re: "Error 1065: The database specified does not exist" problem Grant_Scheffert Level 2 Partner 10-25-2005 09:58 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Five challenges when buying backup and restore software Veritas, Veeam top choices of data backup app users Copy management systems demystified Load More View All Evaluate Develop copy management systems for his comment is here This error can occur because of one of the reasons mentioned below: 1.
Please provide a Corporate E-mail Address. How an effective data archiving system can ease backup woes TECHNOLOGIES Error & error handling Storage Backup PRODUCTS Symantec Backup Exec + Show More In this Article Share this item with Veritas does not guarantee the accuracy regarding the completeness of the translation. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application.
Choose "Drop database and reload from base". 3. In most of the cases I have seen, the problem is connected to a permissions issue related to the account being used to run the service. I’ve removed Backup Exec and removed the MSSQL$BKUPEXEC and Veritas directories, and then rebooted and reinstalled again. Oftentimes, you can force a service to start by right-clicking on it and choosing the Start command from the shortcut menu.
It is possible that updates have been made to the original version after this document was translated and published. They are in the data.cab file.