Home > Backup Exec > Backup Exec 12 Error Communication Stalled

Backup Exec 12 Error Communication Stalled

Contents

This worked a treat! 0 Write Comment First Name Please enter a first name Last Name Please enter a last name Email We will never share this with anyone. The upgrades center on data recovery, workflow ... However, other applications often depend on the .NET Framework and removing the framework can cause those applications to break. You will then need to re-create all your jobs and if you need to restore you must catalog your tapes. Source

You will then need to re-create all your jobs and if you need to restore you must catalog your tapes. Dev_T Level 6 ‎03-21-2010 10:25 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content any news here? 0 Kudos Reply Privacy Policy Site Map Support Terms of Use MenuExperts Exchange Browse BackBrowse Topics Open Questions Open Projects Solutions Members Articles Videos Contribute Products BackProducts Gigs Live Careers Vendor Services Groups Website Go to Tools > Backup Exec Services...

Communication Stalled Backup Exec 2010

Sometimes Error 1053 is related to a permissions problem that keeps the database or one of the Backup Exec Services from starting. Nexus Ars Tribunus Angusticlavius Registered: Jan 26, 2000Posts: 8867 Posted: Wed Jun 17, 2009 8:15 am Yes its still recommended unfortunately. If not, you may have to manually associate the DLL file with Backup Exec. Text Quote Post |Replace Attachment Add link Text to display: Where should this link go?

None of the permissions or memberships on that account changed. Subscribe to our monthly newsletter for tech news and trends Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource Center About Us Who We You may get a better answer to your question by starting a new discussion. Backup Exec 2012 Stuck On Verify Not all occurrences of Symantec Backup Exec error 1053 are related to the .NET framework.

Once this is done select repair database The last step: Repair database indices. Communication Stalled Backup Exec 2010 R3 If you care to try you can attempt recovery of your job history, selection lists, etc by: (still in beutility - must have already completed above steps) Right click on your The exact method to remove and reinstall the .NET Framework will vary depending on the operating system used. This can also cause C++ runtime errors with backup exec remote agent as when the database is corrupt it will cause errors all over. 0 Write Comment First Name Please

If not, you need to dump database and load from Base. Backup Exec Stuck On Queued Registered: Jun 14, 2002Posts: 18034 Posted: Fri Jul 03, 2009 5:40 am quote:Originally posted by indeego:heh, they just released a hotfix for 12.5 SP2 that requires a reboot after install on Connect with top rated Experts 9 Experts available now in Live! This causes Windows to launch the Service Control Manager, which can be used to view the properties for the various services.

Communication Stalled Backup Exec 2010 R3

I have no idea on why this is a problem from time to time, but it is. Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : Inventory jobs stop with status of "Communication ... Communication Stalled Backup Exec 2010 I'm not sure how complex your backup job is, but if it's easy, try deleting the backup job and re-creating it. Backup Exec Inventory Stalled I can't cancel the job and they usually continue in this state for about 15 minutes.

Plus two Linux boxes that need backed up. http://sovidi.com/backup-exec/backup-exec-crc-error.php This could open ... Ge0ph Ars Tribunus Angusticlavius Tribus: Jackpot Nevada Registered: Jan 28, 2000Posts: 8369 Posted: Fri Jun 12, 2009 3:05 pm quote:Something changed, but no clue what as of this point. I couldn't find a known good spare so I shut down this box so I could borrow its cable to troubleshoot with. Backup Exec Status Stalled

All jobs were created at the same time (long time ago) but the same user. Specifically, one of the VSS writers used to back up an application running on the server reported a status of failed, which caused Backup Exec to produce error E000FED1. Sometimes while running an Utility Job Operations on a device like (Inventory, Erase etc.), the job switches to "Communication Stalled" state and then ends in a "Recovered Status". http://sovidi.com/backup-exec/backup-exec-error-cannot-extract-mailbox-messages-exchange-backup.php Symantec Backup Exec has been around in one form or another since the early 1990s and has a reputation as one of the more reliable backup products on the market.

That would give us a little more info to go off of. No problem! Just search Symantec's site for updated drivers.

It isn't the tapes themselves as evidenced by it happens with a brand new tape.Going on the assumption that it is hardware, what else is there?

When we bought that house, it had an unfinished basement and an unfinished attic room, making the cabling process very simple. open the BE GUI open the Devices tab right click on the server and select Paused wait for a few seconds and right click on the server once again now unselect Chances are that having the latest SP for BEWS will allow you to install these patches, or at least addresses issues that these patches create...something to read up on. Email Address (Optional) Your feedback has been submitted successfully!

Windows will display a list of each VSS writer and note if it is in an error state. Download this template to ... includes all backup jobs too! 0 Message Expert Comment by:Madrooki2009-11-10 Thank you! http://sovidi.com/backup-exec/backup-exec-error-backup-snapshot-already-exists.php Help Desk » Inventory » Monitor » Community » MenuExperts Exchange Browse BackBrowse Topics Open Questions Open Projects Solutions Members Articles Videos Contribute Products BackProducts Gigs Live Careers Vendor Services Groups

Featured Post How your wiki can always stay up-to-date Promoted by Quip, Inc Quip doubles as a “living” wiki and a project management tool that evolves with your organization. I've never seen it work 100% correctly. This will give you a clean database. If replacing the tape doesn't work, the problem is most likely related to device drivers or the tape drive itself.