Home > Backup Exec > Event Id 34113 Backup Exec 15

Event Id 34113 Backup Exec 15


For more information, click the following link:

Oct 15, 2009 Backup Exec Alert: Job Failed (Server: "ALBAKERCTX") (Job: "ALBAKERES Oracle Database Daily Monday") ALBAKERES Oracle Database Daily Monday -- The Your post CraigV Moderator Partner Trusted Advisor Accredited ‎10-31-2011 07:12 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content ...are x 11 Ryan Saralampi I got this error because the remote agent service for Backup Exec had stopped. About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up have a peek at these guys

Backup Exec Alert: Job Failed (Server: "SMBKUP") (Job: "USB SMDOC") USB SMDOC -- The job failed with the following error: A communications failure has occurred between the Backup Exec job engine Find out more Read the post Question has a verified solution. Let me explain how my duplicates are set up. For more information, click the following link:

Apr 28, 2011 Backup Exec Alert: Job Failed (Server: "SERVER1") (Job: "CoreConnexions Daily") CoreConnexions Daily -- The job failed with the following error:

Event Id 34113 Backup Exec 15

Clear out any old info that was left in Backup Exec from these drives by retiring any B2D files I know were on any of the drives I formatted. Sonora Jul 31, 2009 Frank400 Manufacturing Verify that the device that veritas agent is trying to backup is available on the network, i.e., powered on, machine name has not changed, etc. I found out that the service account for backup exec (v9.0) did not have write permissions to the folder it was restoring to.

For more information, click the following link:

Sep 19, 2012 Backup Exec Alert: Job Failed (Server: "BACKUP-SRV1") (Job: "File Mail and SQL Dif") File Mail and SQL Dif -- The I hope this helps your issue! For more information, click the following link:

Jun 13, 2014 Backup Exec Alert: Job Failed (Server: "WHP1") (Job: "Catalog 00004") Catalog 00004 -- 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.

Join & Ask a Question Need Help in Real-Time? Event Id 34113 Backup Exec 2010 R3 The management tools on the media server must be the same version or later as the management tools that are on the Exchange Server see Admin Guide page 1054 x 17 Rich Stringer This error could also be generated when the backup device, in this case, a tape drive, has no more available space. Final error category: Resource Errors 0 Message Author Comment by:comtekso ID: 136656922005-03-30 From the ERROR section of my Job Log: Unable to attach to C:.

Reply eXe says: May 7, 2011 at 11:11 am Thanks for your comment, as a matter of fact this error happend on a 2003 server machine in my case. This is not a required step but I have a big stickler about getting rid of info that doesn't need to be retained in the BE database. I actually found the solution to my issue. Subscribe to our monthly newsletter for tech news and trends Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource Center About Us Who We

Event Id 34113 Backup Exec 2010 R3

Help Desk » Inventory » Monitor » Community » home| search| account| evlog| eventreader| it admin tasks| tcp/ip ports| documents | contributors| about us Event ID/Source search Event ID: Please work with Symantec to solve this problem. Event Id 34113 Backup Exec 15 Make sure that it is running under the Local System account.

- If the issue is unresolved, please go to Tools, Options, Network Tab, select the "Use any available Network adapter" Symantec Backup Exec 2014 Event Id 34113 So to me, when my duplicate jobs are running, they shouldn't even be communicating with the server that was backed up because it is only copying what was backed up already

For more information, click the following link:

Dec 29, 2009 Backup Exec Alert: Job Failed (Server: "SIFILE01") (Job: "Daglig Backup") Daglig Backup -- The job failed with the following error: Thanks to John for the hint. As always, make sure your media server is fully patched with available patches, and that these have been installed on any remote servers you might have. Keeping an eye on these servers is a tedious, time-consuming process. V-79-57344-65233

I know from experience that this problem is a major headache so when I say I feel your pain; I really do! Login Join Community Windows Events Backup Exec Ask Question Answer Questions My Profile ShortcutsDiscussion GroupsFeature RequestsHelp and SupportHow-tosIT Service ProvidersMy QuestionsApp CenterRatings and ReviewsRecent ActivityRecent PostsScript CenterSpiceListsSpiceworks BlogVendor PagesWindows Events Event You should be able to find it; if not, check Go to Solution 3 2 Participants comtekso(3 comments) gpriceee LVL 13 Storage4 Storage Software3 4 Comments Message Author Comment by:comtekso check my blog Connect with top rated Experts 11 Experts available now in Live!

If all or most of them are stop… Storage Software Disaster Recovery Windows Server 2008 Advertise Here 596 members asked questions and received personalized solutions in the past 7 days. Thanks Dan. Ghost Chili Sep 2, 2010 Jim Kubicek It Service Provider, 1-50 Employees This is happening here because the backup server is having trouble finding the agent share.

Login By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. © Copyright 2006-2016 Spiceworks Inc.

Job Log tab --> expand all Scroll down until you find the point at which the error occured. This package can be found on the Microsoft web site. See the job log for details. x 11 Edward Patel I was trying to do a restore, but the remote agent would die during the restore.

I think the backup exec agent crashed, causing the "loss of communication" that the event id is referring to. Join our community for more solutions or to ask questions. If ten years ago it was still common to see an entire company using just one server, these days that's no longer the case. news The database was not found, however.

Please stop posting for the sake of added nothing to this discussion! 0 Kudos Reply hi ET, Check the link below CraigV Moderator Partner Trusted Advisor Accredited ‎10-31-2011 07:16 I actually found the solution to my issue. Custom search for *****: Google - Bing - Microsoft - Yahoo Feedback: Send comments or solutions - Notify me when updated Printer friendly Subscribe Subscribe to EventID.Net now!Already a subscriber? The main reason is usually cost.

For more information, click the following link: ----------------------------------------------------------------------- A VSS error has occurred when backing up Exchange 2003/2007 Databases. Yes: My problem was resolved. Unable to attach to \\2000SERVER\System?State. 0 LVL 13 Overall: Level 13 Storage 4 Storage Software 3 Message Accepted Solution by:gpriceee gpriceee earned 500 total points ID: 136658312005-03-30 In the Job Make sure that all selected resources exist and are online, and then try again.

Privacy statement  © 2016 Microsoft. I've seen this when in the Job Setup window (edit the job) the selection view is graphical; change it to text and ensure that all drives in the list actually exist. Not a member? All rights reserved.

Ensure that there are no version mismatches between server version and SP and agent version and SP. 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 WMI, System, and IIS Config. Covered by US Patent.

English: Request a translation of the event description in plain English.