View Issue Details

IDProjectCategoryView StatusLast Update
0013390Tine 2.0Setuppublic2017-08-14 15:54
ReporterkoelschejungAssigned Topmehrer 
PrioritynormalSeveritymajorReproducibilityhave not tried
Status resolvedResolutionfixed 
Product Version2017.08.2 Community Edition 
Target Version2017.08.3 Community EditionFixed in Version2017.08.3 Community Edition 
Summary0013390: container_id update script problems
DescriptionI updated from Ubuntu-Repository, if i update the databases in setup, i get erros by update tinebase.
(Sorry my english is not so good, ich habe eben aus den Ubuntu Quellen aktualisiert. Beim Aktualisierung der DB der Pakete schlägt es bei Tinebase fehl.)

(Im log finde ich folgenden Eintrag: )
Here is the error-log:
e4916 setupuser - 2017-08-10T15:25:17+00:00 ERR (3): Tinebase_Exception::log::104 Zend_Db_Statement_Exception -> SQLSTATE[HY000]: General error: 1005 Can't create table `schoenberg`.`#sql-40e_94e6` (errno: 150 "Foreign key constraint is incorrectly formed"), query was: ALTER TABLE `tine20_cal_resources` ADD CONSTRAINT `tine20_cal_resources::container_id--container::id` FOREIGN KEY (`container_id`) REFERENCES `tine20_container` (`id`)

Andere User haben das gleiche Problem:

Nach dem ich die DB wieder zurückgespielt habe und das Paket Tinebase, als erstes aktualisiert habe, ging es bei mir durch. Bei anderen leider nicht.

TagsNo tags attached.


related to 0013392 resolvedpschuele Tinebase needs to be updated first 




2017-08-11 23:14

reporter   ~0020592


i could fix this by manually updating the sql-tables.

It seems, that the data type of the first named column (in the above case: table=tine20_cal_resources, column=container_id) was not changed from int() to varchar(40).
I manually changed this via phpmyadmin and now everything is working fine.
(If you are doing, too, do not forget to set the "Attribute" to "<empty>").

Had to do the above steps for about 3-5 more tables, but didn't note the names.

Updating the data types should be checked during the upgrade-procedure.

Kind regards,


2017-08-14 11:34

developer   ~0020598


the issue is that Tinebase must be updated first and actually in this case all (precisely: some affected) applications need to be updated in one run (!). We created a separate task to enforce this in the setup. (

To resolve this manually I would strongly advice not to alter the table structure manually! The right way to resolve this, is to set back the application version as listed below and then do an update for all application in one run.

So if you run partial updates (which will be not be possible anymore in the near future) please check the application versions (tine20_applications table). If they are higher than the versions listed here, set them back to the listed version:
Addressbook: 10.5
Calendar: 10.7
Crm: 10.1
Events: 10.1
Projects: 10.1
Sales: 10.8
SimpleFAQ: 10.0
Tasks: 10.1
Timetracker: 10.2

then do a full update of all applications in one run!

best regards

Issue History

Date Modified Username Field Change
2017-08-11 16:59 koelschejung New Issue
2017-08-11 23:14 WolfgangAndreas Note Added: 0020592
2017-08-14 09:32 pschuele Assigned To => pmehrer
2017-08-14 11:12 pschuele Issue cloned: 0013392
2017-08-14 11:12 pschuele Relationship added related to 0013392
2017-08-14 11:34 pmehrer Note Added: 0020598
2017-08-14 13:18 pschuele Summary Update TineBase schlägt fehl. => container_id update script problems
2017-08-14 13:19 pschuele Status new => gerrit
2017-08-14 13:19 pschuele Target Version => 2017.08.4 Community Edition
2017-08-14 13:20 pschuele Status gerrit => resolved
2017-08-14 13:20 pschuele Fixed in Version => 2017.08.4 Community Edition
2017-08-14 14:51 mspahn Target Version 2017.08.4 Community Edition => 2017.08.3 Community Edition
2017-08-14 15:19 mspahn Fixed in Version 2017.08.4 Community Edition => 2017.08.3 Community Edition
2017-08-14 15:54 pschuele Resolution open => fixed