Home > Backup Exec > Backup Exec Error 0xe000fe30

Backup Exec Error 0xe000fe30

Contents

The error is generated when Backup Exec (tm) is missing a system logon account (Figure 1).   UMI - V-79-57344-34041Figure 1  Cause The Backup Exec System Logon Account (SLA) on the Backup To check for a system logon account In Backup Exec do one of the following: On version 2012 - Click the Backup Exec button | Configuration and Settings | Logon Accounts No Yes Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Veritas.com Support Communities Veritas does not guarantee the accuracy regarding the completeness of the translation. http://sovidi.com/backup-exec/backup-exec-final-error-0xe000fe30.php

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 Open your browser and go to crashplan.com: Click get started, it’s free then Click the Download CrashPlan button: Click save in Internet Explorer, the… Windows 8 PCs Storage Software Cloud Computing If this password is not available, select a different account or skip to section , ‘To create the system logon account.’ Do the following: If the account does not have the The network is not effective for the direct access between Backup Exec Remote Agent and the deduplication storage device.

Backup Exec 2014 0xe000fe30 A Communications Failure Has Occurred

No Yes How can we make this article more helpful? In addition, verify NDMP port 10000 for control communications during a backup / restore has also been made available for the service. Job Completion Status  Completed status: Failed Final error code: a00084f9 HEX Final error description: A communications failure has occurred between the Backup Exec job engine and the remote agent. Open 50 ports (i.e.

  1. BE likes to use IPV4 and so I had to hash out the ::1 reference on the Exchange server and place in 127.0.0.1 references for the system name & System FQDN
  2. http://seer.entsupport.symantec.com/docs/255814.htm look at this article.
  3. Sorry, we couldn't post your feedback right now, please try again later.
  4. Verify that the backup job in question is using the updated or newly created SLA before its next use.
  5. After some very helpful support from Symnatec we finally renamed the DEDSRman.dll on all the nodes and all started to work again.
  6. My DC is a Win2008 Server.

Final error category: Server Errors What i already tried : Reinstalling beremote (did not work) Cheking the ports (did not work) What does work: exchange backup. You may also refer to the English Version of this knowledge base article for up-to-date information. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Backup job fails with a communications failure when all of the following conditions are If neither is the case, create a new account and assign it the SLA role.

It was an IPV6 issue. Connect with top rated Experts 10 Experts available now in Live! It was an IPV6 issue. is the server shut down or restarted during the process?

Sorry, we couldn't post your feedback right now, please try again later. Final error category: Server Errors sivakakani Level 3 ‎04-22-2009 01:58 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I No Yes Did this article save you the trouble of contacting technical support? We want to be able to exit in case of errors 2.

E000fe30 A Communications Failure Has Occurred Backup Exec

NOTE: If not logged on to Backup Exec server with the same user name as the Backup Exec logon account being edited, Backup Exec prompted to provide the account owner’s password 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. Backup Exec 2014 0xe000fe30 A Communications Failure Has Occurred No Yes Did this article save you the trouble of contacting technical support? V-79-57344-65072 - The Connection To Target System Has Been Lost. Backup Set Canceled. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?

Firstly make sure the Backup Exec Remote Agent service is running under the local system account. http://sovidi.com/backup-exec/backup-exec-error-backup-snapshot-already-exists.php Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Backup of remote server, the error "0xe000fe30 - A communications failure has 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 Create/Manage Case QUESTIONS?

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 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 Create/Manage Case QUESTIONS? Check This Out to 3.4.2.

To install this feature, go to Server Manager… Windows Server 2012 Storage Software CrashPlan on Windows 8 Video by: Thomas The viewer will learn how to download, install and use CrashPlan It is possible that updates have been made to the original version after this document was translated and published. Create/Manage Case QUESTIONS?

Are you using any SQL VJware Level 6 Employee Accredited Certified ‎02-28-2012 12:04 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? You may also refer to the English Version of this knowledge base article for up-to-date information. No Yes How can we make this article more helpful? Finally on launch Backup Exec and click Tools > Live Update > follow the instructions, Note: you may be asked for a reboot when its finished.

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. Create/Manage Case QUESTIONS? This resolved the issue and it is now restoring like a champ! http://sovidi.com/backup-exec/backup-exec-error-cannot-extract-mailbox-messages-exchange-backup.php Event ID 1000 in Windows event viewer shows the above dll error.