Error when upgrading - V13.3 to 13.4
- Thread starter Busman412
- Start date
Hello,
are you sure you uploaded the correct ZIP file, with unchanged name? It looks like DaDaBIK can't recognize the version from the file name.
if you are using the lifetime version, the file is dadabik_13.4-Levanto_enterprise.zip, for the monthly subscription is dadabik_13.4-Levanto_enterprise_monthly.zip
are you sure you uploaded the correct ZIP file, with unchanged name? It looks like DaDaBIK can't recognize the version from the file name.
if you are using the lifetime version, the file is dadabik_13.4-Levanto_enterprise.zip, for the monthly subscription is dadabik_13.4-Levanto_enterprise_monthly.zip
Hi Eugenio, I'm getting this error that has never happened before when upgrading. Anaelog is the database name.
[08] Error: during query execution. CREATE TABLE `anaelog_user_entities` ( id_user_entity INTEGER PRIMARY KEY NOT NULL AUTO_INCREMENT, table_user_entity VARCHAR(128) NOT NULL UNIQUE, id_user_field_user_entity VARCHAR(255) NOT NULL, first_name_field_user_entity VARCHAR(100) NULL, last_name_field_user_entity VARCHAR(100) NULL, email_field_user_entity VARCHAR(100) NULL, sync_create_user_entity SMALLINT NOT NULL, sync_update_user_entity SMALLINT NOT NULL, sync_delete_user_entity SMALLINT NOT NULL, id_group_user_entity INT NOT NULL UNIQUE, FOREIGN KEY (id_group_user_entity) REFERENCES dadabik_groups(id_group) ON DELETE CASCADE ON UPDATE CASCADE) ENGINE = INNODB ENGINE=InnoDB
The DBMS server said: SQLSTATE[HY000]: General error: 1005 Can't create table `anaelog`.`anaelog_user_entities` (errno: 150 "Foreign key constraint is incorrectly formed")
You are not running the last release of DaDaBIK, the release you are running might have bugs and security holes, see the official change log for further information. You can upgrade DaDaBIK here.
In case you want to upgrade to a more powerful edition (from Pro to Enterprise/Platinum, from Enterprise to Platinum) please contact us.
mysql version: 11.4.5-MariaDB-0ubuntu0.24.10.1
Web server: Apache/2.4.62 (Ubuntu)
Client: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/146.0.0.0 Safari/537.36
URL installation:
[08] Error: during query execution. CREATE TABLE `anaelog_user_entities` ( id_user_entity INTEGER PRIMARY KEY NOT NULL AUTO_INCREMENT, table_user_entity VARCHAR(128) NOT NULL UNIQUE, id_user_field_user_entity VARCHAR(255) NOT NULL, first_name_field_user_entity VARCHAR(100) NULL, last_name_field_user_entity VARCHAR(100) NULL, email_field_user_entity VARCHAR(100) NULL, sync_create_user_entity SMALLINT NOT NULL, sync_update_user_entity SMALLINT NOT NULL, sync_delete_user_entity SMALLINT NOT NULL, id_group_user_entity INT NOT NULL UNIQUE, FOREIGN KEY (id_group_user_entity) REFERENCES dadabik_groups(id_group) ON DELETE CASCADE ON UPDATE CASCADE) ENGINE = INNODB ENGINE=InnoDB
The DBMS server said: SQLSTATE[HY000]: General error: 1005 Can't create table `anaelog`.`anaelog_user_entities` (errno: 150 "Foreign key constraint is incorrectly formed")
Your current DaDaBIK version
You are using DaDaBIK version 13.3-Levanto enterprise, installed on Jan 21, 2026 (installation code: ), the latest version of DaDaBIK is 13.4-Levanto released on Mar 18, 2026You are not running the last release of DaDaBIK, the release you are running might have bugs and security holes, see the official change log for further information. You can upgrade DaDaBIK here.
In case you want to upgrade to a more powerful edition (from Pro to Enterprise/Platinum, from Enterprise to Platinum) please contact us.
System info
PHP Version: 8.3.11mysql version: 11.4.5-MariaDB-0ubuntu0.24.10.1
Web server: Apache/2.4.62 (Ubuntu)
Client: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/146.0.0.0 Safari/537.36
URL installation:
Ok, but is this the file you actually copied in the upgrades_xxxxxxxxx folder? Are you sure the name has not been changed?
Can DaDaBIK read the content of the upgrades_ folder? Could you check the folder permissions?
I recommend to open an email support ticket so we can take a closer look to the problem.
Best,
Hello,
I guess you set a custom $prefix_internal_table, correct? If yes I am afraid this is the result of a bug I posted few minutes ago, in the post you can see a workaround.
Best,