View Issue Details

This bug affects 1 person(s).
 2
IDProjectCategoryView StatusLast Update
07216Bug reportsComfortUpdatepublic2013-01-21 19:29
ReporterNanotubes Assigned Toc_schmitz  
PriorityimmediateSeveritycrash 
Status closedResolutionnot fixable 
Product Version2.00+ 
Summary07216: Total system crash after comfort upadte from 1.92 to 2.00
Description

I comofrt-updated from 1.92 to 2.00 build 12something today and it worked nicely. Then i did the follow-up update to build 13something and it worked untill step 4. The page took ages to load and then showed me a long list of deleted and changed files, an error about something and a message that everything worked. Stupid as i am i didn't copy the list. Anyway i finished the upadte and from now then on whatever i do i get this message: Internal Server Error
InstallerController cannot find the requested view "/installer/welcome_view".

An internal error occurred while the Web server was processing your request. Please contact the webmaster to report this problem.

Thank you.

oddly,if i just go to the frontend(limesurvey/index.php) or backend (limesurvey/admin) it automatically sends me to limesurvey/index.php?r=installer/welcome

With filezilla i found the DB backups in the tmp folder, can i use this to restore everything?
I just want to reproduce the last working state it was in and not lose any data i collected so far.

Steps To Reproduce

use comfort upadte?

TagsNo tags attached.
Bug heat2
Complete LimeSurvey version number (& build)120808
I will donate to the project if issue is resolvedYes
BrowserDone in Firefox, but Error message in IE and Opera displayed too.
Database type & versionMySQL 5.0
Server OS (if known)Linux i think
Webserver software & version (if known)1&1 Dual Unlimited Webhosting
PHP Version5.4

Users monitoring this issue

There are no users monitoring this issue.

Activities

c_schmitz

c_schmitz

2013-01-21 19:29

administrator   ~23732

There is no ComfortUpdate possible from 1.92 to 2.0.

If you managed to go beyond step 3 it means that for some reason the update for the updater (which runs before the main update) did not complete - otherwise it would have kept you from going further.

You should copy the backup files from /tmp to another location and then just update manually.

Issue History

Date Modified Username Field Change
2013-01-21 18:16 Nanotubes New Issue
2013-01-21 18:16 Nanotubes Status new => assigned
2013-01-21 18:16 Nanotubes Assigned To => c_schmitz
2013-01-21 19:29 c_schmitz Note Added: 23732
2013-01-21 19:29 c_schmitz Status assigned => closed
2013-01-21 19:29 c_schmitz Resolution open => not fixable