I'm trying to upgrade from 1.90 to 2.05. I have followed the documentation correctly. I found this post which sort of describes my problem in that I am getting the same error message;

The column in the table in this instances is not a "duplicate". It is only in there once. So does that mean I have to delete every single column that already exists? In which case, that's not an "update" is it, that's a brand new installation.

Or am I supposed to start with a blank database and then, after, import copies of my tables back in to the database? If that's the case, the documentation should make that really clear..

If your database upgrade fails for whatever reason then you will need to restore the original database and try again. (the error from that first try is important)

Trying again on a failed database makes no sense and will get you in more and more trouble.

By "restore the original database" do you mean a fresh install of the limesurvey 1.90 database? Or a restore of my database as it was prior to my attempted upgrade?

If you mean the first then I will lose all my survey data. If you mean the second then surely I'll just have exactly the same problem, and exactly the same error, when I try again?

I meant the 2nd. Are you 100% sure you had the same problem when you tried the first time? Because from my experience usually you don't. Also activate debug mode in config.php before you try again.

Do you mean applications/config/config-sample-mysql.php? There is no config.php file from what I can see...

There is one right on time before when you get to the db update part ( it is create during the installation)

No. There really isn't. There is no config.php file anywhere in a 2.05 that I can see.

I have managed to upgrade

I am not 100% sure what the issue was but I had to delete a particular survey in order for my upgrade to work.

c_schmitz - you were right about needing to restore back to a post-upgrade database state. However, just curious... is there an upgrade planned to avoid needing to do this? The reason my upgrade was failing the second time was because . Can't there be a check done first to see if it alreadys exists? And if it does, skip?

Mike1985_2 wrote: Can't there be a check done first to see if it alreadys exists? And if it does, skip?

I think we have a bug report in devoppement part for all upgrade system.

But it's hard to rework on a very old system and don't break anything ....

Denis