View Issue Details

This bug affects 1 person(s).
 8
IDProjectCategoryView StatusLast Update
09457Bug reportsOtherpublic2015-08-24 14:37
Reporterkatcher01 Assigned Toc_schmitz  
PrioritynormalSeverityminor 
Status closedResolutionfixed 
Product Version2.05+ 
Fixed in Version2.06+ 
Summary09457: A number of MSSQL Errors
Description

Unable to execute check integrity

1) CDbCommand failed to execute the SQL statement: SQLSTATE[IMSSP]: Tried to bind parameter number 2101. SQL Server supports a maximum of 2100 parameters.

Another issue:

2) CDbCommand failed to execute the SQL statement: SQLSTATE[42S02]: [Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid object name 'dbo.lime_tokens_XXXXX

Steps To Reproduce

Unable to force a reproduce of first error.

Second issue was provided to me by an end user. Here is his what he did

The main steps I took were

Create survey with 1 question group
Activtated survey
Created 1 public registered token.
Tested survey display (entered no responses)
Deactivated survey
Got SQL errors and unable to access survey again

TagsNo tags attached.
Attached Files
LimeSurvey-debug.txt (146,437 bytes)
Bug heat8
Complete LimeSurvey version number (& build)Version 2.05+ Build 140116
I will donate to the project if issue is resolvedNo
Browser
Database type & versionMSSQL 2008 R2
Server OS (if known)2008 R2 enterprise
Webserver software & version (if known)apache 2.X
PHP Version5.4X

Users monitoring this issue

There are no users monitoring this issue.

Activities

Mazi

Mazi

2015-01-14 08:25

updater   ~31461

I have marked this ticket "private" so only our develoeprs can access it.

katcher01, please attach your DB for testing.

Thanks!

katcher01

katcher01

2015-01-14 14:58

reporter   ~31462

Hi Mazi, I am currently not permitted to send a copy of the db to you due to privacy concerns. Can you suggest a method to anonymize the db?

PS, the user has tried to replicate the issue 2 regrading the token but was not able. He indicated that the survey he was testing was not available for him to re-activate. Today however, it was there. He shared his desktop with us and easily restored re-activated the survey. So, for this issue, lets call it a one off and hope it was an anomaly.

The first issue (integrity) is still troubling. Since it is a production machine, I am unable to turn debug on. Is there some way you can provide the sql or a sample of the sql the integrity check produces so that I may attempt to run it directly on the db to find the offending sql statement?

Mazi

Mazi

2015-01-14 15:43

updater   ~31463

Carsten, please drop katcher01 a note if you need anything else for testing.

c_schmitz

c_schmitz

2015-02-02 13:28

administrator   ~31586

katcher, without more info on the error message by using debug mode it is not possible to locate the error.
You can can activate the debug mode only for a few seconds to run the check , and then deactivate it right away, again. It should not cause any troubles for your participants, even if the survey is just being used.

katcher01

katcher01

2015-02-02 15:50

reporter   ~31598

Hello, I have asked the admin to turn on debug in order to assist you. I am not sure if they will be able to turn it on or not. I will advise. PS, should I set debug to 2? Also, Is there an admin setting or must I set debug in config?

Thanks

Eric

c_schmitz

c_schmitz

2015-02-02 16:14

administrator   ~31602

You have to set it in /application/config/config.php

katcher01

katcher01

2015-02-02 16:58

reporter   ~31604

As requested debug input provided in file.

Eric

katcher01

katcher01

2015-02-19 15:16

reporter   ~31707

Hello all wondering if any progerss was made on the above error.

Eric

c_schmitz

c_schmitz

2015-03-05 12:41

administrator   ~31769

I am sorry for the delay. We are working on it.

medicnick

medicnick

2015-03-18 18:35

reporter   ~31854

I am able to check integrity on MSSQL - it returns multiple findings but if you click on the "fix it" links they do not do anything. If that is unrelated to this issue I can submit a new issue, please advise.

katcher01

katcher01

2015-03-18 20:29

reporter   ~31855

I do not think it is the same, I do not even get to a result screen indication what needs to be fixed. Hope this helps

Eric

c_schmitz

c_schmitz

2015-08-21 15:39

administrator   ~32977

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

c_schmitz

c_schmitz

2015-08-21 15:42

administrator   ~32978

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

c_schmitz

c_schmitz

2015-08-24 12:35

administrator   ~32986

2.06+ Build 150824 released

c_schmitz

c_schmitz

2015-08-24 14:36

administrator   ~32998

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

c_schmitz

c_schmitz

2015-08-24 14:37

administrator   ~32999

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

Related Changesets

LimeSurvey: master 8187a733

2015-08-21 13:39:45

c_schmitz

Details Diff
Fixed issue 09457: Error in integrity check when using MSSQL Affected Issues
09457
mod - application/controllers/admin/checkintegrity.php Diff File

LimeSurvey: develop 724be21e

2015-08-21 13:41:58

c_schmitz

Details Diff
Fixed issue 09457: Error in integrity check when using MSSQL Affected Issues
09457
mod - application/controllers/admin/checkintegrity.php Diff File

LimeSurvey: master 114bb97a

2015-08-24 12:35:59

c_schmitz

Details Diff
Fixed issue 09457: Error in integrity check when using MSSQL Affected Issues
09457
mod - application/controllers/admin/checkintegrity.php Diff File

LimeSurvey: develop f93951bb

2015-08-24 12:37:30

c_schmitz

Details Diff
Fixed issue 09457: Error in integrity check when using MSSQL Affected Issues
09457
mod - application/controllers/admin/checkintegrity.php Diff File

Issue History

Date Modified Username Field Change
2015-01-13 22:32 katcher01 New Issue
2015-01-14 08:24 Mazi View Status public => private
2015-01-14 08:25 Mazi Note Added: 31461
2015-01-14 08:25 Mazi Assigned To => c_schmitz
2015-01-14 08:25 Mazi Status new => feedback
2015-01-14 14:58 katcher01 Note Added: 31462
2015-01-14 14:58 katcher01 Status feedback => assigned
2015-01-14 15:43 Mazi Note Added: 31463
2015-02-02 13:28 c_schmitz Note Added: 31586
2015-02-02 13:28 c_schmitz Status assigned => feedback
2015-02-02 15:50 katcher01 Note Added: 31598
2015-02-02 15:50 katcher01 Status feedback => assigned
2015-02-02 16:14 c_schmitz Note Added: 31602
2015-02-02 16:15 c_schmitz Status assigned => feedback
2015-02-02 16:58 katcher01 File Added: LimeSurvey-debug.txt
2015-02-02 16:58 katcher01 Note Added: 31604
2015-02-02 16:58 katcher01 Status feedback => assigned
2015-02-09 21:49 katcher01 Issue Monitored: katcher01
2015-02-09 21:49 katcher01 Issue End Monitor: katcher01
2015-02-19 15:16 katcher01 Note Added: 31707
2015-03-05 12:41 c_schmitz Note Added: 31769
2015-03-06 13:57 c_schmitz View Status private => public
2015-03-18 18:35 medicnick Note Added: 31854
2015-03-18 20:29 katcher01 Note Added: 31855
2015-08-21 15:39 c_schmitz Changeset attached => LimeSurvey master 8187a733
2015-08-21 15:39 c_schmitz Note Added: 32977
2015-08-21 15:39 c_schmitz Resolution open => fixed
2015-08-21 15:42 c_schmitz Changeset attached => LimeSurvey develop 724be21e
2015-08-21 15:42 c_schmitz Note Added: 32978
2015-08-21 15:42 c_schmitz Status assigned => resolved
2015-08-21 15:42 c_schmitz Fixed in Version => 2.06+
2015-08-24 12:35 c_schmitz Note Added: 32986
2015-08-24 12:35 c_schmitz Status resolved => closed
2015-08-24 14:36 c_schmitz Changeset attached => LimeSurvey master 114bb97a
2015-08-24 14:36 c_schmitz Note Added: 32998
2015-08-24 14:37 c_schmitz Changeset attached => LimeSurvey develop f93951bb
2015-08-24 14:37 c_schmitz Note Added: 32999