waspsoft.com


Home > Backup Exec > Backup Exec Services Error 1068

Backup Exec Services Error 1068

Contents

Creating your account only takes a few minutes. One likely culprit is the device driver for your tape drive. There is no ndmp entry in services and netstat -ab shows nothing using port 10000. 0 This discussion has been inactive for over a year. 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 http://waspsoft.com/backup-exec/backup-exec-services-not-starting-error-1068.html

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. we just don't want to lose the backups if at all possible. I'm beginning to think going into IT was a mistake Water Cooler I earned my CompTIA A+ certification in 2013, and began going to school for Computer Science in 2014. The other thing to check is to ensure that any AV running on that server isn't perhaps blocking the BE services,a nd if so, put in exclusions for them.

Backup Exec Error 1068 The Dependency Service

What do you think of the new Backup Exec 2012?   24 Replies Mace OP Denis Kelley Jan 22, 2013 at 9:31 UTC Have 2010 R3 and "played" do you have BE installed on more than 1 server? 0 Jalapeno OP Donald (Symantec) Jan 22, 2013 at 10:20 UTC Matthew, has the password for the system Attempting to restart the Remote Agent service on results in "The system cannot find the file specified." The option to install Remote Agent (from disk) is greyed out and my only

After fixing this hardware issue, backups would no longer run (all ip addresses of remote machines changed) and I am no longer able to browse remote resources. I got error message 1069: The service didn't start due to logon failure. The other services will not start if the database engine won't start. Backup Exec 11d Error 1068 If the service is not running, you may be able to manually start the service by right clicking on it and selecting the Start command from the shortcut menu.

Check if anything is using that port. Error 1068 The Dependency Service Or Group Failed To Start Backup Exec 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 Services Overview After that completed, I ran Windows Update, then proceeded to restart the server. Struggling Violin Memory launches two new Flash Storage Platform arrays with improved performance, lower latency and encryption ...

Posted on 2008-12-12 Storage Software MS Server OS Windows Server 2003 1 Verified Solution 12 Comments 8,456 Views Last Modified: 2013-12-01 I'm unable to log into Backup exec. Backup Exec Error 1053 Thank You! This includes any available firmware updates. Again, restart the services after making any changes.

Error 1068 The Dependency Service Or Group Failed To Start Backup Exec

papadage Ars Legatus Legionis et Subscriptor Tribus: Celerius quam asparagi cocuntur. There are several services that are not started. Backup Exec Error 1068 The Dependency Service Considering the size of my network, this was a costly move. Windows Could Not Start The Backup Exec Server Service Error 1068 Have you rebooted this server lately?

I made the account a member of Domain Admins and all Service started. navigate here We deinstalled the old Backup Exec 8.5 version and installed Backup Exec 2010. Have you restarted the server? 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 Backup Exec 12 Error 1068

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Join the community Back I agree Powerful tools you need, all for free. Here's one article that talks about reinstalling MSDE to a different location. - you could try this and see if it helps: http://seer.entsupport.symantec.com/docs/281530.htm 0 Write Comment First Name Please enter a Check This Out Otherwise, if you have domain admin rights on your account, use BEutility.exe to change the BESA to use your account as a test and see if it starts up.

RE: Error 1068: the dependency service or group failed to start Ken_Putnam Level 6 Trusted Advisor ‎10-26-2009 09:37 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Backup Exec Services Will Not Start Join Now It may be that I'm being impatient, but calling the Symantec tech support line didn't get me quite as far as I had hoped (all they were able to If you are not using Veritas drivers for your tape drive, try loading those and see if that helps. 0 Message Author Comment by:wimiller2008-12-15 MSSQL$BKUPEXEC is first in the dependency

Thanks! 0 Kudos Reply Thanks CraigV.

  • By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks.
  • The other thing to check is to ensure that any AV running on that server isn't perhaps blocking the BE services,a nd if so, put in exclusions for them.
  • I didn't find any event in the event viewer for this application.
  • Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : Unable to start Backup Exec Services after stoping...
  • Next Steps Will Symantec Backup Exec restore the brand's reputation?
  • Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved!
  • Backup Exec Error E000FED1: A failure occurred querying the writer status This error message is related to the VSS writer for a particular application.

While the Backup Exec services are stopped for each Backup Exec service, type in the password and confirm the password. 3. My new house... Not all occurrences of Symantec Backup Exec error 1053 are related to the .NET framework. Backup Exec Services Stopped Right click on the TypeLib container and choose the Permissions command from the resulting shortcut menu.

I've had to do the re-install thing quite a bit. Shall I open Backup Exec Application now? I am running BE 13.0.5204  0 Pimiento OP aw3 Jun 2, 2015 at 6:13 UTC Running SGMON to Capture Job Engine, RAWS, Agent Browser: BESERVER: [06/02/15 14:03:39] this contact form Now I wish to start Backup Exec Services again.

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. It's not needed and can cause conflicts with Backup exec's media server. Everything worked just fine. Navigate the Backup Exec directory (the default directory is C: Program files/Veritas/Backup Exec/NT/ Data) to the Data sub directory. 5.

Help Desk » Inventory » Monitor » Community » Home Backup Exec 2012 can't logon to services after update by MatthewIT on Jan 22, 2013 at 9:08 UTC | Symantec 0Spice Download this free guide Archive vs. 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 Used to also have times where it would stop communicating with the library and had to reboot the server to get it back, this wasn't good on a production server so

After backing up the system, open the Registry Editor and navigate through the registry tree to HKEY_CLASSES_ROOT\TypeLib. I don't recall off hand myself, but I think it's probably either the device engine or the media engine. However, other applications often depend on the .NET Framework and removing the framework can cause those applications to break. You may get a better answer to your question by starting a new discussion.

When we bought that house, it had an unfinished basement and an unfinished attic room, making the cabling process very simple. Yeah, remote agents all of a sudden refusing to start after a bootup. Don't use the backup user anywhere else because it may lead to a locked account next time you change that pw. Please login.