Home > Backup Exec > Backup Exec Error Code 34113

Backup Exec Error Code 34113

Contents

All rights reserved. Login By creating an account, you're agreeing to our Terms of Use and our Privacy Policy © Copyright 2006-2016 Spiceworks Inc. Check for network errors. Below are the details of the message. [4400] 05/10/13 23:25:10 Adamm Mover Error: DeviceIo: 05:00:06:00 - Device error 1117 on "\\.\Tape0", SCSI cmd 08, 1 total errors %2 %3 %4 %5 http://sovidi.com/backup-exec/backup-exec-34113-error.php

Click on the Job Monitor tab. 3. Join the community Back I agree Powerful tools you need, all for free. Update: The solution provided above does only work on a 2003 server based system. See the job log for details.

Backup Exec 34113 Job Failed

Chipotle Mar 1, 2010 Flip Other, 101-250 Employees Occurs when an action is aborted by the user or by an error. Microsoft Customer Support Microsoft Community Forums Event Id34113Event SourceBackup ExecDescriptionBackup Exec Alert: Job Failed. (Server: ) (Job: ) -- The job failed with the following error: For more information, click the Click the error detail to find the error location in the job log.Figure 1    6. The main reason is usually cost.

Update the selection list and run the job again. This is usually caused by dirty read/write heads in the tape drive. Solution: Open Registry on the remote serverStart->Run->RegeditNavigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\ParameterCreate a new Dword value named IRPStackSize (case sensitive).Modify the value to between 11 and 50. (15 is the default value when the key is Event Id 34113 Backup Exec 15 See the referenced information below to run an AppCritical test; also, this same information is available from   www.symantec.com/docs/TECH34993   Download the AppCritical Sequencer from   www.apparentnetworks.com/sas/   The Sequencer executables must be run

Please work with Symantec to solve this problem. Backupexec 34113 Email check failed, please try again Sorry, your blog cannot share posts by email. %d bloggers like this: ⚑ Deus Ex Machina ➽ Eventlog Lookup DxM Home | Registry Deus Ex Make sure that you select the write test and that you have stopped all the BE services beforehand. 0 Kudos Reply I have a Dell PowerVault 114T whitehurstge Level 3 ‎05-14-2013 Comment Submit Your Comment By clicking you are agreeing to Experts Exchange's Terms of Use.

Also, the target server must be able to respond to ping and traceroute (ICMP) requests.  Eliminate the 10Base T hub and connect the media server and/or the remote agent server directly Event Id 34113 Backup Exec 2010 R3 Click and expand the Errors section to get the error detail. Yes: My problem was resolved. Check for network errors.

Backupexec 34113

Create/Manage Case QUESTIONS? Check for network errors. Backup Exec 34113 Job Failed WMI, System, and IIS Config. Event Id 34113 Backup Exec 2012 Open Backup Exec User Interface (UI). 2.

This is how video conferencing should work! http://sovidi.com/backup-exec/backup-exec-12-5-error-34113.php c)Configure the "Automatic Response" for media alerts to automatically respond within 15 minutes.--------------------------------------------------------------------------------------------------------------------
CAUSE: 1) the remote agent service for Backup Exec may stopped. 2)This error could also be generated when In some instances, this could be attributed to piping the Backup Exec Server and/or the Remote Server to a 10Base T Hub and not directly to the switch. Recommend Us Quick Tip Connect to EventID.Net directly from the Microsoft Event Viewer!Instructions Customer services Contact usSupportTerms of Use Help & FAQ Sales FAQEventID.Net FAQ Advertise with us Articles Managing logsRecommended Event Id 34113 Backup Exec 2014

You can do this using the Backup Exec management interface, or you can find the job logs in %ProgramFiles%\Symantec\Backup Exec\Data. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? I anyone need any more information do let me know. http://sovidi.com/backup-exec/backup-exec-error-34113.php Join & Ask a Question Need Help in Real-Time?

x 9 Private comment: Subscribers only. Event Id 34113 Backup Exec 2015 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 No Yes Did this article save you the trouble of contacting technical support?

You may also see "Corrupt data encountered" - in which case you will need to look at the logs for this particular backup job, on the Backup Exec server.

  1. Privacy Policy Site Map Support Terms of Use SQL Server   Sign in United States (English) Brasil (Português)Česká republika (Čeština)Deutschland (Deutsch)España (Español)France (Français)Indonesia (Bahasa)Italia (Italiano)România (Română)Türkiye (Türkçe)Россия (Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย
  2. I have seen one forum which says to install a HotFix 139875_ENU_ia64_zip but it seems its only for win server 2003.
  3. x 11 Ryan Saralampi I got this error because the remote agent service for Backup Exec had stopped.
  4. No Yes home| search| account| evlog| eventreader| it admin tasks| tcp/ip ports| documents | contributors| about us Event ID/Source search Event ID: Event Source: Keyword search Example: Windows cannot
  5. My backup server is showing this event id.
  6. See example of private comment Links: ME826936, Symantec Support Page Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (2) - More links...
  7. Are you an IT Pro?
  8. The backup exec error code is E000FED1.

If the server or resource no longer exists, remove it from the selection list. Error Message Backup Job Log shows: Final error: 0xe00084f8 - The network connection to the Backup Exec Remote Agent has been lost. Email Address (Optional) Your feedback has been submitted successfully! Event 34113 Source Backup Exec I will most likely remove the agent and just do a file push and back it up that way for now.

Veritas does not guarantee the accuracy regarding the completeness of the translation. See the job log for details. You may also need to check for problems with cables, termination, or other hardware issues. Check This Out It might have with Windows 2003 but it does not with Windows 2008 R2.

Privacy statement  © 2016 Microsoft. Once a data move command has been sent across the control connection, the remote agent will initiate a data connection for the Backup Exec job engine. It creates a listener on this port, waiting for the media server to establish a control connection. Moved by Boo_MonstersIncMicrosoft contingent staff, Moderator Thursday, March 14, 2013 7:31 AM Wednesday, March 13, 2013 8:37 AM Reply | Quote Answers 0 Sign in to vote Sorry, it’s not a

The actual error detail is more relevant than the event id number. For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml

Sep 02, 2010 Backup Exec Alert: Job Failed (Server: "XXXXXXXXX") (Job: "XXXXXXX Servers - Diff") Steyning Servers - Diff -- The job failed For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml

Jul 15, 2011 Backup Exec Alert: Job Failed (Server: "SISERVERTS") (Job: "Backup 00002") Backup 00002 -- The job failed with the following error: For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml

Dec 29, 2009 Backup Exec Alert: Job Failed (Server: "SIFILE01") (Job: "Daglig Backup") Daglig Backup -- The job failed with the following error:

Additionall what version of backup exec are you running and are you fully patched up with SP's and HF's. http://www.bing.com/search?q=site%3Asymantec.com+Event+ID+34113+Backup+&qs=n&form=QBRE&pq=site%3Asymantec.com+event+id+34113+backup+&sc=0-22&sp=-1&sk= Marked as answer by Boo_MonstersIncMicrosoft contingent staff, Moderator Tuesday, March 19, 2013 8:48 AM Thursday, March 14, 2013 7:46 AM Reply | Quote Moderator 0 Sign in to vote PST files may fail to be backed up if somebody's got the file open (but you wouldn't allow PST files on your file server, would you?). I ran "file redirection" and pointed it elsewhere, and the restore was completed successfully.

This package can be found on the Microsoft web site. x 36 Anderson I had the same problem; I found the answer in Microsofts article ME826936. Veritas does not guarantee the accuracy regarding the completeness of the translation. No: The information was not helpful / Partially helpful.

Based upon your device name, I am assuming that you have a Certance LTO2 drive, which is a fairly old drive. Sorry, we couldn't post your feedback right now, please try again later. No Yes How can we make this article more helpful? For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml

Jun 13, 2014 Backup Exec Alert: Job Failed (Server: "WHP1") (Job: "Catalog 00004") Catalog 00004 -- The job failed with the following error:

Login here! For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml

Nov 09, 2010 Backup Exec Alert: Job Failed

Nov 09, 2010 Backup Exec Alert: Job Failed (Server: "") (Job: "") --