Home > Backup Exec > Backup Exec 2014 A Communications Failure Has Occurred

Backup Exec 2014 A Communications Failure Has Occurred

Contents

I had to copy the RAWS32 directory from the remote server to the agent server and then execute the Go to Solution 6 3 2 +2 5 Participants tmelton82(6 comments) ssparks827(3 Full backup restores without any problem, there is problem when trying restore from Incremental backup Restore Job properties: I'm using VMware redirection to ESXi 5.0 server. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : E000FE30 - A communications failure has occurred i... have a peek at this web-site

Full D Drive    e. I haven't had any issues since. 0 Message Author Closing Comment by:tmelton82 ID: 314247042008-06-12 I had Symantec Tech Support basicaly had me to do the same thing. 0 LVL Once coppied logon to the remote server and run setupaa.cmd (locally) 0 Kudos Reply Jaydeep, Okay, I'll try that CWTokyo Level 4 ‎07-21-2013 05:35 PM Options Mark as New Bookmark Subscribe This Symantec Backup Exec Error E000fe30 A Communications Failure Has Occurred error code has a numeric error number and a technical description.

Backup Exec 2014 A Communications Failure Has Occurred

There is no other information besides that. 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. Unable to open the item \\servername\C:\Program Files\SAV\SAVRT\0129NAV~.TMP - skipped. 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

Check the Windows Event Viewer for details. Join & Write a Comment Already a member? Reply Subscribe RELATED TOPICS: Symantec backup exec, connectivity issue BE 2014 v-ray job failing after upgrade Can you run 2 schedule at the same time in Backup Exec? A Communications Failure Has Occurred Between The Backup Exec Job Engine And The Remote Agent Solved!

skip to main | skip to sidebar E000FE30 - A communications failure has occurred Thursday, March 4, 2010 E000FE30 - A communications failure has occurred If you use Backup Exec from 0xe000fe30 - A Communications Failure Has Occurred. The "Large TCP Offload" feature on the Network Card. Thank You! However it did provide me with more information this time.

Here are some troubleshooting/testing steps you can try: 1. Final Error: 0xe000fe30 - A Communications Failure Has Occurred. Hi,The worst that would happen is that you'd see worse performance and/or higher CPU usage on the server pretty much.It does sometimes cause a brief drop in traffic on the server, Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\master.mdf - skipped. We ended up having to abandon Backup Exec and go elsewhere.  0 Jalapeno OP Craig IT Feb 20, 2015 at 7:37 UTC well that turns my stomach... 0

0xe000fe30 - A Communications Failure Has Occurred.

No Yes How can we make this article more helpful? Sometimes bad things happen to people for no particular reason. Backup Exec 2014 A Communications Failure Has Occurred Disclaimer: This website is not affiliated with Wikipedia and should not be confused with the website of Wikipedia, which can be found at Wikipedia.org. E000fe30 Backup Exec 2012 Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?

This article contains information that shows you how to fix Symantec Backup Exec Error E000fe30 A Communications Failure Has Occurred both (manually) and (automatically) , In addition, this article will help Check This Out One question; let me verify the ports we have open as the NAS and BE server are on one subnet and the fax server I'm trying to back up are on Unable to open the item \\servername\C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\enterprisesec.config.cch.2172.13372828 - skipped. I have an agent running on one server running WS 2008 r2, and the BE server is running Windows 2012. E000fe30 Backup Exec 2015

If it repeats you will need to contact Symantec Support and see if you might need the updated bedsmbox.dll. Related Goodness Performing a Database Restore with Veeam Configuration Backup 12.7.15 by Ideen Jahanshahi Purging Duplicate Calendar Entries from Office 365 via PowerShell 11.30.16 by Eli Sprague Microsoft Exchange 2013: OWA Repeat with AOFO Enabled and select the bottom option "Microsoft Volume Shadow Copy Service (Windows 2003 and later)" and set the Snapshot provider to "Automatic - Allow VSS to select the Source Check the link below: http://www.symantec.com/business/support/index?page=content&id=TECH137682 You can try restoring the VM to a local disk, and then copying to the virtual centre is this is possible.

I had to copy the RAWS32 directory from the remote server to the agent server and then execute the setupaa.cmd and setupaofo.cmd files which perform a silent install. E000fe30 Backup Exec 15 I then ran live update from the main console to apply 3 or 4 patches. Unable to open the item \\servername\C:\Documents and Settings\Administrator\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat - skipped.

My mistake. 0 Kudos Reply ...if there is an AV on that CraigV Moderator Partner Trusted Advisor Accredited ‎07-16-2013 11:54 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed

AOFO: Initialization failure on: "servername\SQLSERV". While I've seen plenty of issues with this feature before, you normally see it with terrible throughput on the system in general and so on - but this machine is solid But did you ever see this?http://seer.entsupport.symantec.com/docs/290098.htmIt was posted before your blog about TCP Offload. 16 April 2010 at 08:09 PeteLong said... V-79-57344-65072 - The Connection To Target System Has Been Lost. Backup Set Canceled. It says No for AOFO used but I have the box checked to choose the AOFO type automatically.

Finally on launch Backup Exec and click Tools > Live Update > follow the instructions, Note: you may be asked for a reboot when its finished. Advanced Open File Option used: Symantec Volume Snapshot Provider (VSP). The error is the same one that tmelton is getting on his D: drive. http://netlookmag.com/backup-exec/backup-exec-rpc-service.html Most of the solutions I found relate to Exchange but in my case I am not backing up Exchange.