View Issue Details

This bug affects 1 person(s).
 6
IDProjectCategoryView StatusLast Update
07096Bug reportsInstallationpublic2012-12-20 23:35
Reporterocean Assigned Toc_schmitz  
PriorityimmediateSeveritypartial_block 
Status closedResolutionno change required 
Product Version2.00+ 
Summary07096: upgrade error on table ###.lime_survey_links doesn't exist
Description

From: $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

TagsNo tags attached.
Attached Files
CDbCommand.PNG (82,216 bytes)   
CDbCommand.PNG (82,216 bytes)   
Bug heat6
Complete LimeSurvey version number (& build)121213
I will donate to the project if issue is resolvedNo
Browser
Database type & version?
Server OS (if known)osx
Webserver software & version (if known)?
PHP Version?

Users monitoring this issue

There are no users monitoring this issue.

Activities

Mazi

Mazi

2012-12-17 10:17

updater   ~23258

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?!

mdekker

mdekker

2012-12-20 13:04

reporter   ~23307

155.5 is a strange number... from files i see it should be 155.6 (did not really check)

Mazi

Mazi

2012-12-20 13:46

updater   ~23309

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.

mdekker

mdekker

2012-12-20 16:26

reporter   ~23315

Check https://github.com/LimeSurvey/LimeSurvey/blob/1.92/admin/update/upgrade-mysql.php around line 700 it should be set to 155.6

Mazi

Mazi

2012-12-20 16:30

updater   ~23316

Weird, I have never seen that DB build number before.

c_schmitz

c_schmitz

2012-12-20 23:35

administrator   ~23333

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