Home > Backup Exec > Backup Exec Error 1068 The Dependency Service Failed To Start

Backup Exec Error 1068 The Dependency Service Failed To Start


Once you've identified that, then you can troubleshoot the causes of that service not starting. E-Mail: Submit Your password has been sent to: -ADS BY GOOGLE Latest TechTarget resources Solid State Storage Virtual Storage Cloud Storage Disaster Recovery Storage IT Channel SearchSolidStateStorage 3D XPoint memory stumbles The weird thig is that it'll be ok for months and then on a rebbot, the services won't restart properly.Yup, that's Veritas. Solved error message: Could not start the Backup Exec Job Engine service on Local Computer. have a peek here

I looked on the Veritas site and all I found was something about incorrect permissions, but I check them and they were ok as per Veritas site.thanks much! Did some research.... Are there any other related errors in the event log besides the 1068? 0 Message Author Comment by:wimiller2008-12-15 I dont see anything else. My Tape Drive Drivers are old and I wish to upgrade them, because we are unable to compress data properly.

Error 1068 Backup Exec Job Engine

Again, restart the services after making any changes. It's not needed and can cause conflicts with Backup exec's media server. Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : Unable to start Backup Exec Services after stoping... You should therefore make a full system backup before attempting a registry modification.

  • Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs.
  • Backup Exec 2010 Help Backup Exec 2010   11 Replies Thai Pepper OP Jeff9151 Jun 13, 2012 at 4:23 UTC Hi Hennepin, The dependencies should be listed on
  • I did this same thing, change the service logon accounts, on a server running BE 8.6 and had no problems.
  • job engine 5.
  • If replacing the tape doesn't work, the problem is most likely related to device drivers or the tape drive itself.

By submitting you agree to receive email from TechTarget and its partners. It's a last ditch effort - but it's worked for me. Backup Exec Error 1053: The service did not respond to the Start or Control Request in a timely fashion This is one of the Backup Exec errors that can be caused Backup Exec 0x80004005 Submit your e-mail address below.

Download this free guide Drill down into today's new backup approaches Due to the features of most modern backup software – which include snapshot management, DR elements, cloud support, VM protection By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. Some services stop automatically if they have no work to do, for example, the performance logs and alerts service... 0 LVL 38 Overall: Level 38 Windows Server 2003 19 MS Sometimes Error 1053 is related to a permissions problem that keeps the database or one of the Backup Exec Services from starting.

And also the remote backup agents on all systems you are backing up. Error 1068 The Dependency Service Or Group Failed To Start Backup Exec Server agent browser. Find Out How Today Suggested Solutions Title # Comments Views Activity cryptolocker in a desktop 3 54 40d Windows 10 Pro -- nonCLOUD backup software ? 4 33 28d Tape vs Device and media 3.

Symantec Backup Exec Error 1068

Any entries in the System or Application event log? 0 Pimiento OP aw3 Jun 2, 2015 at 5:40 UTC If by "Install backupexec again (yes on top of If you're not familiar with service dependencies, you can see the dependencies by opening the Services console, then going to the properties of the service that won't start. Error 1068 Backup Exec Job Engine If you can then setup your domain account network->logon accounts. 0 LVL 38 Overall: Level 38 Windows Server 2003 19 MS Server OS 12 Storage Software 7 Message Active 2 Backup Exec Remote Agent Error 1053 Load More View All Veritas Technologies CEO: Vendor 'got lost' as part of Symantec Veritas Vision: Beyond backup to cloud, data management Veeam availability expands in hybrid cloud platform Acronis Backup

You may get a better answer to your question by starting a new discussion. navigate here Check event viewer for any error related to services. The upgrades center on data recovery, workflow ... Navigate the Backup Exec directory (the default directory is C: Program files/Veritas/Backup Exec/NT/ Data) to the Data sub directory. 5. Backup Exec Error Code E000846b

Is there really no way to solve this? It is possible that updates have been made to the original version after this document was translated and published. My previous home was wired with Cat5E in almost every room. Check This Out The VSSADMIN command can be used to determine which VSS writer is causing your problem.

It is probably SQL Go to Solution 12 Comments LVL 38 Overall: Level 38 Windows Server 2003 19 MS Server OS 12 Storage Software 7 Message Active 2 days ago Error 1068 The Dependency Service Failed To Start Print Spooler Hi In your case I saw the Backup_Exec1 Level 6 Employee Accredited Certified ‎04-04-2012 11:06 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to Download this template to ...

To resolve this issue do the following: 1.

Next Steps Will Symantec Backup Exec restore the brand's reputation? Join Now I changed the password on the user that runs Backup Exec and now some of the services refuse to start.  They grumble that some dependencies won't start, but of Error 1053 often points to a failure of the Backup Exec Management Services or a situation in which Backup Exec Services do not start. Error 1068 The Dependency Service Failed To Start Windows 7 Any help on this issue would be greatly appreciated.

My eyes, my eyes! This email address is already registered. However, cleaning the tape drive rarely corrects the problem. this contact form Registered: Mar 15, 2002Posts: 22584 Posted: Tue Dec 31, 2002 5:01 pm Okay, good man.

The log entries should give you a hint as to thecause of the problem. 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 We deinstalled the old Backup Exec 8.5 version and installed Backup Exec 2010.