Home > Backup Exec > Symantec Backup Exec Error E000fe30

Symantec Backup Exec Error E000fe30

Contents

Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Job fails each time - Error e000fe30 - I'm having a problem with a Windows 2003 Server that is running MSSQL 2005 and is also a guest VM on esx 3.0.1. Dezember 2006 at 23:28:37Completed status: FailedFinal error: 0xe000fe30 - A communications failure has occurred.Final error category: Server ErrorsFor additional information regarding this error refer to link V-79-57344-65072Errors Click an error below Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\model.mdf - skipped. this content

Firstly make sure the Backup Exec Remote Agent service is running under the local system account. Unable to open the item \\servername\C:\Program Files\SAV\SAVRT\0719NAV~.TMP - skipped. 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. This hotfix is not pkh Moderator Trusted Advisor Certified ‎01-31-2012 05:08 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content

E000fe30 Backup Exec 2010

Hope you’ll enjoy it and will choose the one as required by you. Backup- \\server name\D: DataV-79-57344-65072 - The connection to target system has been lost. I would test with two different jobs, one for data and see if it finishes without failures and one with just the shadow components...the other way to test would be use The BE server is also a file server and it runs like clockwork to the same NAS with no failures.

Get 1:1 Help Now Advertise Here Enjoyed your answer? Unable to open the item \\servername\C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\security.config.cch.2172.13372828 - skipped. Backup- servername V-79-57344-34110 - AOFO: Initialization failure on: "C:". A Communications Failure Has Occurred Between The Backup Exec Job Engine And The Remote Agent The 2008 server has been in place for a few months now, the first couple months the server had some files but not alot (approx 100 GB of files and data),

Unable to open the item \\servername\C:\Documents and Settings\Administrator\Local Settings\Temp\mmc035EBE2E.xml - skipped. E000fe30 Backup Exec 2014 By 24 hours a day, I mean 10 minutes doing everything else, and 23h 50m dealing with Backup Exec failures. The "Large TCP Offload" feature on the Network Card. Make sure that no other application has a lock on the cache files created by the snapshot operation. 0 LVL 3 Overall: Level 3 Message Expert Comment by:ssparks827 ID:

Backup- \\servername\C: Unable to open the item \\servername\C:\Documents and Settings\Administrator\NTUSER.DAT - skipped. E000fe30 Backup Exec 2012 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. Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\templog.ldf - skipped.

E000fe30 Backup Exec 2014

Reply Subscribe RELATED TOPICS: Symantec backup exec, connectivity issue BE 2014 v-ray job failing after upgrade Can you run 2 schedule at the same time in Backup Exec? All rights reserved. E000fe30 Backup Exec 2010 For example BE server -> fax server on 10000 fax server -> BE server on 10000 fax server to NAS -> 445, 139 BE server -> fax server on 441 Backup Exec 2014 A Communications Failure Has Occurred Backup- \\servername\D: Data V-79-57344-34110 - AOFO: Initialization failure on: "\\servername\Shadow?Copy?Components".

Thanks. 0 Kudos Reply Contact Privacy Policy Terms & Conditions Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision news Advanced Open File Option used: No. 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 Open the appropriate folder. 3. 0xe000fe30 - A Communications Failure Has Occurred.

I had to copy the RAWS32 directory from the remote server to the agent server and then execute the Go to Solution 6 3 2 +2 5 Participants tmelton82(6 comments) ssparks827(3 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 I also found this article that says Symantec is aware of the problem. have a peek at these guys http://seer.entsupport.symantec.com/docs/285437.htm 0 Kudos Reply Make sure the VSS is enabled chicojrman Level 6 ‎04-14-2009 12:35 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to

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! E000fe30 Backup Exec 2015 I have a call logged with Symantec and will share the resolution if and when I get a response. 0 Message Expert Comment by:pslitbuy ID: 215337382008-05-09 StratfordDC did you ever However it did provide me with more information this time.

Connect with top rated Experts 13 Experts available now in Live!

You would have to download and install it. 0 Kudos Reply I downloaded and installed Devan10 Level 3 ‎02-01-2012 01:05 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Join our community for more solutions or to ask questions. I also found this article that says Symantec is aware of the problem. E000fe30 Backup Exec 15 Backup Exec would back the data up and show everything was ok.

An event is listed in the application event log Source:BackupExec Category:None Event ID:34113 Labels: 12.x and Earlier Backup and Recovery Backup Exec Configuring 0 Kudos Reply 4 Replies Having the same My mistake. 0 Kudos Reply ...if there is an AV on that CraigV Moderator Partner Trusted Advisor Accredited ‎07-16-2013 11:54 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Finally on launch Backup Exec and click Tools > Live Update > follow the instructions, Note: you may be asked for a reboot when its finished. check my blog The 2008 server is set to do daily backups, weekly backups and monthly backups.

Unable to open the item \\servername\C:\WINDOWS\system32\dhcp\tmp.edb - skipped. Join the community of 500,000 technology professionals and ask your questions. About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up Check the Windows Event Viewer for details.

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 Powered by Blogger. The job history indicates that it has backed up my C &Ddrives. 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