Support

Home Forums Event Espresso Premium Database failure [Index column size too large. The maximum column size is 767 by

Database failure [Index column size too large. The maximum column size is 767 by

Posted: January 26, 2017 at 5:41 am


Wim Brouwer

January 26, 2017 at 5:41 am

Can anyone help me with this?
I want to install EE4 after older version of EE3. No update, but fresh with no data. I get the following message and EE4 will not run:

WordPress databasefout: [Index column size too large. The maximum column size is 767 bytes.]
CREATE TABLE wp_esp_message ( MSG_ID bigint(20) unsigned NOT NULL AUTO_INCREMENT, GRP_ID int(10) unsigned NULL, MSG_token varchar(255) NULL, TXN_ID int(10) unsigned NULL, MSG_messenger varchar(30) NOT NULL, MSG_message_type varchar(50) NOT NULL, MSG_context varchar(50), MSG_recipient_ID bigint(20) NULL, MSG_recipient_type varchar(45) NULL, MSG_content longtext NULL, MSG_to varchar(255) NULL, MSG_from varchar(255) NULL, MSG_subject varchar(255) NULL, MSG_priority tinyint(1) NOT NULL DEFAULT 3, STS_ID varchar(3) NOT NULL DEFAULT ‘MIC’, MSG_created datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’, MSG_modified datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’, PRIMARY KEY (MSG_ID), KEY GRP_ID (GRP_ID), KEY TXN_ID (TXN_ID), KEY MSG_messenger (MSG_messenger), KEY MSG_message_type (MSG_message_type), KEY MSG_context (MSG_context), KEY MSG_recipient_ID (MSG_recipient_ID), KEY MSG_recipient_type (MSG_recipient_type), KEY MSG_to (MSG_to), KEY MSG_from (MSG_from), KEY MSG_subject (MSG_subject), KEY MSG_priority (MSG_priority), KEY STS_ID (STS_ID), KEY MSG_created (MSG_created), KEY MSG_modified (MSG_modified) ) ENGINE=InnoDB DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci

Stack Trace:#0 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Activation.helper.php(727): EventEspresso\core\services\database\TableManager->createTable(‘esp_message’, ‘MSG_ID bigint(2…’, ‘InnoDB’) #1 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Base.core.php(557): EEH_Activation::create_table(‘esp_message’, ‘MSG_ID bigint(2…’, ‘ENGINE=InnoDB’, false) #2 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Base.core.php(430): EE_Data_Migration_Script_Base->_create_table_and_catch_errors(‘esp_message’, ‘MSG_ID bigint(2…’, ‘ENGINE=InnoDB’, false) #3 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_DMS_Core_4_9_0.dms.php(312): EE_Data_Migration_Script_Base->_table_is_new_in_this_version(‘esp_message’, ‘MSG_ID bigint(2…’, ‘ENGINE=InnoDB’) #4 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Activation.helper.php(850): EE_DMS_Core_4_9_0->schema_changes_before_migration() #5 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Activation.helper.php(125): EEH_Activation::create_database_tables() #6 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_System.core.php(374): EEH_Activation::initialize_db_and_folders() #7 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/admin_pages/maintenance/Maintenance_Admin_Page.core.php(506): EE_System->initialize_db_if_no_migrations_required(true) #8 [internal function]: Maintenance_Admin_Page->_reset_db(true) #9 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page.core.php(865): call_user_func_array(Array, Array) #10 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page.core.php(681): EE_Admin_Page->_route_admin_request() #11 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page.core.php(532): EE_Admin_Page->route_admin_request() #12 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page.core.php(200): EE_Admin_Page->_page_setup() #13 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/admin_pages/maintenance/Maintenance_Admin_Page.core.php(33): EE_Admin_Page->__construct(true) #14 [internal function]: Maintenance_Admin_Page->__construct(true) #15 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page_Init.core.php(392): ReflectionClass->newInstance(true) #16 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page_Init.core.php(267): EE_Admin_Page_Init->_initialize_admin_page() #17 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page_Loader.core.php(342): EE_Admin_Page_Init->do_initial_loads() #18 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page_Loader.core.php(120): EE_Admin_Page_Loader->_get_installed_pages() #19 [internal function]: EE_Admin_Page_Loader->__construct() #20 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Registry.core.php(884): ReflectionClass->newInstanceArgs(Array) #21 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Registry.core.php(687): EE_Registry->_create_object(‘EE_Admin_Page_L…’, Array, ‘core’, false) #22 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Registry.core.php(360): EE_Registry->_load(Array, ‘EE_’, ‘Admin_Page_Load…’, ‘core’, Array, false, true, false) #23 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin.core.php(191): EE_Registry->load_core(‘Admin_Page_Load…’) #24 [internal function]: EE_Admin->init(”) #25 /home/deb73553n2/domains/nlsas.nl/public_html/wp-includes/class-wp-hook.php(298): call_user_func_array(Array, Array) #26 /home/deb73553n2/domains/nlsas.nl/public_html/wp-includes/class-wp-hook.php(323): WP_Hook->apply_filters(”, Array) #27 /home/deb73553n2/domains/nlsas.nl/public_html/wp-includes/plugin.php(453): WP_Hook->do_action(Array) #28 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_System.core.php(943): do_action(‘AHEE__EE_System…’) #29 [internal function]: EE_System->initialize_last(”) #30 /home/deb73553n2/domains/nlsas.nl/public_html/wp-includes/class-wp-hook.php(298): call_user_func_array(Array, Array) #31 /home/deb73553n2/domains/nlsas.nl/public_html/wp-includes/class-wp-hook.php(323): WP_Hook->apply_filters(”, Array) #32 /home/deb73553n2/domains/nlsas.nl/public_html/wp-includes/plugin.php(453): WP_Hook->do_action(Array) #33 /home/deb73553n2/domains/nlsas.nl/public_html/wp-settings.php(449): do_action(‘init’) #34 /home/deb73553n2/domains/nlsas.nl/public_html/wp-config.php(90): require_once(‘/home/deb73553n…’) #35 /home/deb73553n2/domains/nlsas.nl/public_html/wp-load.php(37): require_once(‘/home/deb73553n…’) #36 /home/deb73553n2/domains/nlsas.nl/public_html/wp-admin/admin.php(31): require_once(‘/home/deb73553n…’) #37 {main}
EEH_Activation – create_database_tables – 855
Pronamic iDEAL — Je hebt geen geldige support licentiesleutel ingevuld. Bestel je licentie op pronamic.eu of login om de licentie te controleren.
WordPress databasefout: [Table ‘deb73553n2_wp1.wp_esp_attendee_meta’ doesn’t exist]
SHOW FULL COLUMNS FROM wp_esp_attendee_meta

WordPress databasefout: [Table ‘deb73553n2_wp1.wp_esp_message’ doesn’t exist]
SHOW FULL COLUMNS FROM wp_esp_message

Thanks!


Josh

  • Support Staff

January 26, 2017 at 6:46 am

Hi Wim,

Can you contact your host and ask them to enable larger index columns by enabling the innodb_large_prefix setting?

Reference:
https://dev.mysql.com/doc/refman/5.5/en/innodb-restrictions.html


Wim Brouwer

January 27, 2017 at 4:12 am

innodb_large_prefix = ON , innodb_file_format = BARRACUDA,
But still the same problem.


Wim Brouwer

January 27, 2017 at 5:41 am

If you need more info or want connection to phpmyadmin, please let me know. It would be very helpful to have this problem solved. Now I cannot deliver a working EE4.

Wim


Josh

  • Support Staff

January 27, 2017 at 7:45 am

Did the settings require a change? If so, was the database server rebooted?


Wim Brouwer

January 27, 2017 at 8:50 am

No, I think not.


Wim Brouwer

January 27, 2017 at 8:54 am

I did an experiment in phpmyadmin with the same syntax but with extra ROW_FORMAT=DYNAMIC. Then the table gave no error.


Josh

  • Support Staff

January 27, 2017 at 12:15 pm

Did the wp_esp_message table end up getting created then?


Wim Brouwer

January 30, 2017 at 8:37 am

Yes it was created then manually.


Wim Brouwer

January 31, 2017 at 3:41 am

I managed to create wp_esp_message table manually with ROW_FORMAT=COMPRTESSED. But when I add an event it says:

Notice: WPDB Error “Table ‘deb73553n2_wp1.wp_esp_attendee_meta’ doesn’t exist” tijdens het uitvoeren van wpdb methode “get_results” met argumenten [“SELECT Registration.REG_ID AS ‘Registration.REG_ID’, Registration.EVT_ID AS ‘Registration.EVT_ID’, Registration.ATT_ID AS ‘Registration.ATT_ID’, Registration.TXN_ID AS ‘Registration.TXN_ID’, Registration.TKT_ID AS ‘Registration.TKT_ID’, Registration.STS_ID AS ‘Registration.STS_ID’, Registration.REG_date AS ‘Registration.REG_date’, Registration.REG_final_price AS ‘Registration.REG_final_price’, Registration.REG_paid AS ‘Registration.REG_paid’, Registration.REG_session AS ‘Registration.REG_session’, Registration.REG_code AS ‘Registration.REG_code’, Registration.REG_url_link AS ‘Registration.REG_url_link’, Registration.REG_count AS ‘Registration.REG_count’, Registration.REG_group_size AS ‘Registration.REG_group_size’, Registration.REG_att_is_going AS ‘Registration.REG_att_is_going’, Registration.REG_deleted AS ‘Registration.REG_deleted’, TransactionTable.TXN_ID AS ‘Transact in /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php on line 2263

Notice: WPDB AGAIN: Fout “Table ‘deb73553n2_wp1.wp_esp_attendee_meta’ doesn’t exist” tijdens het uitvoeren van dezelfde methode en argumenten als eerder. Poging EE Addons DB automatisch te herstellen. in /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php on line 2263

What is a solution?


Wim Brouwer

January 31, 2017 at 3:47 am

I had the same problems with CREATE TABLE wp_esp_attendee_meta(
Again ROW_FORMAT=COMPRESSED did the trick in phpmyadmin.
Strange that I have these problems…


Josh

  • Support Staff

January 31, 2017 at 10:54 am

It is strange, but we did find an issue with some of the recent changes to database scripts and have a ticket to ensure all database indexes are smaller than 191 characters. If you or anyone else would like to test the branch while it’s available for testing, it can be downloaded from here:

https://github.com/eventespresso/event-espresso-core/tree/BUG-10435-ensure-all-db-indexes-smaller-than-191-characters

The support post ‘Database failure [Index column size too large. The maximum column size is 767 by’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso