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

E000fe30 A Communications Failure Has Occurred Backup Exec

Contents

AOFO: Initialization failure on: "servername\SQLSERV". Experiences, tips, problems, rants and ideas. Performing a full backup does not require checking the log file consistency, as all files' archive bits are reset when a full is done. Log onto the Backup Exec Central Administration Server. http://mmonoplayer.com/backup-exec/backup-exec-2014-a-communications-failure-has-occurred.html

I tried it anyway and was pointed to the Backup Exec Remote Agent for Windows Servers (RAWS) crashing. Symantec got me to re-install the agent locally. I'm not sure, but I'm happy to blame it since everything else works just fine. It says No for AOFO used but I have the box checked to choose the AOFO type automatically.

E000fe30 A Communications Failure Has Occurred Backup Exec

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 Unable to open the item \\servername\C:\Documents and Settings\Administrator\Local Settings\Temp\mmc0770157C.xml - skipped. Unable to open the item \\servername\C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.log - skipped.

Help Desk » Inventory » Monitor » Community » Back Search Search form Search this site SolutionsBusiness Intelligence Data Management IT Infrastructure About UsCulture Careers Locations Partners People ResourcesViz Gallery Case Join and Comment By clicking you are agreeing to Experts Exchange's Terms of Use. Join and Comment By clicking you are agreeing to Experts Exchange's Terms of Use. E000fe30 Backup Exec 2012 Join our community for more solutions or to ask questions.

In other words, Symantec has had some success with splitting the backups into two jobs, one for files and one for the Exchange Server. E000fe30 Backup Exec 2014 Now locate your Backup Exec Install Media, locate the Remote agent for Windows folder (usually in winntinstall). That link gave about 7 specific situations, unfortunately none of which exactly applied to my situation. Login.

Unable to open the item \\servername\C:\WINDOWS\system32\wins\winstmp.mdb - skipped. A Communications Failure Has Occurred Between The Backup Exec Job Engine And The Remote Agent Advanced Open File Option used: No. Backup set canceled. The description for the event was: "Faulting application beremote.exe, version 13.0.2896.0, time stamp 0x4b184ba1, faulting module bedsmbox.dll, version 13.0.2896.0, time stamp 0x4b184b99, exception code 0xc0000005, fault offset 0x0000000000040bf0, process id 0x%9,

E000fe30 Backup Exec 2014

Backup set canceled. Get 1:1 Help Now Advertise Here Enjoyed your answer? E000fe30 A Communications Failure Has Occurred Backup Exec The logs will show which actual files have been altered by having the archive bit set. Backup Exec 2014 A Communications Failure Has Occurred Email Address (Optional) Your feedback has been submitted successfully!

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 weblink Interesting site, tis a shame it's still not kept going. Advanced Open File Option used: No. Thank You! 0xe000fe30 - A Communications Failure Has Occurred.

If all these pass try Adding two of them together and re-test.    a. Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : E000FE30 - A communications failure has occurred i... The network connection failed during the snapshot. navigate here Unable to open the item \\servername\C:\Documents and Settings\LocalService\NTUSER.DAT - skipped.

Tiring of the frustration, I did open a support incident after repeatedly bashing my head into a brick wall with protruding glass shards. E000fe30 Backup Exec 2015 Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\master.mdf - skipped. Veritas does not guarantee the accuracy regarding the completeness of the translation.

Backup set canceled. 0 LVL 3 Overall: Level 3 Message Expert Comment by:ssparks827 ID: 207396022008-01-24 What is being backed up on the DC?

I am using Backup Exec 10.0, doing a Differential Exchange backup and have the Advanced Open File Options unchecked. Unable to open the item \\servername\C:\Documents and Settings\Administrator\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat - skipped. Unable to open the item \\servername\C:\Documents and Settings\Administrator\Local Settings\Temp\mmc0EF21990.xml - skipped. E000fe30 Backup Exec 15 For a partial (incremental or differential) backup, Backup Exec is looking for the logs from the last backup to determine what has changed (by way of an archive bit) since the

Unable to open the item \\servername\C:\Program Files\SAV\SAVRT\0129NAV~.TMP - skipped. 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. Covered by US Patent. http://mmonoplayer.com/backup-exec/backup-exec-rpc-service.html Suggested Solutions Title # Comments Views Activity LINUX : Create user with required privilages to take backup of a file system 5 59 132d Windows 2012 R2 as a File &

View solution in original post 0 Kudos Reply 2 Replies Accepted Solution! 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 Offload Receive IP ChecksumOffload Receive TCP ChecksumOffload TCP SegmentationOffload Transmit IP ChecksumOffload Transmit TCP ChecksumAll of them are turned on. 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.

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 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 Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page E000FE30 - A communications failure has occurred in First SAN After a major ERP upgrade, the company needed more storage, storage performance, and storage reliability across several business units, servers, and applications.

The backup would complete, and then I could re-select the Do Consistency Check again. 0 LVL 4 Overall: Level 4 Exchange 4 Windows Server 2003 1 Storage Software 1 Message 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 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    Join Now For immediate help use Live now!

You may also refer to the English Version of this knowledge base article for up-to-date information. Backup set #2 on storage media #15 Drive and media mount requested: 1/24/2008 2:13:48 PM Drive and media information from media mount: 1/24/2008 2:13:59 PM Drive Name: Server Name Media Label: 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 I'm happy to report that after loading the replacement Bedsmbox.dll, the backups complete successfully.

I am just backing up a domain controller. Support spent a couple hours gathering information, running backup jobs (that of course failed), double-checking the most basic of things. (OK, I understand, it's due dilligence)... Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\templog.ldf - skipped.