LimeSurvey issue tracker
Registration

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
07096Bug reports[All Projects] Installationpublic2012-12-17 09:522012-12-20 23:35
Reporterocean 
Assigned Toc_schmitz 
PriorityimmediateSeveritymajor 
StatusclosedResolutionno change required 
Product Version2.00+ 
Target VersionFixed in Version 
Summary07096: upgrade error on table ###.lime_survey_links doesn't exist
DescriptionFrom: $versionnumber = "1.92+"; $dbversionnumber = 155.5; $buildnumber = '120919';
To: $config['versionnumber'] = "2.00+"; $config['dbversionnumber'] = 164; $config['buildnumber'] = '121213';

You get an error see forum link:
http://www.limesurvey.org/nl/forum/installation-a-update-issues/89446-database-update-failed [^]
I will donate to the project if issue is resolved within 48 hrsNo
LimeSurvey build number OR git commit ID121213
Browser
Database & DB-Version?
Operating System (Server)osx
Webserver software & version?
PHP Version?
Attached Filespng file icon CDbCommand.PNG [^] (82,216 bytes) 2012-12-17 09:52

- Relationships

-  Notes
User avatar (23258)
Mazi (developer)
2012-12-17 10:17

This problem was reported by at least two users at the forums.

Since I'm not sure if this was already fixed at the latest release, can someone please look into it if this is still an issue?!
User avatar (23307)
mdekker (developer)
2012-12-20 13:04

155.5 is a strange number... from files i see it should be 155.6 (did not really check)
User avatar (23309)
Mazi (developer)
2012-12-20 13:46

If I remember correclty, TMSWhite once set a DB version number of 155.5

I would assume that the 155.6 number results from a forced DB update on your test system, Menno.
User avatar (23315)
mdekker (developer)
2012-12-20 16:26

Check https://github.com/LimeSurvey/LimeSurvey/blob/1.92/admin/update/upgrade-mysql.php [^] around line 700 it should be set to 155.6
User avatar (23316)
Mazi (developer)
2012-12-20 16:30

Weird, I have never seen that DB build number before.
User avatar (23333)
c_schmitz (administrator)
2012-12-20 23:35

Anyway, the described issue it result from a bug in a old 1.92 build.
Install a clean 1.92 version and copy the missing table from your fresh install to your 1.92 production database. After that the update should work.

- Issue History
Date Modified Username Field Change
2012-12-17 09:52 ocean New Issue
2012-12-17 09:52 ocean File Added: CDbCommand.PNG
2012-12-17 10:17 Mazi Note Added: 23258
2012-12-17 10:18 Mazi Assigned To => c_schmitz
2012-12-17 10:18 Mazi Status new => assigned
2012-12-20 13:04 mdekker Note Added: 23307
2012-12-20 13:46 Mazi Note Added: 23309
2012-12-20 16:26 mdekker Note Added: 23315
2012-12-20 16:30 Mazi Note Added: 23316
2012-12-20 23:35 c_schmitz Note Added: 23333
2012-12-20 23:35 c_schmitz Status assigned => closed
2012-12-20 23:35 c_schmitz Resolution open => no change required


Copyright © 2000 - 2014 MantisBT Team
Powered by Mantis Bugtracker