Environment: Windows Server 2008 (IIS), SQL Server 2012, PHP 5.3, php_pdo_sqlsrv driver

What I'm trying to do: Upgrade a DB used with Limesurvey v1.95 to v2.05.

Very similar to the issue posted earlier:
www.limesurvey.org/en/forum/installation...rade-from-192-to-200

I am getting Error 500 after 45-60 seconds of waiting for the upgrade to complete (on clicking "Click here to continue link; /index.php?r=admin/update/sa/db/continue/yes). I have "debug" set to 1 inside config.php. Earlier, the 500 error was because of memory getting exhausted (as per LS's debug message and PHP error log). I increased the memory limit to 2GB, but still the error persists. Sadly, now no error is getting logged in PHP error log.

I am absolutely clueless where to go from here. :dry:

P.S.: I started with a fresh installation of v2.05, and wizard-based installation of Limesurvey succeeded (including populating of DB). I just changed the DB connectionstring to point to an older DB version.

There is no version 1.95

So what you are saying is that you actually did not "upgrade", but make a completely new install and than changed the to another (older) database by hand???

My bad. It's 1.92+.

P.S.: I can't find an option to change the topic of this thread. Perhaps a moderator than change it from 1.95 to 1.92+? Thanks.

holch wrote: So what you are saying is that you actually did not "upgrade", but make a completely new install and than changed the to another (older) database by hand???

Yes, holch. The whole point of this exercise is to test upgrade the DB in staging environment before implementing the same on production. I don't see a difference between just upgrading the DB and upgrading both web files & DB. Unless, of course, I'm mistaken?

Thanks

I assume that during the upgrade process the database will be adapted as well (new tables, new columns, etc.).

If you first install a completely new installation including the set up of a new database, this process is not done for the old database.

I am not an expert on this, but for me it is quite logic that there might be problems involved, as you basically will skip a step.

You are also going directly from 1.92 to 2.05, with a few versions in between. I am not surprised that this won't work perfectly.

If I understood your process correctly, this is no upgrade at all.

If you want to test in a test enviroment how the upgrade would work, you would have to clone your old database and then do an upgrade on top of the old cloned installation.

Just changing the DB should be fine.

Sounds to me like it could be a simple script timeout.
Did you also try to raise max_execution_time in PHP?

c_schmitz wrote: Just changing the DB should be fine.

Sounds to me like it could be a simple script timeout.
Did you also try to raise max_execution_time in PHP?

Indeed. Although it was not because of a small max_execution_time, but because of a small activity timeout in FastCGI settings in IIS. Error 500 went away on increasing that parameter.

But now I'm faced with another error (comes after approx. 3 minutes of initiating the upgrade):
pastebin.com/cXm0PG2k

Is the only solution to try and upgrade incrementally, as suggested by holch? If so, what version should I start with first?

Thanks

This is usually caused by an incomplete earlier update try . You will need to restore the database from a clean version (you did a backup before you started this whole ordeal, didn't you?)

Aha! That seems quite possible. Yep, I have the original DB intact

I'll try and get back.

Pardon me for bumping this topic after a long while.

I changed the environment a bit (local Windows 7 / Apache / SQL Server 2012). This time, I started upgrading with v2.0, that is 1.92 (DB v156) to 2.0 (DB v164). And that almost worked! Almost. Although the upgrade script crashed at this error pastebin.com/2bAZcLLu , the DB version got changed to 164 in table.

Any idea what quick fix I can make in the file to get the upgrade to complete 100% ?

Looks like I'm pretty close to getting the DB upgraded once and for all!

Thanks