Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\msdblog.ldf - skipped. Unable to open the item \\servername\C:\Documents and Settings\Administrator\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat - skipped. Here is what I got. Unable to open the item \\servername\C:\WINDOWS\system32\wins\winstmp.mdb - skipped. http://mmonoplayer.com/backup-exec/e000fe30-a-communications-failure-has-occurred-backup-exec.html
Advanced Open File Option used: No. 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 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: Personal tools Namespaces Article Search Main Page Applications AOL Internet Explorer MS Outlook Outlook Express Windows Live DLL Errors Exe Errors Ocx Errors Operating Systems Windows 7 Windows Others Windows
Ensure that WMI is running and that it's not blocked by a firewall. 1603". Powered by Blogger. Email Address (Optional) Your feedback has been submitted successfully! Labels: 2010 Agent for VMware Virtual Infrastructure Backup and Recovery Backup Exec Restore VMware VMworld Windows 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution!
More from the Author Richard Clapp Systems Engineer LinkedIn Cleaning Up WinSXS Folder on Windows Server 2008 R2 Posted 07.16.14 Getting Access to Multiple Branches while Using a Split VPN Tunnel I can't disable the AV. Exchange Information store f. A Communications Failure Has Occurred Between The Backup Exec Job Engine And The Remote Agent This tool will scan and diagnose, then repairs, your PC with patent pending technology that fix your windows operating system registry structure.
This Symantec Backup Exec Error E000fe30 A Communications Failure Has Occurred error code has a numeric error number and a technical description. Veritas does not guarantee the accuracy regarding the completeness of the translation. Join Now Anybody ever come across this error in Symantec Backup Exec? It looks like it's having a problem communicating with the backup exec agents, but I can't seem to figure What should I try next?
View this "Best Answer" in the replies below » 11 Replies Pimiento OP Matagorda County Feb 20, 2015 at 7:35 UTC I had this same problem in 2010R3 Final Error: 0xe000fe30 - A Communications Failure Has Occurred. If it repeats you will need to contact Symantec Support and see if you might need the updated bedsmbox.dll. Join & Ask a Question Need Help in Real-Time? Most of the solutions I found relate to Exchange but in my case I am not backing up Exchange.
There are two (2) ways to fix Symantec Backup Exec Error E000fe30 A Communications Failure Has Occurred Error: Advanced Computer User Solution (manual update): 1) Start your computer and log check over here Symantec got me to re-install the agent locally. Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\model.mdf - skipped. The Symantec Backup Exec Error E000fe30 A Communications Failure Has Occurred error may be caused by windows system files damage. E000fe30 Backup Exec 2015
In Backup Exec, set port rage use in step 1 under Tools | Options | Network & Security 3. This is common error code format used by windows and other windows compatible software and driver vendors. Great for personal to-do lists, project milestones, team priorities and launch plans. - Combine task lists, docs, spreadsheets, and chat in one - View and edit from mobile/offline - Cut down his comment is here I then ran live update from the main console to apply 3 or 4 patches.
View solution in original post 0 Kudos Reply 2 Replies Accepted Solution! E000fe30 Backup Exec 15 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 The network connection failed during the snapshot.
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. Click here follow the steps to fix Symantec Backup Exec Error E000fe30 A Communications Failure Has Occurred and related errors. Suggested Solutions Title # Comments Views Activity exchange 7 54 98d Tool to discover installed software on Network 3 75 82d How to check the PVU´s on AIX TSM servers? 3 V-79-57344-65072 - The Connection To Target System Has Been Lost. Backup Set Canceled. Thanks!
I'm not sure, but I'm happy to blame it since everything else works just fine. Even with BE 2012 SP2 which is due to be released soon, BE 2012 can only back up Windows 2012. 0 Kudos Reply I'm sorry - I just checked - CWTokyo Thus, having more than one copy of … Disaster Recovery Storage Software Virtualization VMware Installing and Configuring Windows Server Backup Utility Video by: Rodney This tutorial will walk an individual through weblink Backup- \\servername\D: Data V-79-57344-34110 - AOFO: Initialization failure on: "\\servername\Shadow?Copy?Components".
Advanced Open File Option used: No.