Page 1 of 1

Warning: Code expects a different schema

PostPosted: Thu Jul 23, 2015 1:50 am
by romanstatues88
Hi Everyone,

I reinstalled my Database server after a crash. I had a full backup of the database, so I just reinstalled the latest SVN via ViciBox 6.0.3. Once restored I imported the backed up database and rebooted the server.

Everything in the cluster appears to be working fine except in the System Settings menu I can see this message: "DB Schema Version: WARNING: Code expects different schema: 1420"

Is there something I can do to correct the schema / or this message?

Thank you

Re: Warning: Code expects a different schema

PostPosted: Thu Jul 23, 2015 5:52 am
by mflorell
What schema does it say you have?

When it says this, it means the web code is newer than the database schema, this can cause problems.

Re: Warning: Code expects a different schema

PostPosted: Thu Jul 23, 2015 8:35 am
by romanstatues88
Hello,

Yes it seems some of my settings are showing as all blank. It does not say what version it expects but my old installation said this:

VERSION: 2.12-482a
BUILD: 150422-1953
© 2015 ViciDial Group

My new one says this:

VERSION: 2.12-497a
BUILD: 150717-1333
© 2015 ViciDial Group


What is the solution for this? When I install ViciBox it auto pulls the latest version from SVN.

Re: Warning: Code expects a different schema

PostPosted: Thu Jul 23, 2015 8:43 am
by romanstatues88
Hi,

I seem to have found the solution. Despite going from 2.12 to 2.12 the schema seemed to change. I ran the database upgrade script in the extras folder (upgrade 2.12) and now it seems nice and working.

Thank you

Re: Warning: Code expects a different schema

PostPosted: Thu Jul 23, 2015 10:37 am
by mflorell
That is the solution! Thanks for the postback :)

Re: Warning: Code expects a different schema

PostPosted: Wed Feb 17, 2016 12:14 pm
by iboam
what is the solution for that ?? im on the same boat ...

Re: Warning: Code expects a different schema

PostPosted: Thu Aug 09, 2018 1:38 am
by hashtagjet
romanstatues88 wrote:Hi,

I seem to have found the solution. Despite going from 2.12 to 2.12 the schema seemed to change. I ran the database upgrade script in the extras folder (upgrade 2.12) and now it seems nice and working.

Thank you

Hi, Would you mind sharing where is this database upgrade script and extra folder is? I currently have the same issue.

Re: Warning: Code expects a different schema

PostPosted: Thu Aug 09, 2018 8:19 am
by mflorell
It's in the "extras" directory, this is mentioned in the UPGRADE document.

Re: Warning: Code expects a different schema

PostPosted: Wed Aug 26, 2020 11:22 pm
by dhijrwn
I have this alert now, I only updated my database server, i tried to login and make a call it still working, Is there a negative effect?

old svn
Version: 2.14b0.5
SVN Version: 3187
DB Schema Version: 1584
DB Schema Update Date: 2020-01-22 02:27:24

New svn
Version: 2.14b0.5
SVN Version: 3284
DB Schema Version: 1604 WARNING: Code expects different schema: 1584
DB Schema Update Date: 2020-08-26 20:03:28

----------------
my two vicidial server has different svn
Server dialer1 xx.xx.xx.xx Y 23 - 1% 0 3% 2020-08-26 21:20:15 3187
Server dialer2 xx.xx.xx.xx Y 3 - 1% 0 1% 2020-08-26 21:20:15 3187

---------------
Edited:
Okay, i took the risk, I updated all the server on clusters except the archive server and the error was gone, And tried to dial and login, still works. What should I do or test if everything was working after an upgrade??

Re: Warning: Code expects a different schema

PostPosted: Thu Aug 27, 2020 8:07 am
by mflorell
Everything should be just fine after an upgrade, although I would recommend forcing a conf file update on each of your servers to make sure the auto-generated configuration files are up to date(Admin -> Servers -> Modify Server -> Rebuild Conf Files)

Re: Warning: Code expects a different schema

PostPosted: Thu Aug 27, 2020 9:38 am
by dhijrwn
mflorell wrote:Everything should be just fine after an upgrade, although I would recommend forcing a conf file update on each of your servers to make sure the auto-generated configuration files are up to date(Admin -> Servers -> Modify Server -> Rebuild Conf Files)


Already done. Thank you Matt :D