application error on update - database definition..

[eberswine]

Trying to upgrade to 3.2.1 from 3.1.xx

Any help would be great!!

Getting an application error on database:

1. error getting database definition getTableConstraintDefinition
2. - table ox_account_preference_assoc already exists in database XXX

[eberswine]

Anyone on this ?? There has got to be someone who knows what this means ???

Thanks!!

[yulman]

Hi, I have same problem (http://forum.revive-adserver.com/topic/1905-errors-upgrading-to-revive-32x/), i've been trying to find the reason that this happens but i can't find the solution.

[eberswine]

I guess we don't upgrade ?

 

[marcis]

any solution or ETA on this fix?

[eberswine]

I will try and upgrade the latest release tonight and let you know how it goes.

I am frustrated that NO ONE FROM REVIVE TEAM commented on this yet ??

 

 

[yulman]

I also reported the problem, but still I haven't found a solution, i can't upgrade to 3.2.x.

https://github.com/revive-adserver/revive-adserver/issues/603

 

[hussberlin]

Did anyone solve this problem?

I tried multiple paths from 3.0.2. and made it up to 3.1.0. Any upgrade to versions 3.2.x ended with the above mentioned error message.

I also unsuccesssfully tried 3.1.0 -> 3.2.x.

There must be a trick, right?

[Bastian]

I must confirm this error. I see no possibility to upgrade Revive to the current 3.2.3 Version. Any ideas are welcome.

[magicmulder]

Did anyone solve this problem?

I tried multiple paths from 3.0.2. and made it up to 3.1.0. Any upgrade to versions 3.2.x ended with the above mentioned error message.

I also unsuccesssfully tried 3.1.0 -> 3.2.x.

There must be a trick, right?

Did you change the default database layout in any way? We've just successfully upgraded from 3.0.2 to 3.2.3 with no installation issues. Your error message sounds like Revive is trying to install from scratch instead of updating (because it cannot successfully detect you already have Revive installed). The *_account_preference_assoc table was added in December 2007 according to version control so an update script should not try to install it as it likely predates 3.0.2.

[Bastian]

Did you change the default database layout in any way? We've just successfully upgraded from 3.0.2 to 3.2.3 with no installation issues. Your error message sounds like Revive is trying to install from scratch instead of updating (because it cannot successfully detect you already have Revive installed). The *_account_preference_assoc table was added in December 2007 according to version control so an update script should not try to install it as it likely predates 3.0.2.

no, we didn't change the layout. but we continously upgraded from an really early phpadsnew-Version (2.0.11 i think) to openx (latest official) and to revive 3.0.5 in 2014. i now try to upgrade from that version to 3.2.3. Underlying PHP-Version is latest 5.3.

[Segr]

SQL code to correct errors in the database:

ALTER TABLE `{prefix}_banners_ox_adsense` DROP INDEX `{prefix}_banners_ox_adsense_pkey`;
ALTER TABLE `{prefix}_banners_ox_adsense` ADD PRIMARY KEY (`bannerid`);

After that, the update runs without errors.

[eberswine]

Just upgraded to 3.2.4 using the "SQL code" above from @Segr and it worked like a charm!! Thanks to you!!