Error Starting Backup-exec Device And Media Service
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community
Error Starting The Service Backup Exec Server
MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About backup exec device and media service will not start Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English backup exec device & media service stopping 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Backup Exec Device and Media Service fails to start
Error Connecting To Master Database: Hr = 0x80004005
because the database recovery has failed Article:000019999 Publish: Article URL:http://www.veritas.com/docs/000019999 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.
Event Id 58068
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 the Backup Exec Device & Media Service on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 536928979. Error Message Windows Event Log Shows: Event Type: Error Event Source: Backup Exec Event Category: None Event ID: 58068 Description: The Backup Exec Device and Media Service could not start because the database recovery has failed. Refer to the database recovery log for details. Also SQL Management studio fails to connect to BKUPEXEC instance with error "Login Timeout Expired". DBRecover Log shows : OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;
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 udl test backup exec Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research
Backup Exec Database Recovery Has Failed
Exchange 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 will not start and "Event id 58068, the database recovery has failed. https://www.veritas.com/support/en_US/article.000019999 Refer to the database recovery log for details" occurs. Article:000040813 Publish: Article URL:http://www.veritas.com/docs/000040813 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 https://www.veritas.com/support/en_US/article.000040813 In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem The Backup Exec Device and Media Service will not start and "Event id 58068, the database recovery has failed. Refer to the database recovery log for details" occurs. Error Message The Event viewer shows: at BackupExec.UI.MainForm.a(String[]A_0)at BackupExec.UI.MainForm.b(String[]A_0) Cause The Backup Exec Device and Media Service could not start because the database recovery has failed. Refer to the database recovery log for details. Solution 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. 1. Navigate to the HKEY_Local_Machine/Software/Symantec/Backup Exec For Windows/Backup Exec/Server
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 Process ABOUT About Corporate Profile https://www.veritas.com/support/en_US/article.000028614 Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Backup Exec Device https://www.experts-exchange.com/questions/24453766/Problem-starting-Backup-Exec-Device-Media-Service.html and Media service fails to start with the message "Database specified does not exist" Article:000028614 Publish: Article URL:http://www.veritas.com/docs/000028614 Support / Article Sign In Remember me Forgot Password? Don't have backup exec 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 Backup Exec Device and Media service fails to start with the message "Database specified device and media does not exist" Error Message The Database Specified does not exist or cannot be found Cause 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. Before detaching the database verify if the correct server and instance name is reflected in the Adamm key. Solution 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.HKLM\Software\Symantec\Backup Exec for Windows\ADAMM\Check the Database Server Name key to verify server name. ( The key will not be present if its using l
for 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 > Problem starting Backup Exec Device & Media Service Want to Advertise Here? Solved Problem starting Backup Exec Device & Media Service Posted on 2009-06-01 Storage Software 1 Verified Solution 20 Comments 2,587 Views Last Modified: 2013-12-01 I was having issues starting the Backup Exec services last week. After a couple of repairs and reboots the service was running and allowed me to schedule a backup. The backup started and when I left for the weekend it was ~50% complete and everything seemed to be fine. When I returned this morning there was a message that the backup failed because the service could not be contacted. I checked and it was now stopped. I exited out of Backup Exec and opened it back up. When I attempt to restart the services it hangs on "Starting Backup Exec Device & Media Service." I let it sit for about 20 minutes and the service will not start. I was having this same issue before the multiple repairs and restarts. I am running Windows SBS 2003 on the machine along with Backup Exec 11d and I've had nothing but problems with the combination for awhile. I am doing everything from the PHYSICAL machine logged in to the Administration account. The Backup Exec services are set to run as Administrator. Does anyone have any idea what could be causing this? I posted a similar question last week and didn't receive any response - I closed it out when I thought I had solved the problem. I've been told it could be a potential issue with my MDAC version? If so, how would I test this theory and, if it proves to be the case, solve the issue? All of the latest Windows updates are installed and this is a live server that I prefer not to take down unless absolutely necessary so constantly rebooting the machine isn't ideal. I've read similar questions on here and they seem to receive very few responses and eventually seem to lead to reinstalling the OS as the only solution - I'm