Posted by The Backup Exec Goat at 11:00 Labels: backup, error messages, failed jobs 4 comments: Anonymous said... Given the error, we suspected "something" to do with comms, but never found any issue, and in hundreds of tests conducted could never replicate the issue - transferring large files to/fro Thank You! Unable to open the item \\servername\C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db - skipped. Check This Out
V-79-57344-34110 - AOFO: Initialization failure on: "\\servername\System?State". Unable to open the item \\servername\C:\Program Files\SAV\SAVRT\0719NAV~.TMP - skipped. esxcfg-firewall -Q If the ports are not specified proceed to the resolution section NOTE: Symantec recommends having NDMP port 10000 and a specific dynamic port range available on the Backup Get 1:1 Help Now Advertise Here Enjoyed your answer?
Featured Post Do email signature updates give you a headache? Connect with top rated Experts 9 Experts available now in Live! LEARN MORE Suggested Solutions Title # Comments Views Activity Looking for cloud backup solution for Windows Small Business Server that also compatible with Microsoft Exhange 5 13 109d Anything better than Backup Exec 2010 Error 1603 I have the Information Stores backing up on a separate job from the System State, Public Folders, etc. 0 Message Accepted Solution by:Darthyw2007-05-09 I resolved this awhile ago.
Here is what I got. E000fe30 Backup Exec 2014 Unable to open the item \\servername\C:\WINDOWS\system32\dhcp\tmp.edb - skipped. Email Address (Optional) Your feedback has been submitted successfully! Spending all of your time at every user’s desk to make updates?
skip to main | skip to sidebar E000FE30 - A communications failure has occurred Thursday, March 4, 2010 E000FE30 - A communications failure has occurred If you use Backup Exec from Backupexec E000fe30 All rights reserved. Join & Ask a Question Need Help in Real-Time? 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
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 Unable to open the item \\servername\C:\Documents and Settings\Administrator\Local Settings\Temp\mmc0EF21990.xml - skipped. Symantec Backup Exec Error E000fe30 Unable to open the item \\servername\C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\security.config.cch.2172.13372828 - skipped. Backup Exec Error Code E000fe30 No Yes Did this article save you the trouble of contacting technical support?
Unable to open the item \\servername\C:\Documents and Settings\LocalService\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat - skipped. his comment is here AOFO: Initialization failure on: "servername\SQLSERV". Check the network, and then run the job again. Here is the error for just the SQL instance. E000fe30 A Communications Failure Has Occurred Backup Exec
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:ssparks8272008-01-28 Do Check the Windows Event Viewer for details. Backup- \\servername\D: Data V-79-57344-34110 - AOFO: Initialization failure on: "\\servername\Shadow?Copy?Components". http://onlinetvsoftware.net/backup-exec/backup-exec-12-5-error-e000fe30.php Help Desk » Inventory » Monitor » Community » MenuExperts Exchange Browse BackBrowse Topics Open Questions Open Projects Solutions Members Articles Videos Contribute Products BackProducts Gigs Live Careers Vendor Services Groups
You can stop and start the Volume Shadow Copy Services, reboot the server, or try a backup of just the system state to try and get the stuck VSS back into E000fe30 Backup Exec 15 Unable to open the item \\servername\C:\Program Files\SAV\SAVRT\0129NAV~.TMP - skipped. Microsoft to end Windows 7 PC sales, Firefox tackles weak encryption Spiceworks Originals A daily dose of today's top tech news, in brief. © Copyright 2006-2016 Spiceworks Inc.
Covered by US Patent. 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 Advanced Open File Option used: No. E000fe30 Backup Exec 2015 Interesting site, tis a shame it's still not kept going.
Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your 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) Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password? http://onlinetvsoftware.net/backup-exec/backup-exec-e000fe30-error.php Exclaimer Exchange Office 365 Outlook Migrate Remote IP Addresses to a New Relay Connector Article by: Todd "Migrate" an SMTP relay receive connector to a new server using info from an
My backups report a failure with the following description Error category : Server ErrorsError : e000fe30 - A communications failure has occurred. Create/Manage Case QUESTIONS? There is no other information besides that. Ihave applied the DCOMFIG modifications to no avail.
Backup- servername V-79-57344-34110 - AOFO: Initialization failure on: "C:". Sorry, we couldn't post your feedback right now, please try again later. Or cheaper 9 92 67d what happens to MS-Access (Office suite) transactions if sudden disk failure.. 8 91 54d Change Retention policy - Windows server backup - Windows 2012 R2 2 The one you pick depends on weather your running 32 bit or 64 bit software.
I'm beginning to think going into IT was a mistake Water Cooler I earned my CompTIA A+ certification in 2013, and began going to school for Computer Science in 2014. We eventually gave up with Backup Exec, so while this was "Backup Exec Hell - The Daily Torture of making Backup Exec 10d, 12d and 12.5 work..." it's now "The Joy I'm backing up system state, some of the directory structure and the SQL instance. 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:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\mastlog.ldf - skipped. Join Now For immediate help use Live now! Unable to open the item \\servername\C:\Documents and Settings\Administrator\Local Settings\Temp\mmc035EBE2E.xml - skipped. Open the appropriate folder. 3.
But did you ever see this?http://seer.entsupport.symantec.com/docs/290098.htmIt was posted before your blog about TCP Offload. 16 April 2010 at 08:09 PeteLong said... Connect with top rated Experts 9 Experts available now in Live!