Highlighted

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

 

 

1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

You can check the size of the

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.

 

View solution in original post

20 Replies
Highlighted

...have you tried to run a

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

Thanks!

Highlighted

Hello CraigV, Yes! I run a

Hello CraigV,

 

Yes! I run a repair of the actual BE, but did not work.

Highlighted

Run a repair install of .NET

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 ?

 


 

Highlighted

.NET it is installed. The

.NET it is installed.

The size of the Data folder is 10GB.


No! I cannot create a new backup too.

Highlighted

Daniel, Follow the TN below

Daniel,

 

Follow the TN below to do a comprehensive repair of the BEDB:

https://support.symantec.com/en_US/article.TECH67239.html

Is Backup Exec also fully patched?

Thanks!

Highlighted

CreigV, Is possible copy

CreigV,

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

Highlighted

You can do so. Stop the BE

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!

Highlighted

I've done this! After choose

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.

Highlighted

No. What you have done is to

No. What you have done is to start from an empty database
Highlighted

The above error occurred

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.

Highlighted

4GB? O.o See the image.

4GB? O.o

 

See the image.

 

database_1.JPG

Highlighted

VJware would be referring to

VJware would be referring to the original DB that has been giving you issues.

No idea why you can't export settings from the BEDB and import into an new one...but you have the old Data/Catalogs folders, and if you want to ensure this DB is free of any corruption the old one had, then you'd recatalog your media. Any previous jobs do need to be setup again as well.

Thanks!

Highlighted

Hello CraigV, I create a new

Hello CraigV,

 

I create a new database.

 

Is possible associate a partition with media set or only possible associate media sets with medias?

Highlighted

Media sets can be associated

Media sets can be associated only with the actual medias and not partitions. However, when you specify a backup job, you can specifcy the partition and the media set and the tapes used will be then associated with that media set.

Highlighted

Ah, ok. Thanks. I'm

Ah, ok. Thanks.

I'm configuring all backup exec again! Jobs, Reports, etc.

Got any tips?

Highlighted

I created a new database and

I created a new database and set up BE again.

With the process of configuring BE, I solved other problems that were happening, such as:

- After restarting the server could not be logged in the console only after restarting services and change the logon account.

Thanks for help.

Highlighted

..I think this proves there

..I think this proves there was corruption in your previous BEDB. Glad it is sorted out.

Thanks!

Highlighted

Most of the issues occurred

Most of the issues occurred since your original BEDB grew more than 4GB. Since you used a blank, new DB, the issue will not occur. However, this may not prevent from the new BEDB growing in size in the future.

Do ensure BEDB maintenance runs daily and do not keep job history /alerts for a very long period of time. Keep clearing them up.
 

Highlighted

How can I see the size of my

How can I see the size of my database and perform proper maintenance?