Home
»
Discussion Forums
»
Alerts - VSA
»
Detailed list of System Recovery Event Codes!
Subscribe via RSS
Share this
Similar Posts
I Need Improper shutdown system Event id in windows xp Operating system Details
by
LegacyPoster
on
Feb 10, 2010
hard coded external ip for cd recovery?
by
LegacyPoster
on
Mar 19, 2008
"Pulled from system server" detail
by
LegacyPoster
on
May 24, 2010
Symantec System Recovery
by
rdk@waslet.be
on
Feb 19, 2014
check disk error event code 55
by
LegacyPoster
on
Jun 2, 2010
View More
Details
2
Replies
0
Subscribers
Posted
over 10 years ago
Alerts - VSA
Detailed list of System Recovery Event Codes!
Posted by
LegacyPoster
on
Apr 14, 2010 5:30 PM
After weeks of hassling Symantec support they have finally managed to get me a list they say they didn't have, it is simply a list of all the Error Codes used by Symantec System Recovery and details about them, they have following on from my query agreed to create a KB Article on their site with this information but until that happens here you go...
Oh, I will be creating Success & Failure monitoring sets from these (hopefully before the end of the week), if there is any interest in these please let me know and I will share.
EC8F0003: Virtual Volume Imaging is not available on this machine.
EC8F0007: Cannot create a Virtual Volume Image of %1.
EC8F000C: Cannot find the Virtual Volume Image driver.
E0BB001A: \"%1\" is not a valid filename.
E0BB001B: Cannot lock volume %1 because it contains the OS or has an active paging file.
E0BB0027: Cannot create volume.
E0BC000A: The saved initial state for applying changes does not match the current system state.
EA39001B: Cannot lock drive.
EA39001C: Cannot unlock drive.
EA39001D: Cannot lock a locked drive.
EA39001E: Cannot unlock an unlocked drive.
EA39001F: Cannot lock drive
EA390020: Cannot redetermine media.
EA390025: File or application is open on partition.
EA390026: Program is running from that partition.
EA390028: A hard disk is present but cannot be accessed
EA390029: Cannot write; disk is write protected.
EA39002A: Disk changed since last operation.
EA39002B: Unknown unit.
EA39002C: Drive not ready.
EA39002D: CRC error in data.
EA39002E: Seek error.
EA39002F: Unknown media type.
EA390030: Sector not found.
EA390031: Write fault.
EA390032: Read fault.
EA390033: General hard disk failure.
EA390034: DMA error.
EA390035:Lock violation.
EA390036: Network device fault.
EA390037: Specified drive is busy.
EA390038: Specified sector not in valid read or write range.
EA39003A: Unable to write to the boot sector.
EA390050: License violation.
EA390051: License violation.
EA390055: Bad Windows registry format or missing key.
EA390056: Unable to determine the BIOS drive order.
EA390057: Unable to initialize the engine.
EA390058: Unable to find correct drive.
EA390064: Partition table is bad.
EA390065: Partition not found in current list.
EA390066: Boot sector information not correct.
EA390068: No sectors in partition.
EA390069: Partition starts on wrong boundary.
EA39006A: Partition does not start with sector one. Text Notes
EA39006B: Partition begins after end of disk.
EA39006C: Partition does not end at end of cylinder.
EA39006D: Partition ends after end of disk.
EA39006E: Partition table number of sectors is inconsistant.
EA39006F: The order of entries in an epbr are out of order.
EA390070: Logical partition ends outside Extended.
EA390071: Partitions overlap.
EA390072: Start of Logical versus EPBR is not correct.
EA390073: End of Logical versus end of EPBR is not correct.
EA390074: Partition table Begin and Start inconsistant.
EA390078: The logical drive chain is incompatible.
EA390079: The first sector of the drive cannot be read.
EA39007A: A bad sector exists in the current or new partition area.
EA390082: Boot sector does not have 0xAA55 ending signature.
EA390083: Boot sector does not have valid jump code.
EA390084: Boot sector does not have valid OEM name.
EA390085: Boot sector does not have valid file system type.
EA390086: Boot sector does not have valid FAT/FAT32 signature.
EA390087: Boot sector does not have valid Ext2 signature.
EA390088: Boot sector does not have valid Linux Swap label.
EA39012D: The file could not be opened.
EA39012E: The file could not be opened or created.
EA39012F: The file could not be closed.
EA390132: The file could not be written to successfully.
EA390134: Cannot seek to the file location specified.
EA390135 3- Unable to get the current read/write position of the specified file handle.
EA3901F7: Path was not found.
EA3901F8: File not found.
EA3901F9: Path was invalid.
EA3901FD: A bad sector was detected in the current or new FS area.
EA3901FE: The version of the file system is not supported.
EA390273: Drive geometry obtained from the native OS does not match that seen from boot mode.
EA390640: Invalid NTFS boot sector.
EA390641: Invalid NTFS partition information.
EA390642:File table backup mismatch.
EA390643: System files not all in root file %1 %2.
EA390644: File's parent does not contain the file, File %1 %2.
EA390645: File's parent not directory, File %1 %2.
EA390646: System file records not all marked used, File %1.
EA390647: File record marked free, File %1.
EA390648: File record marked used, File %1.
EA390649: Lost clusters, Clusters %1: %2.
EA39073C: File entered is not a valid image file. Enter another filename.
EA390FA0: Block not found.
EA390FA1: Block table full.
EA390FA2: Duplicate block.
EA390FA3: Cluster not found.
EA390FA4: Entry not added.
E002000D: Device %1 failure querying drive geometry. The media type is unknown or not supported.
E002000E: Could not locate a partition information structure for volume %1.
E0520000: Device %1 dynamic disk error. This is a generic wrapper for lower level results.
E0520001: Device %1 is not a dynamic disk. The device does not have the format of a dynamic disk.
E0520002: LDM error with device %1. There is an engine internal error.
E0520003: Device %1 dynamic disk database has an invalid format. There is a corrupted LDM database.
E0520005: Device %1 dynamic disk database is incompatible with the group. The memory representation of the database is not consistent with this device.
E0520006: Device %1 dynamic disk database is full. The LDM database is full.
E0060003: Block %1 is out of range.
E0060004: Bit %1 is out of range.
E0060005: Bad pointer in block %1.
E0060006: Integrity Check found an invalid marker in block %1.
E0060007: Integrity check found an invalid run count in block %1.
E0060008: Integrity check found runs not sorted in block %1.
E0060009: Integrity check found runs overlap in block %1.
E006000A: Integrity check found %1 blocks instead of %2.
E006000B: Integrity check found invalid number of bits in block %1.
E006000C: Bitmap was not opened before attempting to read or write.
E006000D: Bitmap was previously open but not closed.
E006000E: Bitmap was opened using the wrong read/write mode.
E006000F: Attempting to read from an empty bitmap.
E0060010: Attempting to expand a bitmap located in a pre-defined buffer.
E0060011: Attempting to import a bitmap with an invalid signature.
60070003: Using '%1', the native locale for the OS.
60070004: The '%1' language cannot display in a console window.
60070005: The '%1' language is not supported.
60070006: The '%1' region is not supported.
E0070007: No locale could be loaded. A generic Posix locale will be used.
E0070008: The strings in '%1' could not be loaded. The file may be damaged or inaccessible.
E9290005: RTC file is corrupt. RTC file is not valid.
E9290006: RTC file is missing. RTC file is not found.
E929000D: This functionality is disabled because the application license has expired.
EC950003: The backup image file '%1' cannot be opened.
EC950005: The backup image file is not valid.
EC950006: The destination is not valid.
EC950009: The backup image file could not be restored.
EC950013: All V2i backup image spanned files are not available.
EC95001A: Cannot work with an unknown disk.
EC95001B: The disk signature cannot be written.
EC950022: Only four primary partitions can exist on one disk.
EA9D0020: Platform error calling %1.
A4C70005: Partition at offset %1 of disk %2 could not be added to the disk configuration.
A4C70006: Partition at offset %1 of disk %2 could not be deleted from the disk configuration.
A4C70007: Partition at offset %1 of disk %2 could not be modified.
A4C70008: Disk %1 does not contain NTFT configuration data at sector 2.
A4C7000B: %1 error: Unable to write the NTFT configuration to sector 2 on Disk %2.
A4C70011: The Disk Signature on disk %1 cannot be zero
A4C70018: Partition %1 on disk %2 could not be found.
A4C7001A: An unknown error occurred parsing the Disk\\Information key
ED800000: Missing span file %1. File should exist, because %2 exists
E7AA0001: Initialization of Windows Disk Manager services failed
Enjoy!
Legacy Forum Name: Detailed list of System Recovery Event Codes!,
Legacy Posted By Username: stu_u2k
You have posted to a forum that requires a moderator to approve posts before they are publicly available.
Posted by
LegacyPoster
on
Apr 14, 2010 6:17 PM
Seems the list was not as comprehensive as it should have been, I just compared it to my existing list and there are items missing, I have gone back to Symantec for a response, will update when I hear back.
My Previous List...
===========================
System Recovery FAIL Codes:
===========================
E7D10026:
6C8F1C4F:
EBAB03F1:
EC8F17E5:
EC8F17D8:
6C8F042C:
EC8F17B9:
E7D10041:
EC8F1796:
EC8F17D4:
EC8F042E:
6C8F17E7:
6C8F1C2F:
EC8F17B7:
E7640001:
System Recovery SUCCESS Codes:
==============================
6C8F1F89:
6C8F1F8A:
6C8F1F7B:
6C8F1F7C:
6C8F1F79:
6C8F1F7D:
6C8F1C55:
6C8F1F7A:
6C8F1C69:
6C8F1F80:
6C8F1F7E:
6C8F1C56:
System Recovery Started Codes:
==============================
6C8F0427:
6C8F1F63:
6C8F1F65:
6C8F1F64:
Legacy Forum Name: Event Sets,
Legacy Posted By Username: stu_u2k
You have posted to a forum that requires a moderator to approve posts before they are publicly available.
Posted by
LegacyPoster
on
Apr 18, 2010 10:21 PM
Will subscribe to this thread for updates.
Legacy Forum Name: Event Sets,
Legacy Posted By Username: shulmanclark
You have posted to a forum that requires a moderator to approve posts before they are publicly available.