Backup Exec System Recovery (BESR) recovery point browser and general error messages

Article:TECH56150  |  Created: 2007-01-13  |  Updated: 2013-10-22  |  Article URL http://www.symantec.com/docs/TECH56150
Article Type
Technical Solution

Product(s)

Environment

Issue



Backup Exec System Recovery (BESR) recovery point browser and general error messages

Solution




Recovery Point Browser error messages
The following table lists the Recovery Point Browser error messages and their possible solutions:
 
ErrorDescription
Cannot initialize COM library Symantec Backup Exec System Recovery was unable to initialize the COM subsystem. This error can be caused by insufficient resources or corrupt DLLs. Restart the system, and try to free system resources.
Cannot allocate Symantec Backup Exec System Recovery mount manager instance Symantec Backup Exec System Recovery was unable to allocate resources for the Symantec mount manager. This error is usually reported when Backup Exec System Recovery is partially installed or some of its COM objects are missing or incorrectly registered. To correct this condition, reinstall Symantec Backup Exec System Recovery.
Cannot retrieve drive information The Symantec mount manager did not recognize the drive as a mounted recovery point. This error is most commonly reported when another process is attempting to unmount the drive. The error may also occur if the drive is corrupt. Close all disk management programs, and try again to unmount the drive. If the problem persists, restart the computer to allow Windows to re-enumerate all mounted drives.
Cannot dismount drive. Please verify the drive is not locked by another process The Symantec mount manager was unable to unmount the drive. To resolve the error, make sure there are no open files on the drive and that the drive is not locked by another application.

General error messages
Below is the list of the general error messages that may be encountered while using BESR and the possible solutions:
EC8F17B7
"Cannot create recovery points for job: Recovery point of drive."
E0710007
"Cannot create a virtual volume image." If the error continues, contact technical support. The additional log files may also be required, for example, .txt files from the Agent folder.
E0B000C
This error might also display one of the following:
  • Object Basic Disk SME~Computer~BgM896453 was in the saved state but is not in the current state.
  • Object MediaCommon:Sme~computer ~Pd1~M896453 was in the saved state but is not in the state.
These error messages could be caused by changes to the serial number. It could also be caused by the drive information reporting differently.
If the restore was initially set up in Windows, but the computer was restarted in the recovery environment, try going through the Recover My Computer Wizard in the recovery environment. There could be a change in the drive information in Windows 2000 compared to the recovery environment.
If the error continues to occur during the use of the Recover My Computer Wizard from the recovery environment, contact Symantec Technical Support.
E0BB001B
"Cannot lock volume "\\volume_name" because it contains the operating system or it has an active paging file."
Symantec Backup Exec System Recovery can back up operating system partitions and other partitions that contain page files. This error is usually caused by a driver conflict with another application that might have control of the partition.
Check for other applications that might have a lock on the drive and temporarily turn off any suspected conflicting drivers, and then run Symantec Backup Exec System Recovery again to create the recovery point.
Many times, the error is seen on the first backup following installation if the computer was not rebooted before the backup began. It is necessary to reboot the machine following installation so the drivers can initialize properly.
E0BB0097
"Volume "\\Volume8f40f-6fc6f-11d9-505055403030\"cannot be locked"
If the error occurs when attempting to restore a drive (partition), delete the existing drive first.
If the error occurs when attempting to back up the drive, contact Symantec Technical Support.
E0BC000A
The saved initial state for applying changes does not match the current system state.
Try restoring by using Symantec Recovery Disk.
  • This error can also be caused by fibre channel devices.
Disconnect the devices to confirm whether they are causing the problem.
  • This error can also be caused by Emulex controllers. Occasionally, there are phantom volumes or partition table errors that can cause this error.
E7D1001F
This error can occur if correct rights are not there. However, it could also be caused by slow bandwidth, dropped packets, or other network-related issues.
E926001F
Run the Windows CHKDSK utility on the source drive before copying or creating a recovery point. If the utility cannot be run, and the validity of the recovery point is confirmed, bypass the error by deselecting the option to Check file system after restore. After the recovery completes, run CHKDSK on the drive to eliminate any file system errors.
EA390019
Insufficient permissions.
For example: System A is running Symantec Backup Exec System Recovery. System B is running the Symantec Backup Exec System Recovery Agent service, and system C contains the drive in which the recovery points are stored.
The user who logs onto system A must have at least local administrator rights on system B to create a recovery point. The user also needs rights to the location in which the recovery point is being stored and needs domain user rights to save to the network.
In a domain, created one user with Domain Admin and Administrator rights. Use this account to log in to system A. On system B, the Symantec Backup Exec System Recovery Agent service should be logging in with the same account. Determining when this error occurs can help identify where permissions are not set correctly.
In a workgroup, create duplicate accounts (using the same user name and password) on each computer. Make sure that each account has local administrator rights. Log on with this account when managing other agents in the workgroup.
EA39070A
This error may be encountered while using Veritas Drive Letter Access (DLA). It indicates that the internal structure of the v2i file is invalid or unsupported.
Despite this error, the recovery point on the disk is still valid. To correct this issue, either use a regular CD or DVD drive to read the recovery point, or remove Veritas DLA from the computer so that the CD can be properly read.
This error can also occur for one of the following reasons:
  • The recovery point is damaged or corrupted.
Damage can occur when a recovery point is created over a network and there is significant packet loss during the creation of the recovery point. Symantec recommends to verify the recovery points after they are created to ensure their integrity.
Create a new recovery point to a different location, or create a new recovery point with a different file name to the same location.
  • The recovery point is fine, but there may be a conflict with spyware detection software (such as Pest Control or Spybot) that causes the recovery point to become corrupt or appear to be corrupted.
While using Backup Exec System Recovery or the Recovery Point Browser, make sure that all spyware detection software are turned off.
  • A recovery point is copied from one FireWire drive to another FireWire drive while connected to a FireWire expansion card that uses a Via chipset (such as the Kouwell card).
To work around this issue, replace Via-based FireWire expansion card with a card that uses a non-Via chipset (such as the Adaptec 4300 Fireconnect, which uses a TI chipset).
EA390712
This error is usually caused by insufficient rights to the Symantec Backup Exec System Recovery Agent service. A user must have administrator and domain administrator rights on the sub-share folder. Check that the Symantec Backup Exec System Recovery Agent services Log On information is correct.
EBAB001A
Cannot read data from drive. An unknown exception has occurred.
This error is reported while attempting to save a recovery point to a SAN drive or to removable media, or restoring a recovery point from the recovery environment.
If saving a recovery point to a SAN drive, check Disk Management for missing or old volumes. If saving a recovery point to removable media, insert disks into the drive. If that does not work, disconnect the removable media drive and remove any attached USB devices.
If using Samba shares, make sure that the basic rights are available on Samba. If saving the recovery point to NAS, check the operating system that is installed. There could be an issue with Linux or with proprietary operating system NAS devices.
EC8A0001
This error is caused by updated firmware on QLogic drives conflicting with the QLogic driver on the Symantec Backup Exec System Recovery CD. In other cases, it could also be caused by any SCSI conflict with particular drivers on the Symantec Backup Exec System Recovery CD.
Try loading the driver manually.
If the error continues, do the following:
  • Run the recovery environment support utilities Display SME Disk Information.
  • View Partition Information.
  • Obtain the system information.
  • Contact technical support.
The additional log files may also be required.
EC8F0007
The error is usually caused by a driver conflict with another application that has control of the drive. Check for other applications that might have a lock on the drive. Temporarily turn off any suspected conflicting drivers, and run Symantec Backup Exec System Recovery again.
EC8F000C
Check that the driver is present and that the Symantec Backup Exec System Recovery Agent service is started.
EC950001
This error occurs when the driver for the storage controller does not load in Symantec Recovery Disk. Restart the computer by using Symantec Recovery Disk and press F6 to load the necessary drivers.
Catastrophic error
This error might be caused by a conflict with another program.
Contact Symantec Technical Support.
WinBOM error when booting from recovery environment
This error is an issue with the network interface card (NIC) driver not loading. If the recovery point to be restored is located on the network, first try a different NIC card. If that is unsuccessful, send the drivers and a system information file to Symantec Technical Support.
The month and year are switched on some international computers
This error is an issue with some international servers.
For more information, go to the following URL and search on the generated error code:

Send the .pqh files to Symantec Technical Support.

Supplemental Materials

SourceUMI
ValueV-281-188-10
DescriptionError E0BC000A: The saved initial state for applying changes does not match the current system state.

SourceError Code
ValueEBAB001A
DescriptionCannot read data from drive. An unknown exception has occurred

SourceUMI
ValueV-281-2987-26
DescriptionCannot read data from drive. An unknown exception has occurred.

SourceError Code
ValueEC8F17B7
DescriptionCannot create recovery points for job: Recovery point of drive.

SourceError Code
ValueE0BB001B
DescriptionCannot lock volume

SourceUMI
ValueV-281-187-27
DescriptionCannot lock volume

SourceError Code
ValueE0BB0097
DescriptionVolume "\\\"cannot be locked"

SourceUMI
ValueV-281-187-151
DescriptionVolume "\\Volume{8f40f-6fc6f-11d9-505055403030}\"cannot be locked"

SourceError Code
ValueE0BC000A
DescriptionThe saved initial state for applying changes does not match the current system state

SourceError Code
ValueEC950001
DescriptionRestore Engine cannot be initialized

SourceUMI
ValueV-281-3221-1
Descriptionrestore engine cannot be initialized


Legacy ID



294949


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


Terms of use for this information are found in Legal Notices