EBAB00CC: Unable to continue due to lack of memory

Article:TECH54575  |  Created: 2009-01-18  |  Updated: 2014-05-22  |  Article URL http://www.symantec.com/docs/TECH54575
Article Type
Technical Solution

Product(s)

Subject

Issue



When using a System Recovery product the following error below occurs preventing the product to perform a specific task. This error has been shown to occur performing the following tasks:

  • In the process of creating a recovery point image
  • When attempting to perform a restore of a recovery point image.

Error



"EBAB00CC: Unable to continue due to lack of memory"


Cause



Since this error occurs while performing various tasks within this product please review and follow the steps listed under the specific task below. If the steps listed for the task does not remedy the issue where this error persist please contact Symantec Technical Support for assistance.


Solution



The following steps can be used sequentially or in no particular order as it differs according to the environment:

If the above steps do not resolve the issue:

  • Perform a clean boot, as per http://support.microsoft.com/kb/310353. Reboot machine and attempt to re-run backup. 
  • If backing up a compressed drive, backing up to a NAS device may cause this error. Run a test backup to a local drive, such as USB or a local disk 
  • From a command prompt, run CHKDSK X: /R /F to do a thorough scan, where X: is the volume(s) being backed up. Run the Windows Defragmentation (Defrag) utility to de-fragment the same volumes. If Windows cannot de-fragment the volume(s) effectively because of a fragmented MFT, a drive that is reaching capacity, etc., use a third-party de-fragmentation utility to run a boot-time defrag.
  • As a test, split the backup job if multiple drives exist. (Do not do this if backing up Microsoft Exchange or SQL servers if databases and logs stored on different drives.)
  • Change the backup job to Split the backup into smaller chunks using the option "Divide into smaller files to simplify archiving." Recommended for testing is 2GB.
  • Adjust the scheduled time of backup if any other backup applications run during that time, ensuring backups do not overlap. Ideally, temporarily disable any other 3rd party backup applications to rule out possible conflicts.
  • Run the SEAST log gathering utility:www.symantec.com/docs/TECH54539, and check the PARTINFO.TXT file within the *.CAB file created. Scroll through this log and look for any errors, as seen in bold in the example below. If such errors occur, use DISK MANAGEMENT to resize the partition (no more than 100mb should suffice). If this does not resolve the issue, it may be necessary to manually copy the data, remove the partition, and recreate it.

    =========================================================================================================================
Disk Geometry Information for Disk 1         Sector Count: 3,892,838,400   (1,023 Cylinders, 254 Heads, 63 Sectors/Track)
Signature: B3D3B45D
Detected Sector Size:   512
Detected Alignment:     None
.........................................................................................................................
System               Part Table LBA   # Boot     BCyl Head Sect FS      ECyl Head Sect       StartSect         NumSects
=========================================================================================================================
   On Disk Values:                0   0   0         0    0   2  EE      1023  255  63                1    4,294,967,295
   Calculated:                                      0    0   2        268401  230   4  

.........................................................................................................................
GPT Header Data:
     Signature:            EFI PART
     EFI Revision:         1.0
     Header Size:          92
     Header Checksum:      3294383838
     Primary LBA:          1
     Backup LBA:           8,187,805,695
     First Usable LBA:     34
     LastUsable LBA:       8,187,805,662
     Disk GUID:            8ca86a5e-72f2-4d4d-afcd-ef4f07a207e9
     Partition Entry LBA:  2
     Max # of Partitions:  128
     Partition Entry Size: 128
     Partition Array CRC:  2912368156

WARNING: Backup LBA is not valid in GPT header.

====================================================================================================================
Partition Information for Disk   1:               3.81 TB
Volume Path            PartitionType  Status         Size      Part Table Lba   #     Start Sector    Total Sectors
====================================================================================================================
Protective MBR         GPT Protect    Pri               2 TB                0   0                1    4,294,967,295
.........................................................................................................................................
GPT Partitions for Disk 1:        3.81 TB
 #   Partion Type/Volume GUID            Sect Index  Attribute Bits              Start Sector                  End Sector    Size
-----------------------------------------------------------------------------------------------------------------------------------------
  0  Microsoft reserved partition        
     2b74a448-0f12-47d2-acdd-15de3c291964   2 0                 0                          34                     262,177    128 MB

F:\
  1  Basic data partition                
     3a3b2bab-ad47-4dae-9cbe-938e4eb09922   2 1                 0                     262,178               8,187,803,681    3.81 TB

WARNING:  Above partition extends beyond end of disk.

 


Supplemental Materials

SourceUMI
ValueV-281-2987-204
Description

EBAB00CC: Unable to continue due to lack of memory


Legacy ID



292845


Article URL http://www.symantec.com/docs/TECH54575


Terms of use for this information are found in Legal Notices