Home > Backup Exec > Symantec Backup Exec 2012 Error E000fe30

Symantec Backup Exec 2012 Error E000fe30


Terms Of Service | Privacy Policy | Copyright Policy | Affiliates 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 Once you have verified that the services are stable again you can try and retest. Posted on 2008-01-24 Storage Software 13 1 solution 26,065 Views Last Modified: 2013-12-01 For the last week my backups have been failing with error: e000fe30 - A communications failure has occurred. this content

In other words, Symantec has had some success with splitting the backups into two jobs, one for files and one for the Exchange Server. Check the Windows Event Viewer for details. Creating your account only takes a few minutes. Snapshot provider error (0xE0008520): Device could not be snapped because it contains an active cache file.

E000fe30 Backup Exec 2010

Join Now For immediate help use Live now! Try Free For 30 Days Join & Write a Comment Already a member? Finally on launch Backup Exec and click Tools > Live Update > follow the instructions, Note: you may be asked for a reboot when its finished.

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. 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 You are here: Error E000FE30 in Backup Exec - V-79-57344-65072 How to Fix Jobs Crashing with Error 0xe000fe30 in Backup Exec sponsors: © Copyright 2016 Net-Noggin, LLC. | phone: 574.876.3872 E000fe30 Backup Exec 2012 Everything seems to work well at the begining, but after few minutes Byte Count stops, and Job rate successively goes down, Tape Autoloader starts with daily (with incrementals) tape loading after

I'm not sure, but I'm happy to blame it since everything else works just fine. Backup Exec 2014 A Communications Failure Has Occurred Hope you’ll enjoy it and will choose the one as required by you. Exceptions Backup- \\servername\D: Data V-79-57344-34108 - An unexpected error occurred when cleaning up Symantec Volume Snapshot Provider (VSP) snapshots. Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\modellog.ldf - skipped.

The closest option had the same basic error message of V-79-57344-65072 - The connection to target system has been lost. V-79-57344-65072 - The Connection To Target System Has Been Lost. Backup Set Canceled. The "Large TCP Offload" feature on the Network Card. Test the individual components    a. But, it had a different problem description.

Backup Exec 2014 A Communications Failure Has Occurred

Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\mastlog.ldf - skipped. Symantec got me to re-install the agent locally. E000fe30 Backup Exec 2010 Here are some troubleshooting/testing steps you can try: 1. E000fe30 Backup Exec 2015 V-79-57344-3844 - The media server was unable to connect to the Remote Agent on machine {server name} Remote Agent not detected on {server name} Note: You may also see error E0000F04

Examine the services. news Im not using Backup Exec Granular Recovery Technology (GRT) Device Name Created On Job Type Job Status Percent Complete Start Time End Time Elapsed Time Byte Count Job If so try disabling it then run a test backup. 0 What Is Threat Intelligence? Join the community of 500,000 technology professionals and ask your questions. 0xe000fe30 - A Communications Failure Has Occurred.

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! Related Goodness Performing a Database Restore with Veeam Configuration Backup 12.7.15 by Ideen Jahanshahi Step by Step: Upgrading to Veeam 9 1.13.16 by Ideen Jahanshahi What Is Digital Forensics? 2.5.16 by V-79-57344-34110 - AOFO: Initialization failure on: "\\servername\D:". have a peek at these guys 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.

On a x64 bit server run double click the following two files, setupaax64.cmd and setupaofox64.cmd (noting will happen other than a command window will flash up). 4. Final Error 0xe000fe30 A Communications Failure Has Occurred This is how video conferencing should work! There is no other information besides that.

Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\tempdb.mdf - skipped.

If you are backing up Exchange Server as part of a file backup job, one possible work-around is to separate those two resources. Check the network, and then run the job again. 0 Message Expert Comment by:StratfrordDC ID: 211385732008-03-16 I am having the same problem with version 12.0 on a 2003 Server. I've ensured that the agent has local admin access to both the BE server and the local server where it's running, and the NAS allows the same user read/write access (it's A Communications Failure Has Occurred Backup Exec Directly connect an external storage device such as a USB drive, or CD\DVD burner: If the device is a USB drive, ensure i… Storage Software Windows Server 2008 Disaster Recovery Setting

Unable to open the item \\servername\C:\Program Files\SAV\SAVRT\0129NAV~.TMP - skipped. Nothing I've found fixed the problem of the pesky "E000FE30 - A communications failure has occurred" error. The logs did give me this: For additional information regarding this error refer to link V-79-57344-65072... check my blog Unable to open the item \\servername\C:\Documents and Settings\LocalService\NTUSER.DAT - skipped.

Go to Solution. Unable to open the item \\servername\C:\WINDOWS\system32\wins\winstmp.mdb - skipped. Simple template. You may get a better answer to your question by starting a new discussion.

Error : e000fe30 - A communications failure has occurred.