Home > Backup Exec > Event Id 58068

Event Id 58068

Contents

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 Refer to the database recovery log for details. No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES 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. navigate here

Have you tried to repair the BEDB through BEutility.exe? Type CLICONFG 3. Email Address (Optional) Your feedback has been submitted successfully! CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical https://www.veritas.com/support/en_US/article.000089808

Event Id 58068

CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical No Yes How can we make this article more helpful? When attempting to start the Backup Exec Device and Media Server service, Event ID 58068 is generated citing Backup Exec as the source. Click Start->Run 2.

By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.   1. This specific provider is the method Backup Exec services use to connect to the Backup Exec database, without it, Backup Exec will not function. Sorry, we couldn't post your feedback right now, please try again later.

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Veritas does not guarantee the accuracy regarding the completeness of the translation. Thank You! Thank You!

Error Message The Backup Exec Device and Media Service reports the following error: "The Backup Exec Device and Media Service could not start because the database recovery has failed. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem When trying to start the Backup Exec services, the Device and Media service, the service fails to Sorry, we couldn't post your feedback right now, please try again later. Refer to the database recovery log for details.

The Backup Exec Device And Media Service Could Not Start Because The Database Recovery Has Failed

AccountName is a placeholder for the account that you specify to start the SQL Server service. https://www.veritas.com/support/en_US/article.000007179 Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Backup Exec Device and Media Service fails to start with error: Windows could not start Event Id 58068 Thank You! No Yes Did this article save you the trouble of contacting technical support?

Are you an IT Pro? Create/Manage Case QUESTIONS? You may also refer to the English Version of this knowledge base article for up-to-date information. Refer to the database recovery log for details" occurs.

No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES Sometimes the value of "PreviousDjmPrimaryServer" and the value of "Database Server Name" is the same as seen in the Event ID description above. Creating your account only takes a few minutes. My question is, should I just uninstall Backup Exec and Reinstall it all over, because just reinstalling the database isn't working.

Sorry, we couldn't post your feedback right now, please try again later. Thank You! You may also refer to the English Version of this knowledge base article for up-to-date information.

No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES

It is possible that updates have been made to the original version after this document was translated and published. You may also refer to the English Version of this knowledge base article for up-to-date information. Sorry, we couldn't post your feedback right now, please try again later. Sorry, we couldn't post your feedback right now, please try again later.

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: Refer to the database recovery log for details." Details: This issue has several causes, if the steps below do not resolve the issue or the symptoms do not match, please refer Restart the SQL Server (BKUPEXEC) Service. 5. Email Address (Optional) Your feedback has been submitted successfully!

Navigate to the HKEY_Local_Machine/Software/Symantec/Backup Exec For Windows/Backup Exec/Server key in the registry editor.The string value of LastknownSQLDB must be point to the BEDB_Dat.mdf location.       2. Also SQL Management studio fails to connect to BKUPEXEC instance with error "Login Timeout Expired". It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.  2. Please contact Microsoft Support for further assistance. 0 Kudos Reply Hi I would ask first what Backup_Exec1 Level 6 Employee Accredited Certified ‎08-08-2012 05:33 AM Options Mark as New Bookmark Subscribe

Login By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. © Copyright 2006-2017 Spiceworks Inc. Add your comments on this Windows Event! Create/Manage Case QUESTIONS? CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical

Directory lookup for the file "E:\logs\BEDB_log.ldf" failed with the operating system error 2(The system cannot find the file specified.). Refer to the database recovery log for details." The Backup Exec Database Recovery log* reports the following error: "Error connecting to master database: hr = 0x80040e4dOS ERROR: 0x80040e4d (-2147217843)Status of database Thank You!