Backup Exec Unknown Database Error 12
Contents |
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In an error occurred when writing to the backup exec database CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest backup exec unknown media helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for symantec backup exec unknown media Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : Unknown database error 12 VOX : Backup and Recovery : Backup Exec : Unknown database error
Backup Exec Sql Database
12 Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Unknown database error 12 Brian_Blackwell Level 5 09-26-2005 11:26 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I got this error "after" verify was done. backup exec database maintenance the backup was complete, no errors but the verify had errors. I run 9.1 (latest) and NW6.5 SP3. never seen this error before last weekend. it happened on a full backup that runs every friday night.Job completed: With ERROR - Unknown Database Error 12 Labels: Backup and Recovery Backup Exec 0 Kudos Reply 5 Replies Re: Unknown database error 12 Stumpr2 Level 6 Trusted Advisor 09-27-2005 07:35 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Brian,This same error was discussed in the "VERITAS Technical Services Peer to Peer News Groups"Items in veritas.backupexec.netware.englishHere is a link to the discussions:http://news.support.veritas.com/dnewsweb.exe?utag=&group=veritas.backupexec.netware.english&xrelated=13203&cmd_related=Related+Items 0 Kudos Reply Re: Unknown database error 12 Brian_Blackwell Level 5 09-27-2005 07:45 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content yeah I read that after I posted. but we have had virus scan running in the past and never had a problem. the only change I have made in the past 6 months is add a new netware box t
PKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response Security Simulation Website Security backup exec database maintenance failure SSL Certificates Complete Website Security Code Signing Certificates Norton Shopping
Backup Exec Database Location
Guarantee Buy SSL Products A-Z Services Services Home Business Critical Services Consulting Services Customer Success
Backup Exec Database Repair
Services Cyber Security Services Education Services Solutions Solutions Home Topics Encryption Everywhere Internet of Things Next Generation Endpoint Office 365 Industries Automotive Cyber Insurance https://vox.veritas.com/t5/Backup-Exec/Unknown-database-error-12/td-p/45909 Education Financial Services Global Service Providers Industrial Control Systems Healthcare Retail Government Federal Government State & Local Support Center Technical Support Symantec Connect Buying Programs Upgrades Maintenance & Renewals Training Security Center Security Center Home Blogs ISTR Threats Virus Definitions and Security Updates Removal Tools Partner Find a Partner Become https://support.symantec.com/en_US/article.TECH46484.html a Partner Login Required Login into Partner Portal Partner Licensing Partner Renewals Partner Training Margin Builder Opportunity Registration Financial Benefits English 中文(简体) 中文(繁體) Česká English Français Deutsch Magyar Italiano 日本語 한국어 Polski Português Pусский Español Site: Symantec Enterprise Small Business Norton United States Search Support Home Support Home MySymantec Licensing Products A-Z SYM16-015 Security Advisory Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' Backup job completes with following error message "ERROR - Unknown Database Error 12 " TECH46484 January 6th, 2007 http://www.symantec.com/docs/TECH46484 Support / Backup job completes with following error message "ERROR - Unknown Database Error 12 " Did this article resolve your issue? Thank you for your feedback! Provide feedback on this article Request Assistance Print Article Subscribe to this Article Manage your Subscriptions Search Again Situation Backup job completes with following error message "ERROR - Unknown Databa
AmruthaVarshiniJMarch 29, 20100 0 0 0 Problem Description:https://blogs.msdn.microsoft.com/sqlserverfaq/2010/03/29/unable-to-connect-to-sql-server-2005-from-backupexec-application/ = "urn:schemas-microsoft-com:office:office" /> =============== While connecting to SQL Server 2005 https://www.scribd.com/doc/17875934/Trouble-Shooting-Backup-Exec Express instance through BackupExec application, we might encounter a connection failure. And the following error message would be logged in the Application event viewer logs The Backup Exec Device and Media Service could not start because the database recovery has failed. Refer backup exec to the database recovery log for details. For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml Resolution : ========= · From the error message, we see that media service could not start as the recovery failed on a database · Checked the SQL Server ERRORLOG and found the following errors being logged backup exec database //////////ERRORLOG////////// 2009-08-15 17:03:11.54 spid17s Starting up database ‘BEDB'. 2009-08-15 17:06:00.85 Server SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required. 2009-08-15 17:06:31.90 spid12s Service Broker manager has shut down. 2009-08-15 17:06:31.98 spid12s Error: 17054, Severity: 16, State: 1. 2009-08-15 17:06:31.98 spid12s The current event was not reported to the Windows Events log. Operating system error = 1717(The interface is unknown.). You may need to clear the Windows Events log if it is full. 2009-08-15 17:06:32.78 spid5s SQL Trace was stopped due to server shutdown. Trace ID = ‘1'. This is an informational message only; no user action is required. 2009-08-15 17:06:32.95 Server The SQL Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. Error: 0x862, state: 3. Administrator should deregister this SPN manually to avoid client authentication errors. · Found only one user database ‘BEDB' on the serve
allUploadSign inJoinBooksAudiobooksComicsSheet Music Error:- 0xe00084f4 - An unknown error has occurred. Solution :- The following errors may occur when backing up to tape if the latest tape device drivers are notinstalled: (Figures 1 and 2) Figure 1 Figure 2 To install the latest tape device drivers go to:http://support.veritas.com/rd/bews-downloads.htm Source:- http://support.veritas.com/docs/283866 Error:- " Remote calls are not allowed for this process " Solution:- Figure 1 This error occurs when the remote computer does not have Distributed COM (DCOM) enabled.To resolve this problem, enable DCOM on the remote computer. To do this, follow the instructionsgiven below.For Windows Server 2003, Windows 2000, or Windows XP:1. Click Start | Control Panel 2. Double-click Administrative Tools , and then double-click Component Services to open theComponent Services Microsoft Management Console (MMC)3. Expand Component Services , and then expand Computers 4. Right-click on My Computer , and then click Properties 5. On the Default Properties tab, select the Enable Distributed COM on this computer checkbox, then click OK 6. Close the Component Services MMC7. Restart the computer For Windows NT:1. Click Start | Run 2. In the Run dialog box, type dcomcnfg, then click OK 3. In the Distributed COM Configuration Properties dialog box, on the Default Properties tab,select the Enable Distributed COM on this computer check box, and then click OK 4. Restart the computer Source:- http://support.veritas.com/docs/257194 Error: - The Advanced Open File Option cache file is not removed after a successful backup. AOFO: Initialization failure on: "C:". Advanced Open File Option used: Symantec VolumeSnapshot Provider (VSP).AOFO: Unable to get minimum quiet time for physical volumes. Reduce the activity on thesevolumes, or wait and run the backup when there is less activity on the volumes.AOFO: Initialization failure on: "D:". Advanced Open File Option used: Symantec VolumeSnapshot Provider (VSP).AOFO: Unable to get minimum quiet time for physical volumes. Reduce the activity on thesevolumes, or wait and run the backup when there is less activity on the volumes. Solution:- To troubleshoot the cause of the Open File Option (OFO) quiet time message, follow these steps:1. Create a backup job of only the drive that reported the OFO message and select Use OpenFile Option if available from the bac