View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|13946||Bug reports||[All Projects] Survey taking||public||2018-08-07 19:25||2018-08-22 15:08|
|Target Version||Fixed in Version|
|Summary||13946: SQL error when saving a response|
When a participant tries to save and resume later, the "An error occurred saving a response to survey" error is being triggered, and an email notification about it is being sent to the survey administrator.
This is the content of the email (I have removed personal information about the participant for obvious reasons, placeholders are between brackets <> ) :
There is no error message at the end of the email, it just ends there.
The thing that jumps to me right away is that the table name in that sql update statement is incorrect. Our Limesurvey installation uses the "lime_" prefix on tables, so it should be lime_survey_524447 instead of survey_524447. So it looks like somehow the Limesurvey code is not taking into account the table prefix when building that query.
|Steps To Reproduce|
I don't have steps to reproduce, just the notification email sent by the system.
|Tags||No tags attached.|
|Complete LimeSurvey version number (& build)||Version 3.13.2+180709|
|I will donate to the project if issue is resolved||No|
|Browser||Google Chrome Version 56.0.2924.87 (64-bit)|
|Database & DB-Version||mysql Ver 14.14 Distrib 5.5.60, for Linux (x86_64) using readline 5.1; Limesurvey dbversionnumber = 353|
|Operating System (Server)||CentOS release 6.9|
|Webserver software & version||Apache/2.2.15 (Unix)|
|PHP Version||PHP 5.6.36|
Can you please attach the offending survey?
limesurvey_survey_524447.lss (120,386 bytes)
Sorry, still cannot reproduce. Do you know which questions were answered? Can you reproduce it your self?
I think this issue maybe related to this one I have just raised: https://bugs.limesurvey.org/view.php?id=13950
"CDbCommand failed to execute the SQL statement: SQLSTATE: [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Implicit conversion from data type nvarchar to varbinary(max) is not allowed. Use the CONVERT function to run this query."
your bug ticket says that you're using MySQL. Are you indeed using mssql?
Wasn't there an issue a while ago which caused the DB prefix to not be set properly?
Same Issue here 13880
@Mazi: I am suspecting that is what is happening here.
Yes, I would say is the same scenario described in https://bugs.limesurvey.org/view.php?id=13880.
|2018-08-07 19:25||segui||New Issue|
|2018-08-08 11:02||olle||Note Added: 48753|
|2018-08-08 11:03||olle||Status||new => feedback|
|2018-08-08 16:38||gslines||File Added: limesurvey_survey_524447.lss|
|2018-08-08 16:38||gslines||Note Added: 48762|
|2018-08-08 17:51||olle||Note Added: 48763|
|2018-08-09 12:40||MerkOne||Note Added: 48764|
|2018-08-09 17:55||LouisGac||Note Added: 48768|
|2018-08-17 15:12||Mazi||Note Added: 48821|
|2018-08-17 22:54||ArneD||Note Added: 48822|
|2018-08-22 15:08||gslines||Note Added: 48854|