Forum Discussion

NetlinkRic's avatar
NetlinkRic
17 years ago

Error EC8F1C50

Hi,

Using Backup Exec System Recovery v7.0.1.21808 under Windows SBS 2003 R2 SP1.

In the past few days, the overnight backup task has repeatedly failed with the following error logged in the Application Event Log - ID 100:-

"Error EC8F1C50: Cannot create file backup for job: File Backup. Error E4BC0012: An interaction with the catalog's database layer failed unexpectedly: sqlite3_step--5: database is locked. Details: 0xE4BC0012 Source: Backup Exec System Recovery"

I've attempted to re-schedule the backup jobs, added the System Variable v2i_buffered = defined (which was noted on another post I found to resolve this issue) and rebooted numerous times, but the error persists.

Any advice on how I might resolve this problem gratefully received!

Regards,

Richard Tubb.
Backup and Recovery
BESR 7.x and Earlier
System Recovery
  • Richie_Rivera's avatar
    Richie_Rivera
    17 years ago
    This solution worked for me on a Server 2003 system:-
     
    Stop the Norton save and Restore service or Symantec Backup Exec service
    Go to C:\Documents and Settings\All users \ Application DATA \ Symantec \ FileBackup and DELETE the Catalog.dat file. It may be at a slightly different location depending on the OS so search for Catalog.dat if you cannot locate it. Make sure the file is related to Symantec.
    Restart the service, run your backup.
    The file can become corrupted apparantly. Support says this file does not really contain any useful information.
  • reubee's avatar
    reubee
    17 years ago
    I get this error about every second or third day using 7.0.3.24709 on Windows Vista Business, backing a laptop up to an external drive.  It is proving very frustrating to stop the service, delete catalog.data, and restart the service again.
  • accardi's avatar
    accardi
    16 years ago

    Is anyone from Symantec monitoring this forum?  The answer to what is posted here has not yet been given.  Yes, there are directions on how to remove this catalog file, but who wants to do this manually every other day?   How do you prevent it from being created in the first place?

     

    If what was said earlier in this thread is correct (file has no value and is not needed) why isn't there a patch that doesn't create it in first place?

     

    Come on Symantec.   If the answer is posted else where, please point us to it.

     

    accardi

     

  • Ensign's avatar
    Ensign
    Level 2
    16 years ago

    Has there been a resolution to this problem as I am now experiencing this problem and cannot find much more infrmation about the problem

    Many thanks

  • Ensign's avatar
    Ensign
    Level 2
    16 years ago

    Apologies. I thought I had found the solution to the problem, but after a few backups that have failed and there has been no VPN to the network it is still failing.

    The message I am receiving is

    Description: Error EC8F1C50: Cannot create file backup for job: File Backup. Error E4BC0012: An interaction with the catalog's database layer failed unexpectedly: sqlite3_step--5: database is locked.

    Details: 0xE4BC0012

     

    The backup appears to be failing at different points throughout the backup job. I have also tried deleting the catalog file after stopping the service and there is no change. Any help that can be given will be much appreciated

     

    thanks in advance

  • john_chan's avatar
    john_chan
    16 years ago

    Hi

     

    Having the same problem. Has a solution been found yet? Please let me know. Thanks!! 

  • Ensign's avatar
    Ensign
    Level 2
    16 years ago

    I am afraid that I have not found a solution yet. At present I am using NTbackup to carryout  a data file backup which is not ideal. I have changed the time of the backups and still getting the errors. There is nothing in the event logs except for the error itself.

     

    If anyone out there can shed any light, it would be gratefully received.

     

    Thanks

  • Bakantor's avatar
    Bakantor
    16 years ago
    I am having almost exactly the same problem with Ghost 12. Has anyone found a solution?