If neither is the case, create a new account and assign it the SLA role. Check the network, and then run the job again. However it did provide me with more information this time. Related Articles, References, Credits, or External Links NA Author: Migrated Share This Post On GoogleFacebookTwitter Search for: Copyright PeteNetLive © 2016 skip to main | skip to sidebar E000FE30 - A http://gatoisland.com/backup-exec/backup-exec-e000fe30-error.php
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 Do BaileyGeek Level 2 04-05-2009 02:48 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Having the same issue. For additional information regarding this error refer to link V-79-57344-65072 My configuration is as follows: Microsoft Small Business Server 2003r2 w/ 4GBRam Symantec BackupExec for Windows 12 (Small Business Server License) not so much.
Do you have an update? 0 Kudos Reply Ditto Manny99 N/A 04-14-2009 10:23 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\modellog.ldf - skipped. We have a nearly identical duplicate of this server for development and it backs up just fine.
I then ran live update from the main console to apply 3 or 4 patches. http://seer.entsupport.symantec.com/docs/285437.htm Please go therough this document and then verify: http://support.veritas.com/docs/262333 Also download this utility in order to check that the port 10000 is not being used by any other port : Check the Windows Event Viewer for details. 0xe000fe30 - A Communications Failure Has Occurred. Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\master.mdf - skipped.
Snap! Backup Exec 2014 A Communications Failure Has Occurred IN THIS DISCUSSION Symantec Backup Exec Symantec 258197 Followers Follow Join the Community! Image 1: Backup Exec log Image 2: Esxi 5.0 (destination server ) - network performace Image 3: Windows Event log (event id: 1000) Solved! Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\tempdb.mdf - 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. E000fe30 Backup Exec 2010 The network connection failed during the snapshot. Get 1:1 Help Now Advertise Here Enjoyed your answer? Backup- \\server name\D: DataV-79-57344-65072 - The connection to target system has been lost.
It is possible that updates have been made to the original version after this document was translated and published. this contact form Go to Solution E000FE30 - A communications failure has occurred in Backup Exec Error adam3344 Level 2 05-23-2012 05:47 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight With R3 everything works fine. I'm trying to restore VM form Tape, backed up with Backup Exec 2010 13.0. E000fe30 A Communications Failure Has Occurred Backup Exec
Backup set canceled. Symantec got me to re-install the agent locally. You may also refer to the English Version of this knowledge base article for up-to-date information. http://gatoisland.com/backup-exec/backup-exec-12-5-error-e000fe30.php 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
Thanks! I'm backing up system state, some of the directory structure and the SQL instance. Veritas does not guarantee the accuracy regarding the completeness of the translation. E000fe30 Backup Exec 15 Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : e000fe30 - A communications failure has occurred VOX : Backup and Recovery :
Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? Click OK.Do one of the following: On version 2012: 1. On the Edit Logon Credentials dialog box, click OK. 2. On the Logon Account Management dialog box, click OK.On version 2010 R3 and Verify that the backup job in question is using the updated or newly created SLA before its next use. Check This Out We ended up having to abandon Backup Exec and go elsewhere. 0 Jalapeno OP Craig IT Feb 20, 2015 at 7:37 UTC well that turns my stomach... 0
Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\msdblog.ldf - skipped. Firstly make sure the Backup Exec Remote Agent service is running under the local system account. Sorry, we couldn't post your feedback right now, please try again later. Unable to open the item \\servername\C:\Documents and Settings\Administrator\Local Settings\Temp\mmc0770157C.xml - skipped.
You may get a better answer to your question by starting a new discussion. No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES