Join the community of 500,000 technology professionals and ask your questions. One of my servers is having the exact same 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? Please stop posting for the sake of posting...you 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 http://antonydupont.com/event-id/event-id-34113-virus.html
Weitere Informationen finden Sie unter dem folgenden Link: http://entced.symantec.com/entt?product=BE&module=eng-event&error=V-379-34113&build=retail&version=14.1.1786.1093&language=DE&os=Windows_V-6.2.9200_SP-0.0_PL-0x2_SU-0x110_PT-0x3Apr 09, 2015 Comments Pure Capsaicin Jul 16, 2009 Justin.Davison Consulting, 251-500 Employees In the event that an agent is regularly failing Ensure that there are no version mismatches between server version and SP and agent version and SP. Stats Reported 7 years ago 6 Comments 24,937 Views Others from Backup Exec 57755 33152 33808 33919 58068 57476 57860 34114 See More IT's easier with help Join millions of IT
Let me explain how my duplicates are set up. See the job log for details. Login. Symantec Backup Exec 2014 Event Id 34113 The actual error detail is more relevant than the event id number.
Are you an IT Pro? Event Id 34113 Backup Exec 2015 I actually found the solution to my issue. Add your comments on this Windows Event! http://www.eventid.net/display-eventid-34113-source-Backup%20Exec-eventno-10269-phase-1.htm For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtmlApr 10, 2013 Backup Exec Alert: Job Failed (Server: "NOV-BACKUP") (Job: "DAILY Backup NOVMAIL (exchange only)") DAILY Backup NOVMAIL (exchange only) -- The
I hope this helps your issue! V-379-34113 I think the backup exec agent crashed, causing the "loss of communication" that the event id is referring to. Please search for event id 34113 from Backup Exec and select from the list the event that matches the event description. Review the resource credentials for the job, and then run the job again.
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. http://www.symantec.com/connect/forums/job-failed-eventid-34113 Hope you’ll enjoy it and will choose the one as required by you. Event Id 34113 Backup Exec 15 Get 1:1 Help Now Advertise Here Enjoyed your answer? Event Id 34113 Backup Exec 2010 R3 Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password?
Event ID: 34113 Source: Backup Exec Source: Backup Exec Type: Error Description:Backup Exec Alert: Job Failed. (Server:
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 V-79-57344-65233 x 3 EventID.Net According to Symantec, this can occur if there are one or more servers selected in the backup job which no longer exist on the network. For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtmlSep 02, 2010 Backup Exec Alert: Job Failed (Server: "XXXXXXXXX") (Job: "XXXXXXX Servers - Diff") Steyning Servers - Diff -- The job failed
Your post refers to some other problem affecting BE 12.5...the OP has BE 2010!!!! I have been fighting this on since I had to manually install the agent as the remote install continued to fail. Rebooting often resolves VSS Application Writer failure. 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"
read more... Reformat each drive and partition it NTFS. 2. Email: Name / Alias: Hide Name Solution Your solution: * Additional Links Name: URL:
Recycle all backup exec services and try to perform backup operation.
The reason for the backup job to fail is that the 'Backup Exec Remote Agent for Windows Servers' service running