Tuesday, February 26, 2008

Backup Exec 12: Error "The Backup Exec Server Service detected a schema version mismatch."

[UPDATE] The exact same can happen in BE 12.5. See this post for details. [/UPDATE]

I just tried to update our Backup Exec 11d SP1 to Backup Exec 12 and although all pre-checks were okay and the installation did also not issue any errors, BE didn't started. Checked the event log and the following events were logged:

The Backup Exec Server Service detected a schema version mismatch.


The Backup Exec Server Service did not start. An internal error (-536813108) occurred in object 1.

Oh, I really love database schema errors. According to the Symantec support website (http://seer.entsupport.symantec.com/docs/283038.htm or http://seer.entsupport.symantec.com/docs/254014.htm) you need to recreate the entire database if this error happens which means you need to recreate everything from scratch! Thanks for nothing buddy!

Using SQL Server Profiler, I was able to figure out what the problem was. BE uses two tables as schema reference: ControlInfo and Version (you can simply install the SQL Server Mngmt Studio Express and issue an "select * from …" for these two). In this case here, ControlInfo was okay (Version 12.0) but Version still had 11 for some components listed.

There are two SQL files you need to execute against your BEDB database (using Mngmt Studio Express for example):

C:\Program Files\Symantec\Backup Exec\dbupgrade11.5.sql

If there are any errors, you may ignore them.

Once this has run, run

C:\Program Files\Symantec\Backup Exec\dbupgrade11.5-viewandsp.sql

Inside this file, there might be a problem with the following command:

-- sync with bedb.sql version, 1.644

ALTER TABLE [dbo].[Alert] ADD



Simply delete these lines and the script will run to the end. Restarting Backup Exec should now show that BE does no longer throw an schema mismatch error.



  1. Thanks. You saved me.

  2. saved me to. thanks

  3. Hi,
    I am having the same problem but am using BE 10.0. The dbupgrade files are different and i cannot find dbupgrade11.5-viewandsp.sql. Any help in identifying which file would be greatly appreciated as i tried many different solutions but am still unable to resolve.
    Thanks alot

  4. This worked for me... saved my @55! Thanks!!!

  5. Your are the best

  6. Okay - I'm having same issue. Never used SQL Server Mngmt Studio Express.

    You said: BE uses two tables as schema reference: ControlInfo and Version (you can simply install the SQL Server Mngmt Studio Express and issue an "select * from …" for these two). I found the tables, but what do you mean by: issue an "select * from …" for these two.

    I am really looking forward to making this work.

    feeling SQL stupid

  7. Wow... I had to run the 12.0 sql scripts as well because I was upgrading to version 12.5 but it worked like a charm.

    Thanks a million!

  8. @Andrew: Yes, 12.5 seems to suffer from the exact same schema FAIL. See this post:


  9. I've recently upgraded the CASO from 11D to 12 sp3 without issues but the managed media servers aren't connecting with the same schema mismatch. to what servers do I do the sql fix. The caso or the servers that have the schema error? Thanks

  10. If the CASO works but all Media Servers fail, I think the Database that the Media Servers use is the one that needs the fix.

  11. FYI...worked for me in an upgrade situation from 10d to 2010...