Home > Backup Exec > Backup Exec E000fe30 Error

Backup Exec E000fe30 Error


Cause When attempting to run a backup or restore job to a Vmware ESX 3.5 server utilizing the Remote Agent for Linux and Unix Servers (RALUS) agent while the ESX firewall Work-Arounds for E000FE30 - A communications failure has occurred in Backup Exec. DOMAIN\Administrator)Click Change Password to enter the current password for this user in both the password and confirm fields. Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\modellog.ldf - skipped. http://waspsoft.com/backup-exec/backup-exec-12-5-error-e000fe30.html

I've spent 5 hours researching this on a brand new installation of Backup Exec 2010, and have 3 hours with support so far. Comment Submit Your Comment By clicking you are agreeing to Experts Exchange's Terms of Use. Double-Urgh. I have tested and re ran full backups, I have restarted the servers and made sure everything is up to date as well as making sure all the remote agents are

Backup Exec Error E0008821

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. Offload Receive IP ChecksumOffload Receive TCP ChecksumOffload TCP SegmentationOffload Transmit IP ChecksumOffload Transmit TCP ChecksumAll of them are turned on. We eventually gave up with Backup Exec, so while this was "Backup Exec Hell - The Daily Torture of making Backup Exec 10d, 12d and 12.5 work..." it's now "The Joy NOTE: The password entered is encrypted for security.

Veritas does not guarantee the accuracy regarding the completeness of the translation. Unable to open the item \\servername\C:\Documents and Settings\Administrator\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat - skipped. 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 Version 2010 R3 and earlier: On the Account Management dialog box, click OK.         Terms of use for this information are found in Legal Notices.

Related Articles

Now locate your Backup Exec Install Media, locate the Remote agent for Windows folder (usually in winntinstall). Email Address (Optional) Your feedback has been submitted successfully! Email Address (Optional) Your feedback has been submitted successfully! The logs did give me this: For additional information regarding this error refer to link V-79-57344-65072...

You could see the files on the backup to disc volume, but Back Exec couldnt during the restore. E000fe30 Backup Exec 2014 Covered by US Patent. In addition, verify NDMP port 10000 for control communications during a backup / restore has also been made available for the service. 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.

  • Note: Example open port command would be: esxcfg-firewall -o 50000,tcp,in,RALUS 2.
  • Check the Windows Event Viewer for details.
  • Error : e000fe30 - A communications failure has occurred.
  • Simple template.
  • Related Articles, References, Credits, or External Links NA Author: Migrated Share This Post On GoogleFacebookTwitter Search for: Copyright PeteNetLive © 2016 MenuExperts Exchange Browse BackBrowse Topics Open Questions Open Projects Solutions
  • Reconfiguring the system to use a different WAN link to ensure the fault isn't with the WAN.
  • Disabling the firewall, in troubleshooting this issue, allows successful backups and restores.This error is caused when the ESX server's firewall is not configured with correct port exceptions to be used by
  • Firstly make sure the Backup Exec Remote Agent service is running under the local system account.
  • I'm happy to report that after loading the replacement Bedsmbox.dll, the backups complete successfully.

Backup Exec Error 1603

If neither is the case, create a new account and assign it the SLA role. 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 Error E0008821 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 Backup Exec Error 1068 Create/Manage Case QUESTIONS?

I am just backing up a domain controller. navigate here IN THIS DISCUSSION Symantec Backup Exec Symantec 258197 Followers Follow Join the Community! When we bought that house, it had an unfinished basement and an unfinished attic room, making the cabling process very simple. Finally on launch Backup Exec and click Tools > Live Update > follow the instructions, Note: you may be asked for a reboot when its finished. E000fe30 A Communications Failure Has Occurred Backup Exec

Posted by The Backup Exec Goat at 11:00 Labels: backup, error messages, failed jobs 4 comments: Anonymous said... Symantec got me to re-install the agent locally. Unable to open the item \\servername\C:\WINDOWS\system32\dhcp\tmp.edb - skipped. Check This Out Advanced Open File Option used: No.

V-79-57344-34110 - AOFO: Initialization failure on: "\\servername\System?State". Backup Exec Error Code E000fe30 Open 50 ports (i.e. Example iptables firewall rule: -A RH-Firewall-1-INPUT -sxx.xx.xx.xx -p tcp -m tcp -j ACCEPT Where xx.xx.xx.xx equals the IP Address of the backup server.

Unable to open the item \\servername\C:\Documents and Settings\NetworkService\NTUSER.DAT - skipped.

If that doesn't help, light up support and move on with your day with more of a smile than a frown. Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\tempdb.mdf - skipped. Nothing I've found fixed the problem of the pesky "E000FE30 - A communications failure has occurred" error. E000fe30 Backup Exec 15 Creating your account only takes a few minutes.

Powered by Blogger. All rights reserved. You're not alone! this contact form Join Now For immediate help use Live now!

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 Join our community for more solutions or to ask questions. Call Toll Free | Contact Us | My Account KB Browse Categories Affiliates Backup & Restore Billing & MyAccount FAQs Control Panels Customer Tools Databases Dedicated Servers DNS and Domain Registration Want to Advertise Here?

Do you know what might happen if I were to turn all of them off? 25 January 2010 at 17:16 The Backup Exec Goat said... 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. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Thank You!

The network connection failed during the snapshot. Urgh. AOFO: Initialization failure on: "servername\SQLSERV". However it did provide me with more information this time.

Snapshot provider error (0xE0008520): Device could not be snapped because it contains an active cache file. Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\mastlog.ldf - skipped.