Home > Backup Exec > Backup Exec Error Code E000fe30

Backup Exec Error Code E000fe30

Contents

Labels: 2010 Backing Up Backup and Recovery Backup Exec Error messages Troubleshooting 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! I will do a shadow copy of the data to a different place see what it does. About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : E000FE30 - A communications failure has occurred i... Source

I'm having a problem with a Windows 2003 Server that is running MSSQL 2005 and is also a guest VM on esx 3.0.1. Any activity while the backup runs on the server .. Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile C C++ C# CSS ERB HTML Java JavaScript Lua ObjectiveC PHP Perl Text Powershell Python R Ruby Sass Scala SQL Sorry, we couldn't post your feedback right now, please try again later.

E000fe30 A Communications Failure Has Occurred

I am just backing up a domain controller. Thanks! 0 Kudos Reply Check everything that Craig Jaydeep_S Level 6 Employee Accredited Certified ‎07-17-2013 12:56 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to Advanced Open File Option used: Symantec Volume Snapshot Provider (VSP).

If you still get failures, post the exact error message here. 0 Kudos Reply I'll have to check tomorrow CWTokyo Level 4 ‎07-17-2013 02:32 AM Options Mark as New Bookmark Subscribe Unable to open the item \\servername\C:\Program Files\SAV\SAVRT\0129NAV~.TMP - skipped. However, if it is randomising the failures, I'd recommend updating the media server with any available patches and then push-installing these out to the remote servers you might have. Backup Exec Error 80004005 Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?

Home Symantec Backup Exec 2014 Error e000fe30 - A communications failure has occurred by Craig IT on Feb 20, 2015 at 6:30 UTC | Data Backup 0Spice Down Next: Backing up Backup Exec Error Code E000846b Advanced Open File Option used: No. Thanks View solution in original post 0 Kudos Reply 6 Replies Hi M1ke, Do you need to CraigV Moderator Partner Trusted Advisor Accredited ‎09-15-2011 06:21 AM Options Mark as New Shouldn't that have included this hot fix? 0 Kudos Reply Would recommend you to VJware Level 6 Employee Accredited Certified ‎01-31-2012 10:30 AM Options Mark as New Bookmark Subscribe Subscribe to

The 2008 server has been in place for a few months now, the first couple months the server had some files but not alot (approx 100 GB of files and data), Backup Exec 80004005 verify what happens during the weekly job on the server by examining the event vwr...!! Join the community of 500,000 technology professionals and ask your questions. The first file that it make it crash is a .pdf file.

Backup Exec Error Code E000846b

Access the Backup and Restore options: Click on the windows 7 start ball in the lower left corner of the scree… Windows 7 PCs Storage Software Advertise Here 845 members asked I excluded this file and after a while another pdf then make the backup crashed. E000fe30 A Communications Failure Has Occurred Ok so didn't found a solution M1ke Level 3 ‎10-04-2011 07:05 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Symantec Backup Exec E000fe30 I can't believe that the ports are open, they talk to each other and yet it fails EVERY time. 0 Kudos Reply On the Media Server, browse Jaydeep_S Level 6 Employee

All we can do is to find a way to make some unavoidable situations… avoidable. http://gatoisland.com/backup-exec/backup-exec-12-5-error-e000fe30.php Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\templog.ldf - skipped. Terms Of Service | Privacy Policy | Copyright Policy | Affiliates

Snapshot provider error (0xE0008520): Device could not be snapped because it contains an active cache file. E000fe30 Backup Exec 2010

I then ran live update from the main console to apply 3 or 4 patches. With R3 everything works fine. VOX : Backup and Recovery : Backup Exec : E000FE30 - A communications failure has occurred i... http://gatoisland.com/backup-exec/backup-exec-2010-error-code-e000fe30.php An upgrade was desperately needed.

If they are, open up your job and choose Automatic as your snapshot provider instead of a specific one. Symantec Backup Exec E0008703 You may also refer to the English Version of this knowledge base article for up-to-date information. Snap!

Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Error E000FE30 : A communication failure has occurred when attempting to backup

My new house... Errors: Final error: 0xe000fe30 - A communication failure has occurred Final error category: Server Errors V-79-57344-65072 - The Exchange Store service is not responding. No Yes Did this article save you the trouble of contacting technical support? Backup Exec Error Code E0008821 Email Address (Optional) Your feedback has been submitted successfully!

could be a corrupted job or selection as well Does the monthly and weekly backups which are working fine uses same selection list or different? 0 Kudos Reply The issues Hi, I suspect your issue CraigV Moderator Partner Trusted Advisor Accredited ‎05-23-2012 07:37 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Make sure that no other application has a lock on the cache files created by the snapshot operation. 0 LVL 3 Overall: Level 3 Message Expert Comment by:ssparks8272008-01-28 Do http://gatoisland.com/backup-exec/backup-exec-e000fe30-error.php Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\msdbdata.mdf - skipped.

This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. V-79-57344-34110 - AOFO: Initialization failure on: "\\servername\System?State". Symantec Backup exec 2014 I am running a one time backup on Symantec Backup Exec 2014...   11 Replies Pimiento OP Matagorda County Feb 20, 2015 at 7:35 esxcfg-firewall -Q If the ports are not specified proceed to the resolution section   NOTE: Symantec recommends having NDMP port 10000 and a specific dynamic port range available on the Backup

Is there a way to say to backup exec not to stop the job if it detect a corrupted file to just skip and continue? I'm trying to restore VM form Tape, backed up with Backup Exec 2010 13.0. Labels: Agents Backing Up Backup and Recovery Backup Exec Configuring Error messages Managing Backup Devices Troubleshooting Windows Server (2003-2008) 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution! Even with BE 2012 SP2 which is due to be released soon, BE 2012 can only back up Windows 2012. 0 Kudos Reply I'm sorry - I just checked - CWTokyo

Error : e000fe30 - A communications failure has occurred. Unable to open the item \\servername\C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\enterprisesec.config.cch.2172.13372828 - skipped. It is possible that updates have been made to the original version after this document was translated and published. I have Backup Exec 2010 R3 on a Windows Storage Server 2007 64 bits Service Pack 2 The server i'm trying to backup Data is a Windows Server 2003 R2 Standard

© Copyright 2017 gatoisland.com. All rights reserved.