Home > Symantec Error > Symantec Error Code E0008703

Symantec Error Code E0008703

Contents

I tried backing up a few files and it backed up fine then did a test run the same files i backed up and its still doing the same thing :-( No Yes Did this article save you the trouble of contacting technical support? I have rebooted the NAS already but i havent tried running a full backup yet, i'll rebooting it again and check for the sleep mode as well and run it tonight. Please advise? :) Thanks Also, could a bad block within the 5gb's that we excluded cause these sorts of issues? 0 Tabasco OP erok Jul 19, 2013 at http://allconverter.net/symantec-error/symantec-error-e0008703.html

I've below 2 questions: 1. 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 But No files are getting backup Solved Backup fails in test Run, Normal Backup Job successfully completes. Thanks for the minimal help and article links that I located on the first page of a basic google search for my error numbers. 3 symantec reps. 1 thread. 1 work

V-79-57344-34563

Check if there is Windows Delayed Write Failed error has occured in Windows Event Viewer when backup job was running. 3. The full backup does not backup the full capacity of VMDK. Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? I can't do this hit or miss thing.

yes no add cancel older | 1 | .... | 107 | 108 | 109 | (Page 110) | 111 | 112 | 113 | .... | 445 | newer HOME What is more troubling, is that Symantec claims, via Dell, that the Storage Provisioning option is no longer supported in Backup Exec 2012, and they do not have an alternative solution.  Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password? See log file for details" (a0008703 HEX or e0008703 HEX) No devices found to run job is reported when running a "Test Run"   Error Message Final Error Code:  a0008703 HEX

Thanks for recommending that I check to see if my drive was full Jay... *makes rasberry sound and a thumbs down jesture*   Textcd /d %windir%\system32 net stop vss net stop Can anyone offer any suggestions as to why this might be the case on this particular system? AWS Cloud Computing Linux Advertise Here 705 members asked questions and received personalized solutions in the past 7 days. I think...

BE 2010|2010 R2|2010 R3 Hardware (HCL) 0 Kudos Reply I'm writing to a Buffalo ltjimster Level 6 ‎07-16-2013 01:51 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Im not terribly familiar with this error but will begin digging on it immediately. This is the second time this has happened and last time I just cut a random 50gb of my backup out and it worked. You may get a better answer to your question by starting a new discussion.

Backup Exec 2014 0xe0008703

http://www.symantec.com/docs/TECH195898 0 Kudos Reply nothing different as far as i ltjimster Level 6 ‎07-15-2013 08:22 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email Have tried new and old tapes, drive and autoloader firmware is current @ 10/713 and we've even rebuilt the backup server just in case. V-79-57344-34563 Help Desk » Inventory » Monitor » Community » Home Backup Exec Error by ITGirl007 on May 13, 2011 at 9:26 UTC | Data Backup 0Spice Down Next: Need ideas on 0xe0008703 - The Test Run Has Detected A Potential Problem Connect with top rated Experts 14 Experts available now in Live!

Use help to read help documents for built in bash shell commands.: Use man to interface with the online reference manuals for shell commands.: Use man to search man pages for weblink 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 By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. did a test backup fails with the error code E0008703.

What kind of data are you targeting in this backup job? They had Backup Exec running default build and it was erroring out constantly. Thank you. navigate here Any help would be much appreciated.

Contact us about this article I need a solution I am running BackupExec 2012 on Windows Server 2008 with a QuikStor 320GB drive. Have you tried to run the actual job anyway to see if you get the same error? Their infrastructure was out of date with a long list of band aid fixes.

Join Now For immediate help use Live now!

All Windows. That server is physically attached to a Dell MD1000 storage array. Please give us more details as to how the job is configured. I think...

Are you running a differential or incremental job? Unknown error = low disk space? 0 Cayenne OP Helpful Post Syldra Oct 9, 2013 at 1:29 UTC Agreed with Denis Kelley, 750GB is theorical/unformatted capacity and usually Labels: 2010 Backing Up Backup and Recovery Backup Exec Configuring Error messages Managing Backup Devices Windows Server (2003-2008) 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution! ...have you checked to http://allconverter.net/symantec-error/symantec-error-code-11.html of course I have no clue where it is.

write caching stays enabled even after I go in and disable the check mark. 0 Jalapeno OP Donald (Symantec) Jul 16, 2013 at 2:04 UTC Erok... Has anyone else experienced this or can provide any assistance? I need reliable backups :/ 0 Tabasco OP erok Jul 18, 2013 at 11:44 UTC bump? 0 Tabasco OP erok Jul 18, 2013 at 6:13 Thanks! 0 Kudos Reply James, Are you Donald_Eady Level 6 Employee Accredited ‎07-15-2013 07:25 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print

It gives me the option of going back an UN-installing my current Storage Provisioning option, but I am afraid Backup Exec will then no longer be able to see or configure Which would be fine if I wasn't running windows server 2003 r2 with 2 terabytes of data. Any suggestions?