worldlegacy
August 29, 2018 at 9:17 am
WordPress database error: [Tablespace for table ‘{DatabaseName].wp_esp_promotion_object‘ exists. Please DISCARD the tablespace before IMPORT]
—————————————————————————————————-
We’ve created the table manually to be sure the table could be created and dropped.
[DatabaseName].wp_esp_promotion_object
CREATE TABLE wp_esp_promotion_object
(
POB_ID INT UNSIGNED NOT NULL AUTO_INCREMENT,
PRO_ID INT UNSIGNED NOT NULL,
OBJ_ID INT UNSIGNED NOT NULL,
POB_type VARCHAR(45) NULL,
POB_used INT NULL,
PRIMARY KEY (POB_ID),
KEY OBJ_ID (OBJ_ID),
KEY PRO_ID (PRO_ID)
)
ENGINE=InnoDB DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci
;
—————————————————————————————————-
Per Josh’s post to us:
https://eventespresso.com/topic/event-expresso-promotions-error/#post-262018
Restoring an older version of the database did not fix the problem.
Support thread found and sent by Event Espresso Team:
https://stackoverflow.com/questions/15694168/error-tablespace-for-table-xxx-exists-please-discard-the-tablespace-before-imp
The wp_esp_promotion_object table is not there, so we deleted the supporting files and that did not solve the problem.
wp_esp_promotion_object.idb <- problem file deleted
wp_esp_promotion_object.frm <- file does not exist
Per Josh’s post to us: https://eventespresso.com/topic/event-expresso-promotions-error/#post-262075
Have WebHost clear the error from the database.
Can you please tell us what ‘clearing the error from the database’ would look like?
Even our WebHost is scratching their head.
—————————————————————————————————-
This same error has been found on a few other Support Tickets.
Only one that was not heavily redacted:
Error Code when manually adding registrants
Posted: July 16, 2018 at 5:29 am
Results: Moved to another server, but no result was specified
https://eventespresso.com/topic/error-code-when-manually-adding-registrants/#post-274507
Event Expresso Promotions Error (Our original)
Posted: February 6, 2018 at 12:55 pm
World Legacy original post unresolved
https://eventespresso.com/topic/event-expresso-promotions-error/
Both of these customers experienced the following output from the scripts:
Stack Trace:#0 /home/[CustomerName]/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Activation.helper.php(671):
EventEspresso\core\services\database\TableManager->createTable(‘esp_promotion_o…’, ‘POB_ID INT UNSI…’, ‘InnoDB ‘) #1 /home/[CustomerName]/public_html/wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Base.core.php(647):
EEH_Activation::create_table(‘esp_promotion_o…’, ‘POB_ID INT UNSI…’, ‘ENGINE=InnoDB ‘, false) #2 /home/[CustomerName]/public_html/wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Base.core.php(553):
EE_Data_Migration_Script_Base->_create_table_and_catch_errors(‘esp_promotion_o…’, ‘POB_ID INT UNSI…’, ‘ENGINE=InnoDB ‘, false) #3 /home/[CustomerName]/public_html/wp-content/plugins/eea-promotions/core/data_migration_scripts/EE_DMS_Promotions_1_0_0.dms.php(78):
EE_Data_Migration_Script_Base->_table_should_exist_previously(‘esp_promotion_o…’, ‘POB_ID INT UNSI…’, ‘ENGINE=InnoDB ‘) #4 /home/[CustomerName]/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Addon.core.php(428):
EE_DMS_Promotions_1_0_0->schema_changes_before_migration() #5 /home/[CustomerName]/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Addon.core.php(381):
EE_Addon->initialize_db() #6 [internal function]:
EE_Addon->initialize_db_if_no_migrations_required(”) #7 /home/[CustomerName]/public_html/wp-includes/class-wp-hook.php(298):
call_user_func_array(Array, Array) #8 /home/[CustomerName]/public_html/wp-includes/class-wp-hook.php(323):
WP_Hook->apply_filters(”, Array) #9 /home/[CustomerName]/public_html/wp-includes/plugin.php(453):
WP_Hook->do_action(Array) #10 /home/[CustomerName]/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_System.core.php(1079):
do_action(‘AHEE__EE_System…’) #11 [internal function]:
EE_System->perform_activations_upgrades_and_migrations(”) #12 /home/[CustomerName]/public_html/wp-includes/class-wp-hook.php(298):
call_user_func_array(Array, Array) #13 /home/[CustomerName]/public_html/wp-includes/class-wp-hook.php(323):
WP_Hook->apply_filters(”, Array) #14 /home/[CustomerName]/public_html/wp-includes/plugin.php(453):
WP_Hook->do_action(Array) #15 /home/[CustomerName]/public_html/wp-settings.php(449):
do_action(‘init’) #16 /home/[CustomerName]/public_html/wp-config.php(89):
require_once(‘/home/[CustomerName]/…’) #17 /home/[CustomerName]/public_html/wp-load.php(37):
require_once(‘/home/[CustomerName]/…’) #18 /home/[CustomerName]/public_html/wp-admin/admin.php(31):
require_once(‘/home/[CustomerName]/…’) #19 /home/[CustomerName]/public_html/wp-admin/plugins.php(10):
require_once(‘/home/[CustomerName]/…’) #20 {main}
Josh
August 29, 2018 at 9:24 am
Add New Note to this Reply
Specifically can the web host check to see if someone set foreign_key_checks=0
?
worldlegacy
September 1, 2018 at 9:37 am
Add New Note to this Reply
Josh, the foreign_key_checks is set to 1 (one).
Should we have them change it to 0 (zero)?
Thank you!
Josh
September 4, 2018 at 6:27 am
Add New Note to this Reply
No, because this answer StackExchange mentions changing foreign_key_checks to zero as a potential cause for the error.
This other answer on StackExchage outlines a possible solution:
https://stackoverflow.com/a/50028383/2311736