View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
12231 | Bug reports | Installation | public | 2017-03-27 18:10 | 2017-06-14 17:07 |
Reporter | franz007 | Assigned To | |||
Priority | none | Severity | crash | ||
Status | closed | Resolution | no change required | ||
Product Version | 2.64.x | ||||
Summary | 12231: Cannot update db | ||||
Description | Upgrading from 2.64.2 (build 170324) to 2.64.3 (build 170327), after copying the config.php file to the new directory, accessing the admin page, it fails with the following Internal Server Error: | ||||
Tags | No tags attached. | ||||
Bug heat | 4 | ||||
Complete LimeSurvey version number (& build) | 2.64.3 (build 170327) | ||||
I will donate to the project if issue is resolved | No | ||||
Browser | |||||
Database type & version | MySQL 5.5.54-0+deb8u1 (Debian) | ||||
Server OS (if known) | Debian 8.7 | ||||
Webserver software & version (if known) | apache2 2.4.10-10+deb8u4 | ||||
PHP Version | 5.6.30+dfsg-0+deb8u1 | ||||
Please discard this issue. |
|
This is still an active issue. I tried upgrading directly from 2.05 to 2.65 Notifications table was not there. I am trying to create the table from my dev to push it along. I will see if it works. PS, I had no problme on dev |
|
Here is what I did to get around it An non-recoverable error happened during the update. Error details: CDbCommand failed to execute the SQL statement: SQLSTATE[42S01]: [Microsoft][ODBC Driver 11 for SQL Server][SQL Server]There is already an object named 'lime_notifications' in the database.. The SQL statement executed was: CREATE TABLE [lime_notifications] ( [id] int IDENTITY PRIMARY KEY NOT NULL, [entity] nvarchar(15) not null, [entity_id] int not null, [title] nvarchar(255) not null, [message] nvarchar(max) not null, [status] nvarchar(15) default 'new' NULL, [importance] int default 1 NULL, [display_class] nvarchar(31) default 'default' NULL, [created] datetime not null, [first_read] datetime null ) Our next attempt was to delete the table and continue. I believe there is something wrong in the upgrade db script. It checked for the existence of the table notifications and if not present, dies yet later on, it asked to create the table. Why was it looking for the notifications table if it was to be created later? I think it now works. I will see what happens for the next minor point upgrade. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2017-03-27 18:10 | franz007 | New Issue | |
2017-03-27 18:11 | franz007 | Issue Monitored: franz007 | |
2017-03-29 14:10 | franz007 | Issue End Monitor: franz007 | |
2017-03-29 14:11 | franz007 | Note Added: 43361 | |
2017-03-31 00:58 | DenisChenu | Relationship added | related to 11550 |
2017-03-31 00:59 | DenisChenu | Status | new => closed |
2017-03-31 00:59 | DenisChenu | Resolution | open => no change required |
2017-06-14 16:32 | katcher01 | Note Added: 43907 | |
2017-06-14 17:07 | katcher01 | Note Added: 43908 |