Forum Discussion

DanielRibeiroBR's avatar
DanielRibeiroBR
Level 3
10 years ago
Solved

Error: 207: Database Exception

Good morning,
I need help!
Where I go edit a job, this error appear:

 

BEMSDK Method 'CBemPolicy.Update''

BEMSDK Failure Code: FFFFFFFF

Error: 207: Database Exception 0xcf, Source: Microsoft OLE DB Provider for SQL Server, result: 0x80040e14, Invalid column name 'ArchiveScriptID'.

 

I ran the database repair, but did not work!

error.JPG

 

 

Backing Up
Backup and Recovery
Backup Exec
Configuring
Integration
Troubleshooting
Windows Server (2003-2008)
  • VJware's avatar
    VJware
    10 years ago

    You can check the size of the BEDB in \Program Files\Symantec\Backup Exec\Data directory. It should be less than 4GB.

    Database Maintenance is enabled by default to run daily at 4AM. The schedule and other settings related to Database Maintenance can be configured from -

    BE 2010 & earlier: Tools - Options - Database Maintenance

    BE 2012 & above - BE button - Configuration & Settings - Backup Exec Settings

    Do not keep Job History & Alerts for extended periods of time. Default is usually fine. Choose the option delete aged data to periodically purge these records from the BEDB and thereby preventing the BEDB from growing large.

     

  • CraigV's avatar
    CraigV
    Moderator
    10 years ago

    ...have you tried to run a repair of the actual Backup Exec installation?

    Thanks!

  • VJware's avatar
    VJware
    Level 6
    10 years ago

    Run a repair install of .NET as well.

    What is the size of BEDB under the Data folder ?

    Lastly, are you able to create a new backup job with the new settings instead of editing it ?

     


     

  • DanielRibeiroBR's avatar
    DanielRibeiroBR
    Level 3
    10 years ago

    .NET it is installed.

    The size of the Data folder is 10GB.


    No! I cannot create a new backup too.

  • DanielRibeiroBR's avatar
    DanielRibeiroBR
    Level 3
    10 years ago

    CreigV,

    Is possible copy Backup Exec configuration (jobs, reports, media sets, etc) and import in a new installation of BE with a new Database?

  • CraigV's avatar
    CraigV
    Moderator
    10 years ago

    You can do so. Stop the BE services and grab copies of the Data/Catalogs folders and make sure all the files are there. Most important of all being bedb.bak!

    Once done, open up BEutility.exe and choose the option to Dump Database and Reload from Base. This loads a blank DB for Backup Exec.

    You can then check if you're getting the same error.

    Thanks!

  • DanielRibeiroBR's avatar
    DanielRibeiroBR
    Level 3
    10 years ago

    I've done this!

    After choose the option to Dump Database and Reload from Base, this problem did not show up again.

    Is possible export the BE configuration and import after performing the above procedure?

    I do not want use the same database.

  • pkh's avatar
    pkh
    Moderator
    10 years ago
    No. What you have done is to start from an empty database
  • VJware's avatar
    VJware
    Level 6
    10 years ago

    The above error occurred since the size of the BEDB crossed the 4GB limit.

    Couple of options:

    1) Reload from a blank DB. You'll have to reconfigure everything.

    2) Shrink the existing DB, however existing settings will be maintained. This involves running sql queries to remove unwanted data from the DB and shrinking it as well.