View Issue Details

IDProjectCategoryView StatusLast Update
12202Bug reports[All Projects] ComfortUpdatepublic2017-10-23 11:11
Reporterweb_digitalAssigned ToLouisGac 
Status closedResolutionfixed 
Product Version2.63.x 
Target VersionFixed in Version 
Summary12202: Comfort update notification message fails to save to SQL Server DB - user locked out
DescriptionThere looks to be a bug saving the comfort update notifications to database for SQL Server.
When there is an update due this results in the user being unable to log in to the admin and a sql error being displayed - see attached.
To fix I updated locally and pushed the new code to the server, so no further updates were due.
TagsNo tags attached.
Complete LimeSurvey version number (& build)2.63.1+170305
I will donate to the project if issue is resolvedNo
Database & DB-VersionSQL Server
Operating System (Server)Ubuntu
Webserver software & versionApache 2
PHP Version5




2017-03-14 18:21


sql-bug.txt (2,428 bytes)

CDbCommand failed to execute the SQL statement: SQLSTATE[HY000]: General error: 515 General SQL Server error: Check messages from the SQL Server [515] (severity 16) [(null)]. The SQL statement executed was: INSERT INTO [dbo].[lime_notifications] ([status], [importance], [display_class], [entity], [entity_id], [title], [message], [created], [hash]) VALUES (:yp0, :yp1, :yp2, :yp3, :yp4, :yp5, :yp6, GETDATE(), :yp7). Bound with :yp0='new', :yp1=1, :yp2='default', :yp3='user', :yp4=1, :yp5='New update available (Current version: 170203)', :yp6='A security update is available.<a href=/index.php/admin/update>Click here to use ComfortUpdate.</a>', :yp7='9e40344f3b6f569b347e2e5451c7e513a8e27fce7ec4ecea7244a104bfa94575'


346         {
347             if($this->_connection->enableProfiling)
348                 Yii::endProfile('system.db.CDbCommand.execute('.$this->getText().$par.')','system.db.CDbCommand.execute');
350             $errorInfo=$e instanceof PDOException ? $e->errorInfo : null;
351             $message=$e->getMessage();
352             Yii::log(Yii::t('yii','CDbCommand::execute() failed: {error}. The SQL statement executed was: {sql}.',
353                 array('{error}'=>$message, '{sql}'=>$this->getText().$par)),CLogger::LEVEL_ERROR,'system.db.CDbCommand');
355             if(YII_DEBUG)
356                 $message.='. The SQL statement executed was: '.$this->getText().$par;
358             throw new CDbException(Yii::t('yii','CDbCommand failed to execute the SQL statement: {error}',
359                 array('{error}'=>$message)),(int)$e->getCode(),$errorInfo);
360         }
361     }
363     /**
364      * Executes the SQL statement and returns query result.
365      * This method is for executing an SQL query that returns result set.
366      * @param array $params input parameters (name=>value) for the SQL execution. This is an alternative
367      * to {@link bindParam} and {@link bindValue}. If you have multiple input parameters, passing
368      * them in this way can improve the performance. Note that if you pass parameters in this way,
369      * you cannot bind parameters or values using {@link bindParam} or {@link bindValue}, and vice versa.
370      * Please also note that all values are treated as strings in this case, if you need them to be handled as
sql-bug.txt (2,428 bytes)

Issue History

Date Modified Username Field Change
2017-03-14 18:21 web_digital New Issue
2017-03-14 18:21 web_digital Status new => assigned
2017-03-14 18:21 web_digital Assigned To => LouisGac
2017-03-14 18:21 web_digital File Added: sql-bug.txt
2017-10-23 11:11 LouisGac Status assigned => closed
2017-10-23 11:11 LouisGac Resolution open => fixed