While attempting a restore or while backing up system, the error below occurs, causing a failure.
Error EBAB03E9: Internal application error memory access violated C0000005. Application tried to read memory at xxxxxxxxx.
In later versions, the error is: "Errors Exist"
This issue has no central root cause. Please attempt the appropriate solution listed below and if the issue persists please contact Symantec Technical Support for further assistance.
Method 1: Check system and application logs for VSS errors
- If VSS errors exists, first ensure the VOLUME SHADOW SERVICE is set to automatic. Click START to ensure the service starts by clicking START (it will turn off by itself).
- Test VSS by running a backup using Windows Backup \ NTBackup, which utilize VSS.
- Determine which application is causing the error(s) in the logs. Various applications may use VSS, as well as use their own VSS writers. Each application that uses VSS needs to cooperate when a VSS backup occurs. If one of the VSS writers fail during a backup, this error may occur and the respective application may need to be repaired or modified. Please contact the mftr of that software for specific instructions on how to correct this.
- Open a command prompt and type VSSADMIN LIST WRITERS. The state of each writer needs to be STABLE.
Method 2: Check for Heavy Disk fragmentation or Disk errors
Use the Windows CHKDSK utility to do a thorough scan of the volume(s). Then use the Windows defrag utility to de-fragment the volumes. If the drives are severely fragmented, run the defrag several times. If Windows cannot de-fragment the volume(s) effectively because of a fragmented MFT, or a drive that is reaching capacity, etc., use a third-party de-fragmentation utility to run a boot-time defrag.
Please refer to these links for more information regarding CHKDSK:
Method 3: Remove memory stick drives prior to running a restore
Remove any additional flash memory stick and/or USB drives that are not a part of the recovery attempt. If a flash drive is being used to provide drivers or recovery points, insert the drive at the point of adding drivers to detect hardware devices or when prompt for drivers during the retargeting stage only.
NOTE: Issue can occur during a restore using the Symantec Recovery Disk when the recovery point is stored on a USB drive with hardware or formatting issues. Error is typically seen when running the Recover My Computer Wizard and the wizard is scanning for recovery points.
Method 4: Backing up to the source drive with adequate free disk space.
Symantec Technical Support does not recommend the backup of a drive to itself; however, if the need to arise be sure that the source drive has more 20% free contiguous space available above the additional use space.
Example: A 500 GB drive, has 250GB of used space, even with compression, would not be recommended to backup to itself; however if it had only 150 GB or less of use space then temporarily backing up to itself should work.
Method 5: Error generated during a Physical to Virtual Conversion.
During conversion of a physical to virtual (P2V) and uploading to ESXi 4.0 error may occurs as below
EC8F1F48: Impossible to do conversion process 'VMware VMDK'.. Error EC8F1F45: Cannot convert image file. Error EBAB03EA: Internal Application Error: Memory Access Violation c0000005: Application tried to write memory at 00000014. Error EBAB03EA: Internal Application Error: Memory Access Violation %
1: Application tried to write memory at %
2.Issue is resolved by applying Service Pack 1 or later for BESR 2010 or Service Pack 1 for SSR 2011.
Method 6: Virtual Disk Service is stopped.
* 2010-02-16T16:10:44.4543253Z Main Thread(8996) Context: RESULT_CLASS : RESULT e0bb0186
1: Warning 80070422: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Error SME_ERROR_VSD_LOAD_FAILED (E0BB0186): Virtual Disk Service failed to load.
Warning 80070422: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
On Examining the Services , if the Virtual Disk Service has stopped do the following:
1. Start the Virtual Disk Service
2. Restart the Backup Exec System Recovery Service.
3. Run a test backup.