Hmmm... I suppose the next logical move is to delete that variable from the table, then try again. But I suspect there is something else going on here that I'm just not thinking of. Do you have backups of the database that you can revert to? That might be worth a shot as well. It strikes me as odd that the table was missing in the first place...

Also, I'm wondering if trying to access the tokens feature in LS might tell us more about what's going on. Are you using tokens (i.e., have you initialized tokens for any of your surveys)? Perhaps you could create a dummy survey (just copy some of your existing questions/groups), then initialize tokens for it and see what happens (of course, make backups before doing anyting! ).

Sorry I can't be more specific - I just need a little more information about what's going on.

ricardo schrieb: Is it possible that the updater is looking for that table to add the "date_invited" column afterwards and thus this problems shows up if that column was already created manually?!?

Try deleting that column and run the update again.

I deleted the "date_invited" variable and ran update again...
then I got a new error message, this time "duplicate column 'date_completed'" So I also deleted that field and ran the update again...and voila! Finally I got the "database successfully updated to version 164"

I checked the database and the updater automatically added the 'date_invited' and the 'date_completed' fields automatically...as Mazi said.

Thank you all

ricardo schrieb: You're welcome!

the same error over here

ocean schrieb: a) Is that a simple statement, a question or a call for help?!?

b) If that is the same error, you might be able to solve it by carefully reading the posts above

I solved the problem on my own site
but I think that someone how want's to update to a new version also gets the error
so maybe the script must have some more checks to avoid any more errors on this

I guess that the problem doesn't exist at the latest releases, but we can have a look:

1. Can you let us know from which version you updated and which Limesurvey version and build you updated to?

2. Can you provide step-by-step instructions on how to reproduce the problem?

From: $versionnumber = "1.92+"; $dbversionnumber = 155.5; $buildnumber = '120919';
To: $config = "2.00+"; $config = 164; $config = '121213';

Mazi schrieb:
uhhhhh