Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Backups of volume D fail with 'Internal Application Error: Memory Access Violation c0000005'.

Created: 30 Aug 2012 • Updated: 12 Feb 2013 | 2 comments
Chris Riley's picture
1
Vote
Login to vote
Me Too!I have the same issue
Product(s): Symantec System Recovery (formerly Backup Exec System Recovery) - BESR 2010, Symantec System Recovery (formerly Backup Exec System Recovery)
Severity: Non-data threatening / major functionality
Status: Private fix ready
Tech Note: More Information

Problem

Backups of volume D fail with the error listed below when using Backup Exec System Recovery (BESR) 2010.

Backups of other volumes (i.e. C) are successful.

Error

High Priority Error: Error EC8F17B7: Cannot create recovery points for job: Drive Backup of Store (D:\).
Error EC8F03EA: Cannot create a virtual volume image of the selected drive.
Error EBAB03E9: Internal Application Error: Memory Access Violation c0000005:
Application tried to read memory at 00000000. 0xEBAB03E9 (Backup Exec System

Environment

Windows 2008 R2

Solution

Currently there is no workaround to this issue.

Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
 
This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns.  For information on how to contact Symantec Sales, please see http://www.symantec.com

Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.

Comments 2 CommentsJump to latest comment

Chris Riley's picture

The issue is still under investigation (I'm currently waiting for an update from our engineering team).

Do you have a support case open for your issue?

0
Login to vote