Home > Backup Exec > Backup Exec 2010 Error Code E000fe30

Backup Exec 2010 Error Code E000fe30

Contents

Additional we planned to use Symantec NetBackup7 to backup to tape media for disaster recovery. The one you pick depends on weather your running 32 bit or 64 bit software. voila!Top tip for anyone else facing this problem - don't just check the network drivers, but try turning off these features, even if you cannot see this issue at any other In other words, Symantec has had some success with splitting the backups into two jobs, one for files and one for the Exchange Server. http://onlinetvsoftware.net/backup-exec/backup-exec-2010-error-e000fe30.php

Nothing I've found fixed the problem of the pesky "E000FE30 - A communications failure has occurred" error. Email Address (Optional) Your feedback has been submitted successfully! No matter what I did, the job crashed with the following error: E000FE30 - A communications failure has occurred(But I have the answer for you!) Digging into the Backup Exec logs starting at 50000 to 50050) ; TCP (out) review the appropriate Vmware administrative/User guides or contact Vmware technical support for assistance.

E000fe30 Backup Exec 2015

Microsoft to end Windows 7 PC sales, Firefox tackles weak encryption Spiceworks Originals A daily dose of today's top tech news, in brief. © Copyright 2006-2016 Spiceworks Inc. Want to Advertise Here? It is possible that updates have been made to the original version after this document was translated and published. I don't have the "Large TCP Offload" option, but I have a short list of other Offload options on both my built-in NIC and my SAN connection.

Covered by US Patent. Unable to open the item \\servername\C:\Documents and Settings\NetworkService\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat - skipped. VOX : Backup and Recovery : Backup Exec : E000FE30 - A communications failure has occurred i... 0xe000fe30 - A Communications Failure Has Occurred. Just the shadow copy components, or data too?

System State and Shadow Copy Components    g. When we bought that house, it had an unfinished basement and an unfinished attic room, making the cabling process very simple. Here is the error for just the SQL instance. Exceptions Backup- \\servername\D: Data V-79-57344-34108 - An unexpected error occurred when cleaning up Symantec Volume Snapshot Provider (VSP) snapshots.

Backup set canceled. The Connection To Target System Has Been Lost Backup Set Canceled Backup Exec They cautioned me repeatedly that it wasn't supported and I could lose my backup job definitions, etc. (Understood, it's an Alpha, Beta or whatever you want to call it, I just CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical There is no other information besides that.

E000fe30 Backup Exec 15

Check the network, and then run the job again. 0 Message Expert Comment by:StratfrordDC2008-03-16 I am having the same problem with version 12.0 on a 2003 Server. Advanced Open File Option used: Symantec Volume Snapshot Provider (VSP). E000fe30 Backup Exec 2015 I have the same problem! Backup Exec 2014 A Communications Failure Has Occurred Just do it.

Unable to open the item \\servername\C:\Documents and Settings\Administrator\Local Settings\Temp\mmc035EBE2E.xml - skipped. http://onlinetvsoftware.net/backup-exec/backup-exec-12-5-error-e000fe30.php However, the odds are that they will hook you up with the hotfix for Bedsmbox.dll required to solve your headaches. Unable to open the item \\servername\C:\Documents and Settings\LocalService\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat - skipped. Anywho, any light you can shed would be helpful! 0 Message Accepted Solution by:StratfrordDC2008-05-11 My problem occurred after I upgraded to version 12. E000fe30 Backup Exec 2012

Connect with top rated Experts 9 Experts available now in Live! Advanced Open File Option used: Symantec Volume Snapshot Provider (VSP). Now locate your Backup Exec Install Media, locate the Remote agent for Windows folder (usually in winntinstall). this contact form Then, they mentioned it's a known issue and it was taking such a long time because they had to gather details for a hotfix for the Bedsmbox.dll file.

Unable to open the item \\servername\C:\Documents and Settings\LocalService\NTUSER.DAT - skipped. A Communications Failure Has Occurred Between The Backup Exec Job Engine And The Agent For Windows Unable to open the item \\servername\C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db - skipped. 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

View my complete profile (C) VPW / All Rights Reserved |.

  • You might see one or more listed in the following state: Writer name: 'System Writer'    Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}    Writer Instance Id: {b25db62a-f58e-4d9f-bf54-37f17f12742e}    State: [5] Waiting for completion   
  • So I'm a little baffled.
  • Urgh.
  • All rights reserved.
  • Join Now For immediate help use Live now!
  • Terms of use for this information are found in Legal Notices.

    Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may
  • 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.
  • 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.

Backup Exec would back the data up and show everything was ok. 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 Comment Submit Your Comment By clicking you are agreeing to Experts Exchange's Terms of Use. V-79-57344-65072 If it repeats you will need to contact Symantec Support and see if you might need the updated bedsmbox.dll.

Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password? 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- servername V-79-57344-34110 - AOFO: Initialization failure on: "C:". navigate here Tiring of the frustration, I did open a support incident after repeatedly bashing my head into a brick wall with protruding glass shards.

I then ran live update from the main console to apply 3 or 4 patches. Solved Backup Exec Error - e000fe30 - A communications failure has occurred. Sorry, we couldn't post your feedback right now, please try again later. On a x32 bit server run double click the following two files, setupaa.cmd and setupaofo.cmd (noting will happen other than a command window will flash up). 3.

Check the Windows Event Viewer for details. Snapshot provider error (0xE000851C): Cache files required for the Symantec Volume Snapshot Provider (VSP) snapshot could not be created. 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 Thank You!

Networking I've moved recently. View solution in original post 0 Kudos Reply 2 Replies Accepted Solution! Related Articles, References, Credits, or External Links NA Author: Migrated Share This Post On GoogleFacebookTwitter Search for: Copyright PeteNetLive © 2016 Back Search Search form Search this site SolutionsBusiness Intelligence Data I know you don't want to.

not so much. Test the individual components    a. I had to copy the RAWS32 directory from the remote server to the agent server and then execute the Go to Solution 13 Comments LVL 3 Overall: Level 3 Message The network connection failed during the snapshot.

IN THIS DISCUSSION Symantec Backup Exec Symantec 258196 Followers Follow Join the Community! Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? Here is what I got. You may also refer to the English Version of this knowledge base article for up-to-date information.

It's supposed to be a perpetual license. 0 Serrano OP Best Answer Elias_VTC (Veritas) Feb 20, 2015 at 8:12 UTC Brand Representative for Veritas Double check your firewall Check the network, and then run the job again. They blamed my network and the servers the agents were on.  Even when it did work we found out the hard way we couldnt restore any data from the backups.