I should add that the title is not accurate. The upgrade does work properly and the schema is upgraded, it's just that the user will be unable to login to LimeSurvey using webserver authentication as they had previously before the upgrade.

Maybe this can be a check in the upgrade script? If webserver auth is active perform these actions?

mdekker, should be possible. Can you implement it into an existing dbversion step (as it makes no sense to create a new one)?

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=13978

@gkuchyt I gues since you already upgraded it is not possible to test but if you can, please give it a try and let us know if the fix works.

2.05+ Build 140317 released

First I really apologize for taking so long to follow up on this. I know it bothers me when customers do this on tickets I have open with them.

I was doing this in our test instance so I can attempt to repeat at will.

So when I attempted to go from 2.00+ to the latest build (2.05 build 130320) I got a stack trace during the database schema upgrade. Screenshot here http://www.uvm.edu/~gkuchyt/saa/tmp/08738_stacktrace.png

Though, attempting to re-run the upgrade process after the stack trace seems to yield a successful update.

Dont see a lot of comments on this and it would be hard to fix it the right way. Leaving the ticket for reference. Problem will die out when 2.05 is around for a longer time and there are no more 2.00 installations trying to upgrade.