Welcome to the LimeSurvey Community Forum

Ask the community, share ideas, and connect with other LimeSurvey users!

Can't upgrade further than LimeSurvey-6.15.3

More
1 month 21 hours ago - 1 month 45 minutes ago #271154 by MancombSeepgood
LimeSurvey version: 6.15.3
Own server or LimeSurvey Cloud: Own server
Survey theme/template: fruity_twentythree
DB: Postgres 15.13

==================

Hi,
I am in the process of upgrading from an ancient 3.28.5+220405 version to the latest release. It is working quite well up until 6.15.3:
I am able to do arbitrary intermediate upgrades or just jump straight to 6.15.3.
But I cannot upgrade to 6.15.4 or 6.15.5. This is the error message that I get:

CDbExceptionCDbCommand konnte das SQL-Statement nicht ausführen: SQLSTATE[42703]: Undefined column: 7 FEHLER: Spalte »token« existiert nicht
LINE 1: ...5282,993188,985571,992965,994275,994942,996579,998638,token)
^. The SQL statement executed was: UPDATE "surveys" SET "access_mode"=:access_mode WHERE sid in (112745,123624,[...],998638,token,

"column 'token' does not exist"

Does anyone have an idea how to resolve this problem an upgrade to the latest release?

Thanks in advance!

edit: Sorry, I confused the version number. It is all about 6.15.x, not 6.14.x
Last edit: 1 month 45 minutes ago by MancombSeepgood.
The topic has been locked.
More
4 weeks 17 hours ago #271213 by MancombSeepgood
Solved it myself. This will never happen to anyone else. So, dear admin, feel free to remove the whole thread, if possible.

The cause was the following:

Someone – who was involved in the administration of our Limesurvey instance before me – thought, that it would be a good idea to place some tables in the same db and scheme as Limesurvey. I was going to remove those tables before upgrading the productive instance but did not had done that by now. One of those tables had the string "token" in its name, which is the string the current db update is looking for and then did not find the expected columns:
Code:
foreach (dbGetTablesLike('%token%') as $table) {

So removing this rogue table solved it.

 
The topic has been locked.
More
3 weeks 4 days ago #271230 by holch
Great that you could solve it yourself, because for sure we would have been pretty useless here, as we don't have access to your database. :-)

I don't think it is necessary to delete, because believe it or not, you are probably not the only one that might have a similar issue and people who read this, might remember that there was "something". I will close the thread though.

Help us to help you!
  • Provide your LS version and where it is installed (own server, uni/employer, SaaS hosting, etc.).
  • Always provide a LSS file (not LSQ or LSG).
Note: I answer at this forum in my spare time, I'm not a LimeSurvey GmbH employee.
The topic has been locked.
Moderators: holchtpartner

Lime-years ahead

Online-surveys for every purse and purpose