250610 11:06:04 [Note] Plugin 'FEDERATED' is disabled.
250610 11:06:04 InnoDB: The InnoDB memory heap is disabled
250610 11:06:04 InnoDB: Mutexes and rw_locks use Windows interlocked functions
250610 11:06:04 InnoDB: Compressed tables use zlib 1.2.3
250610 11:06:04 InnoDB: Initializing buffer pool, size = 250.0M
250610 11:06:04 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file .\ibdata1 did not exist:
InnoDB: a new database to be created!
250610 11:06:04  InnoDB: Setting file .\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
250610 11:06:04  InnoDB: Log file .\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile0 size to 50 MB
InnoDB: Database physically writes the file full: wait...
250610 11:06:04  InnoDB: Log file .\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile1 size to 50 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
250610 11:06:04  InnoDB: Waiting for the background threads to start
250610 11:06:05 InnoDB: 5.5.41 started; log sequence number 0
250610 11:06:05 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
250610 11:06:05 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
250610 11:06:05 [Note] Server socket created on IP: '0.0.0.0'.
250610 11:06:05 [Note] Event Scheduler: Loaded 0 events
250610 11:06:05 [Note] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: ready for connections.
Version: '5.5.41'  socket: ''  port: 3306  MySQL Community Server (GPL)
250610 11:06:21 [Note] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Normal shutdown

250610 11:06:21 [Note] Event Scheduler: Purging the queue. 0 events
250610 11:06:21  InnoDB: Starting shutdown...
250610 11:06:21  InnoDB: Shutdown completed; log sequence number 1595675
250610 11:06:21 [Note] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Shutdown complete

250610 11:07:08 [Note] Plugin 'FEDERATED' is disabled.
250610 11:07:08 InnoDB: The InnoDB memory heap is disabled
250610 11:07:08 InnoDB: Mutexes and rw_locks use Windows interlocked functions
250610 11:07:08 InnoDB: Compressed tables use zlib 1.2.3
250610 11:07:08 InnoDB: Initializing buffer pool, size = 250.0M
250610 11:07:08 InnoDB: Completed initialization of buffer pool
250610 11:07:08 InnoDB: highest supported file format is Barracuda.
250610 11:07:08  InnoDB: Waiting for the background threads to start
250610 11:07:09 InnoDB: 5.5.41 started; log sequence number 1595675
250610 11:07:09 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
250610 11:07:09 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
250610 11:07:09 [Note] Server socket created on IP: '0.0.0.0'.
250610 11:07:09 [Note] Event Scheduler: Loaded 0 events
250610 11:07:09 [Note] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: ready for connections.
Version: '5.5.41'  socket: ''  port: 3306  MySQL Community Server (GPL)
250610 11:07:31 [Warning] '.\sas_acetech\wp_actionscheduler_actions' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_actionscheduler_claims' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_actionscheduler_groups' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_actionscheduler_logs' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_commentmeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_comments' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_fbv' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_fbv_attachment_folder' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_fsmpt_email_logs' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_itsec_bans' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_itsec_dashboard_events' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_itsec_distributed_storage' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_itsec_fingerprints' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_itsec_geolocation_cache' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_itsec_lockouts' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_itsec_logs' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_itsec_mutexes' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_itsec_opaque_tokens' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_itsec_temp' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_itsec_user_groups' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_links' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_options' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_post_views' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_postmeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_posts' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [ERROR] Cannot find or open table sas_acetech/wp_revslider_css from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:31 [ERROR] Cannot find or open table sas_acetech/wp_revslider_css_bkp from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:31 [ERROR] Cannot find or open table sas_acetech/wp_revslider_layer_animations from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:31 [ERROR] Cannot find or open table sas_acetech/wp_revslider_layer_animations_bkp from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:31 [ERROR] Cannot find or open table sas_acetech/wp_revslider_navigations from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:31 [ERROR] Cannot find or open table sas_acetech/wp_revslider_navigations_bkp from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:31 [ERROR] Cannot find or open table sas_acetech/wp_revslider_sliders from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:31 [ERROR] Cannot find or open table sas_acetech/wp_revslider_sliders_bkp from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:31 [ERROR] Cannot find or open table sas_acetech/wp_revslider_slides from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:31 [ERROR] Cannot find or open table sas_acetech/wp_revslider_slides_bkp from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:31 [ERROR] Cannot find or open table sas_acetech/wp_revslider_static_slides from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:31 [ERROR] Cannot find or open table sas_acetech/wp_revslider_static_slides_bkp from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:31 [Warning] '.\sas_acetech\wp_term_relationships' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_term_taxonomy' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_termmeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_terms' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_usermeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_users' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_wc_admin_note_actions' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_wc_admin_notes' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_wc_category_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_wc_customer_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_wc_download_log' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_acetech\wp_wc_download_log.frm'
250610 11:07:31 [Warning] '.\sas_acetech\wp_wc_order_coupon_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_wc_order_product_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_acetech\wp_wc_order_product_lookup.frm'
250610 11:07:31 [Warning] '.\sas_acetech\wp_wc_order_stats' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_acetech\wp_wc_order_stats.frm'
250610 11:07:31 [Warning] '.\sas_acetech\wp_wc_order_tax_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_wc_product_meta_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_wc_reserved_stock' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_wc_tax_rate_classes' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_wc_webhooks' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_woocommerce_api_keys' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_woocommerce_attribute_taxonomies' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_woocommerce_downloadable_product_permissions' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_woocommerce_log' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_woocommerce_order_itemmeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_woocommerce_order_items' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_woocommerce_payment_tokenmeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_woocommerce_payment_tokens' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_woocommerce_sessions' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_woocommerce_shipping_zone_locations' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_woocommerce_shipping_zone_methods' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_woocommerce_shipping_zones' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_woocommerce_tax_rate_locations' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_woocommerce_tax_rates' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_wpforms_payment_meta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_wpforms_payments' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_wpforms_tasks_meta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_wpmailsmtp_debug_events' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_wpmailsmtp_email_tracking_events' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_wpmailsmtp_email_tracking_links' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_wpmailsmtp_emails_log' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_wpmailsmtp_tasks_meta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [ERROR] Cannot find or open table sas_acetech/wp_wt_iew_action_history from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:31 [ERROR] Cannot find or open table sas_acetech/wp_wt_iew_cron from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:31 [ERROR] Cannot find or open table sas_acetech/wp_wt_iew_ftp from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:31 [ERROR] Cannot find or open table sas_acetech/wp_wt_iew_mapping_template from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:31 [Warning] '.\sas_acetech\wp_yoast_indexable' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_yoast_indexable_hierarchy' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_yoast_migrations' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [Warning] '.\sas_acetech\wp_yoast_primary_term' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:31 [ERROR] Cannot find or open table sas_acetech/wp_yoast_seo_links from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblactivity_log.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblannouncements.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblclients.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblconsent_purposes.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblconsents.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblcontact_permissions from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblcontacts.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblcontract_comments.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblcontract_renewals.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblcontracts.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblcontracts_types from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblcountries from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblcreditnote_refunds.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblcreditnotes.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblcredits.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblcurrencies from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblcustomer_admins from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblcustomer_groups from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblcustomers_groups from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblcustomfields from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblcustomfieldsvalues from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tbldepartments from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tbldismissed_announcements from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblemaillists.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblemailtemplates from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblestimate_request_forms.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblestimate_request_status from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblestimate_requests.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblestimates.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblevents.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblexpenses.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblexpenses_categories from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblfiles.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblfilter_defaults from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblfilters from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblform_question_box from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblform_question_box_description from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblform_questions from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblform_results from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblgdpr_requests.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblgoals from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblinvoicepaymentrecords.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblinvoices.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblitem_tax from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblitemable from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblitems from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblitems_groups from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblknowedge_base_article_feedback.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblknowledge_base.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblknowledge_base_groups from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbllead_activity_log.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbllead_integration_emails.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblleads.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblleads_email_integration from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblleads_sources from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblleads_status from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbllistemails.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblmail_queue.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblmaillistscustomfields from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblmaillistscustomfieldvalues from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblmigrations from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblmilestones from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblmodules from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblnewsfeed_comment_likes.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblnewsfeed_post_comments.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblnewsfeed_post_likes.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblnewsfeed_posts.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblnotes.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblnotifications.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tbloptions from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblpayment_attempts.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblpayment_modes from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblpinned_projects from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblproject_activity.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblproject_files.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblproject_members from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblproject_notes from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblproject_settings from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblprojectdiscussioncomments.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblprojectdiscussions.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblprojects.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblproposal_comments.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblproposals.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblrelated_items from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblreminders.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblroles from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblsales_activity.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblscheduled_emails.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblservices from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblsessions from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblshared_customer_files from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblspam_filters from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblstaff.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblstaff_departments from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblstaff_permissions from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblsubscriptions.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblsurveyresultsets.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblsurveys.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tblsurveysemailsendcron from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblsurveysendlog.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tbltaggables from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tbltags from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tbltask_assigned from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbltask_checklist_items.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbltask_comments.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tbltask_followers from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbltasks.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tbltasks_checklist_templates from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tbltaskstimers from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tbltaxes from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tbltemplates from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblticket_attachments.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblticket_replies.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbltickets.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbltickets_pipe_log.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tbltickets_predefined_replies from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tbltickets_priorities from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tbltickets_status from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbltodos.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbltracked_mails.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbltwocheckout_log.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbluser_auto_login.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_prefex2/tbluser_meta from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblvault.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblviews_tracking.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblweb_to_lead.frm'
250610 11:07:32 [Warning] '.\sas_yenfood\wp_actionscheduler_actions' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_actionscheduler_claims' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_actionscheduler_groups' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_actionscheduler_logs' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_chaty_contact_form_leads.frm'
250610 11:07:32 [Warning] '.\sas_yenfood\wp_commentmeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_comments' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_csshero5' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [ERROR] Cannot find or open table sas_yenfood/wp_fbv from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_yenfood/wp_fbv_attachment_folder from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [Warning] '.\sas_yenfood\wp_gla_budget_recommendations' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_gla_merchant_issues' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_gla_shipping_rates' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_gla_shipping_times' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_itsec_bans.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_itsec_dashboard_events.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_itsec_distributed_storage.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_itsec_fingerprints.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_itsec_geolocation_cache.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_itsec_lockouts.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_itsec_logs.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_yenfood/wp_itsec_mutexes from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_itsec_opaque_tokens.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_itsec_temp.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_itsec_user_groups.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_yenfood/wp_kbp_countdown_entry from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_kbp_form_entry.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_yenfood/wp_kbp_form_entrymeta from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [Warning] '.\sas_yenfood\wp_links' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [ERROR] Cannot find or open table sas_yenfood/wp_litespeed_url from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_yenfood/wp_litespeed_url_file from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_mailchimp_carts.frm'
250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_mailchimp_jobs.frm'
250610 11:07:32 [Warning] '.\sas_yenfood\wp_micro_revisions' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_options' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [ERROR] Cannot find or open table sas_yenfood/wp_post_views from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [Warning] '.\sas_yenfood\wp_postmeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_posts' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_term_relationships' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_term_taxonomy' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_termmeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_terms' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_usermeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_users' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_wc_admin_note_actions' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_wc_admin_notes' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_wc_category_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_wc_customer_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_wc_download_log' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_wc_order_coupon_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_wc_order_product_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_wc_order_stats' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_wc_order_tax_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_wc_product_meta_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_wc_rate_limits' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_wc_reserved_stock' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_wc_tax_rate_classes' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_wc_webhooks' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_woocommerce_api_keys' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_woocommerce_attribute_taxonomies' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_woocommerce_downloadable_product_permissions' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_woocommerce_log' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_woocommerce_order_itemmeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_woocommerce_order_items' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_woocommerce_payment_tokenmeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_woocommerce_payment_tokens' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_woocommerce_sessions' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_woocommerce_shipping_zone_locations' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_woocommerce_shipping_zone_methods' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_woocommerce_shipping_zones' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_woocommerce_tax_rate_locations' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [Warning] '.\sas_yenfood\wp_woocommerce_tax_rates' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:07:32 [ERROR] Cannot find or open table sas_yenfood/wp_wt_iew_action_history from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_yenfood/wp_wt_iew_cron from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_yenfood/wp_wt_iew_ftp from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_yenfood/wp_wt_iew_mapping_template from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_yoast_indexable.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_yenfood/wp_yoast_indexable_hierarchy from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_yenfood/wp_yoast_migrations from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_yoast_primary_term.frm'
250610 11:07:32 [ERROR] Cannot find or open table sas_yenfood/wp_yoast_seo_links from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:32 [ERROR] Cannot find or open table sas_yenfood/wp_ywcdd_calendar from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:07:38 [Warning] '.\sas_acetech\wp_commentmeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:08:32 [Warning] '.\sas_acetech\wp_fbv' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:08:41 [Warning] '.\sas_acetech\wp_posts' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:10:47 [Note] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Normal shutdown

250610 11:10:47 [Note] Event Scheduler: Purging the queue. 0 events
250610 11:10:47  InnoDB: Starting shutdown...
250610 11:10:47  InnoDB: Shutdown completed; log sequence number 1595675
250610 11:10:47 [Note] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Shutdown complete

250610 11:12:09 [Note] Plugin 'FEDERATED' is disabled.
250610 11:12:09 InnoDB: The InnoDB memory heap is disabled
250610 11:12:09 InnoDB: Mutexes and rw_locks use Windows interlocked functions
250610 11:12:09 InnoDB: Compressed tables use zlib 1.2.3
250610 11:12:09 InnoDB: Initializing buffer pool, size = 250.0M
250610 11:12:09 InnoDB: Completed initialization of buffer pool
250610 11:12:09 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
250610 11:12:09  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_actionscheduler_actions.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_actionscheduler_claims.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_actionscheduler_groups.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_actionscheduler_logs.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_commentmeta.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_comments.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_fbv.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_fbv_attachment_folder.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_fsmpt_email_logs.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_itsec_bans.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_itsec_dashboard_events.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_itsec_distributed_storage.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_itsec_fingerprints.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_itsec_geolocation_cache.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_itsec_lockouts.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_itsec_logs.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_itsec_mutexes.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_itsec_opaque_tokens.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_itsec_temp.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_itsec_user_groups.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_links.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_options.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_postmeta.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_posts.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_post_views.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_revslider_css.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_revslider_css_bkp.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_revslider_layer_animations.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_revslider_layer_animations_bkp.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_revslider_navigations.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_revslider_navigations_bkp.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_revslider_sliders.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_revslider_sliders_bkp.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_revslider_slides.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_revslider_slides_bkp.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_revslider_static_slides.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_revslider_static_slides_bkp.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_termmeta.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_terms.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_term_relationships.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_term_taxonomy.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_usermeta.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_users.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wc_admin_notes.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wc_admin_note_actions.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wc_category_lookup.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wc_customer_lookup.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wc_download_log.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wc_order_coupon_lookup.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wc_order_product_lookup.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wc_order_stats.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wc_order_tax_lookup.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wc_product_attributes_lookup.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wc_product_download_directories.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wc_product_meta_lookup.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wc_rate_limits.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wc_reserved_stock.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wc_tax_rate_classes.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wc_webhooks.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_woocommerce_api_keys.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_woocommerce_attribute_taxonomies.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_woocommerce_downloadable_product_permissions.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_woocommerce_log.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_woocommerce_order_itemmeta.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_woocommerce_order_items.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_woocommerce_payment_tokenmeta.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_woocommerce_payment_tokens.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_woocommerce_sessions.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_woocommerce_shipping_zones.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_woocommerce_shipping_zone_locations.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_woocommerce_shipping_zone_methods.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_woocommerce_tax_rates.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_woocommerce_tax_rate_locations.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wpforms_payments.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wpforms_payment_meta.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wpforms_tasks_meta.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wpmailsmtp_debug_events.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wpmailsmtp_emails_log.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wpmailsmtp_email_tracking_events.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wpmailsmtp_email_tracking_links.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wpmailsmtp_tasks_meta.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wt_iew_action_history.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wt_iew_cron.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wt_iew_ftp.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_wt_iew_mapping_template.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_yoast_indexable.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_yoast_indexable_hierarchy.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_yoast_migrations.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_yoast_primary_term.ibd
InnoDB: Error: checksum mismatch in file .\sas_acetech\wp_yoast_seo_links.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblactivity_log.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblannouncements.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblclients.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblconsents.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblconsent_purposes.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblcontacts.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblcontact_permissions.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblcontracts.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblcontracts_types.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblcontract_comments.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblcontract_renewals.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblcountries.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblcreditnotes.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblcreditnote_refunds.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblcredits.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblcurrencies.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblcustomers_groups.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblcustomer_admins.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblcustomer_groups.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblcustomfields.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblcustomfieldsvalues.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbldepartments.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbldismissed_announcements.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblemaillists.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblemailtemplates.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblestimates.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblestimate_requests.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblestimate_request_forms.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblestimate_request_status.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblevents.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblexpenses.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblexpenses_categories.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblfiles.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblfilters.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblfilter_defaults.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblform_questions.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblform_question_box.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblform_question_box_description.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblform_results.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblgdpr_requests.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblgoals.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblinvoicepaymentrecords.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblinvoices.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblitemable.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblitems.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblitems_groups.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblitem_tax.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblknowedge_base_article_feedback.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblknowledge_base.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblknowledge_base_groups.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblleads.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblleads_email_integration.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblleads_sources.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblleads_status.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbllead_activity_log.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbllead_integration_emails.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbllistemails.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblmaillistscustomfields.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblmaillistscustomfieldvalues.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblmail_queue.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblmigrations.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblmilestones.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblmodules.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblnewsfeed_comment_likes.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblnewsfeed_posts.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblnewsfeed_post_comments.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblnewsfeed_post_likes.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblnotes.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblnotifications.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbloptions.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblpayment_attempts.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblpayment_modes.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblpinned_projects.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblprojectdiscussioncomments.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblprojectdiscussions.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblprojects.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblproject_activity.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblproject_files.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblproject_members.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblproject_notes.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblproject_settings.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblproposals.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblproposal_comments.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblrelated_items.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblreminders.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblroles.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblsales_activity.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblscheduled_emails.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblservices.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblsessions.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblshared_customer_files.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblspam_filters.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblstaff.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblstaff_departments.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblstaff_permissions.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblsubscriptions.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblsurveyresultsets.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblsurveys.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblsurveysemailsendcron.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblsurveysendlog.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbltaggables.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbltags.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbltasks.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbltaskstimers.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbltasks_checklist_templates.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbltask_assigned.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbltask_checklist_items.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbltask_comments.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbltask_followers.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbltaxes.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbltemplates.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbltickets.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbltickets_pipe_log.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbltickets_predefined_replies.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbltickets_priorities.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbltickets_status.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblticket_attachments.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblticket_replies.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbltodos.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbltracked_mails.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbltwocheckout_log.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbluser_auto_login.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tbluser_meta.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblvault.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblviews_tracking.ibd
InnoDB: Error: checksum mismatch in file .\sas_prefex2\tblweb_to_lead.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_actionscheduler_actions.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_actionscheduler_claims.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_actionscheduler_groups.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_actionscheduler_logs.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_chaty_contact_form_leads.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_commentmeta.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_comments.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_csshero5.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_fbv.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_fbv_attachment_folder.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_gla_budget_recommendations.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_gla_merchant_issues.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_gla_shipping_rates.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_gla_shipping_times.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_itsec_bans.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_itsec_dashboard_events.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_itsec_distributed_storage.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_itsec_fingerprints.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_itsec_geolocation_cache.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_itsec_lockouts.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_itsec_logs.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_itsec_mutexes.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_itsec_opaque_tokens.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_itsec_temp.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_itsec_user_groups.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_kbp_countdown_entry.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_kbp_form_entry.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_kbp_form_entrymeta.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_links.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_litespeed_url.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_litespeed_url_file.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_mailchimp_carts.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_mailchimp_jobs.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_micro_revisions.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_options.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_postmeta.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_posts.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_post_views.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_termmeta.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_terms.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_term_relationships.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_term_taxonomy.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_usermeta.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_users.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_wc_admin_notes.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_wc_admin_note_actions.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_wc_category_lookup.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_wc_customer_lookup.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_wc_download_log.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_wc_order_coupon_lookup.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_wc_order_product_lookup.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_wc_order_stats.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_wc_order_tax_lookup.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_wc_product_meta_lookup.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_wc_rate_limits.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_wc_reserved_stock.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_wc_tax_rate_classes.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_wc_webhooks.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_woocommerce_api_keys.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_woocommerce_attribute_taxonomies.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_woocommerce_downloadable_product_permissions.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_woocommerce_log.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_woocommerce_order_itemmeta.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_woocommerce_order_items.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_woocommerce_payment_tokenmeta.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_woocommerce_payment_tokens.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_woocommerce_sessions.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_woocommerce_shipping_zones.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_woocommerce_shipping_zone_locations.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_woocommerce_shipping_zone_methods.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_woocommerce_tax_rates.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_woocommerce_tax_rate_locations.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_wt_iew_action_history.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_wt_iew_cron.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_wt_iew_ftp.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_wt_iew_mapping_template.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_yoast_indexable.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_yoast_indexable_hierarchy.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_yoast_migrations.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_yoast_primary_term.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_yoast_seo_links.ibd
InnoDB: Error: checksum mismatch in file .\sas_yenfood\wp_ywcdd_calendar.ibd
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
250610 11:12:09  InnoDB: Waiting for the background threads to start
250610 11:12:10 InnoDB: 5.5.60 started; log sequence number 1595685
250610 11:12:10 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
250610 11:12:10 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
250610 11:12:10 [Note] Server socket created on IP: '0.0.0.0'.
250610 11:12:10 [Note] Event Scheduler: Loaded 0 events
250610 11:12:10 [Note] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: ready for connections.
Version: '5.5.60'  socket: ''  port: 3306  MySQL Community Server (GPL)
250610 11:12:34 [Warning] '.\sas_acetech\wp_actionscheduler_actions' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_actionscheduler_claims' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_actionscheduler_groups' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_actionscheduler_logs' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_commentmeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_comments' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_fbv' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_fbv_attachment_folder' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_fsmpt_email_logs' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_itsec_bans' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_itsec_dashboard_events' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_itsec_distributed_storage' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_itsec_fingerprints' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_itsec_geolocation_cache' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_itsec_lockouts' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_itsec_logs' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_itsec_mutexes' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_itsec_opaque_tokens' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_itsec_temp' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_itsec_user_groups' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_links' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_options' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_post_views' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_postmeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_posts' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [ERROR] Cannot find or open table sas_acetech/wp_revslider_css from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_acetech/wp_revslider_css_bkp from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_acetech/wp_revslider_layer_animations from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_acetech/wp_revslider_layer_animations_bkp from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_acetech/wp_revslider_navigations from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_acetech/wp_revslider_navigations_bkp from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_acetech/wp_revslider_sliders from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_acetech/wp_revslider_sliders_bkp from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_acetech/wp_revslider_slides from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_acetech/wp_revslider_slides_bkp from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_acetech/wp_revslider_static_slides from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_acetech/wp_revslider_static_slides_bkp from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [Warning] '.\sas_acetech\wp_term_relationships' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_term_taxonomy' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_termmeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_terms' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_usermeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_users' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_wc_admin_note_actions' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_wc_admin_notes' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_wc_category_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_wc_customer_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_wc_download_log' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_acetech\wp_wc_download_log.frm'
250610 11:12:34 [Warning] '.\sas_acetech\wp_wc_order_coupon_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_wc_order_product_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_acetech\wp_wc_order_product_lookup.frm'
250610 11:12:34 [Warning] '.\sas_acetech\wp_wc_order_stats' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_acetech\wp_wc_order_stats.frm'
250610 11:12:34 [Warning] '.\sas_acetech\wp_wc_order_tax_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_wc_product_meta_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_wc_reserved_stock' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_wc_tax_rate_classes' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_wc_webhooks' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_woocommerce_api_keys' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_woocommerce_attribute_taxonomies' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_woocommerce_downloadable_product_permissions' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_woocommerce_log' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_woocommerce_order_itemmeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_woocommerce_order_items' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_woocommerce_payment_tokenmeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_woocommerce_payment_tokens' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_woocommerce_sessions' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_woocommerce_shipping_zone_locations' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_woocommerce_shipping_zone_methods' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_woocommerce_shipping_zones' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_woocommerce_tax_rate_locations' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_woocommerce_tax_rates' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_wpforms_payment_meta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_wpforms_payments' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_wpforms_tasks_meta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_wpmailsmtp_debug_events' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_wpmailsmtp_email_tracking_events' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_wpmailsmtp_email_tracking_links' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_wpmailsmtp_emails_log' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_wpmailsmtp_tasks_meta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [ERROR] Cannot find or open table sas_acetech/wp_wt_iew_action_history from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_acetech/wp_wt_iew_cron from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_acetech/wp_wt_iew_ftp from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_acetech/wp_wt_iew_mapping_template from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [Warning] '.\sas_acetech\wp_yoast_indexable' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_yoast_indexable_hierarchy' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_yoast_migrations' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [Warning] '.\sas_acetech\wp_yoast_primary_term' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:34 [ERROR] Cannot find or open table sas_acetech/wp_yoast_seo_links from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblactivity_log.frm'
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblannouncements.frm'
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblclients.frm'
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblconsent_purposes.frm'
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblconsents.frm'
250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblcontact_permissions from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblcontacts.frm'
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblcontract_comments.frm'
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblcontract_renewals.frm'
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblcontracts.frm'
250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblcontracts_types from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblcountries from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblcreditnote_refunds.frm'
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblcreditnotes.frm'
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblcredits.frm'
250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblcurrencies from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblcustomer_admins from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblcustomer_groups from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblcustomers_groups from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblcustomfields from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblcustomfieldsvalues from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tbldepartments from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tbldismissed_announcements from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblemaillists.frm'
250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblemailtemplates from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblestimate_request_forms.frm'
250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblestimate_request_status from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblestimate_requests.frm'
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblestimates.frm'
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblevents.frm'
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblexpenses.frm'
250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblexpenses_categories from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblfiles.frm'
250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblfilter_defaults from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblfilters from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblform_question_box from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblform_question_box_description from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblform_questions from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblform_results from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblgdpr_requests.frm'
250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblgoals from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblinvoicepaymentrecords.frm'
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblinvoices.frm'
250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblitem_tax from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblitemable from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblitems from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblitems_groups from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblknowedge_base_article_feedback.frm'
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblknowledge_base.frm'
250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblknowledge_base_groups from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbllead_activity_log.frm'
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbllead_integration_emails.frm'
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblleads.frm'
250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblleads_email_integration from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblleads_sources from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblleads_status from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbllistemails.frm'
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblmail_queue.frm'
250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblmaillistscustomfields from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblmaillistscustomfieldvalues from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblmigrations from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblmilestones from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tblmodules from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblnewsfeed_comment_likes.frm'
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblnewsfeed_post_comments.frm'
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblnewsfeed_post_likes.frm'
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblnewsfeed_posts.frm'
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblnotes.frm'
250610 11:12:34 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblnotifications.frm'
250610 11:12:34 [ERROR] Cannot find or open table sas_prefex2/tbloptions from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblpayment_attempts.frm'
250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tblpayment_modes from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tblpinned_projects from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblproject_activity.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblproject_files.frm'
250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tblproject_members from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tblproject_notes from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tblproject_settings from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblprojectdiscussioncomments.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblprojectdiscussions.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblprojects.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblproposal_comments.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblproposals.frm'
250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tblrelated_items from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblreminders.frm'
250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tblroles from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblsales_activity.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblscheduled_emails.frm'
250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tblservices from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tblsessions from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tblshared_customer_files from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tblspam_filters from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblstaff.frm'
250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tblstaff_departments from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tblstaff_permissions from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblsubscriptions.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblsurveyresultsets.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblsurveys.frm'
250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tblsurveysemailsendcron from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblsurveysendlog.frm'
250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tbltaggables from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tbltags from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tbltask_assigned from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbltask_checklist_items.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbltask_comments.frm'
250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tbltask_followers from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbltasks.frm'
250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tbltasks_checklist_templates from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tbltaskstimers from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tbltaxes from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tbltemplates from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblticket_attachments.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblticket_replies.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbltickets.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbltickets_pipe_log.frm'
250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tbltickets_predefined_replies from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tbltickets_priorities from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tbltickets_status from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbltodos.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbltracked_mails.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbltwocheckout_log.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tbluser_auto_login.frm'
250610 11:12:35 [ERROR] Cannot find or open table sas_prefex2/tbluser_meta from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblvault.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblviews_tracking.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_prefex2\tblweb_to_lead.frm'
250610 11:12:35 [Warning] '.\sas_yenfood\wp_actionscheduler_actions' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_actionscheduler_claims' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_actionscheduler_groups' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_actionscheduler_logs' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_chaty_contact_form_leads.frm'
250610 11:12:35 [Warning] '.\sas_yenfood\wp_commentmeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_comments' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_csshero5' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [ERROR] Cannot find or open table sas_yenfood/wp_fbv from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] Cannot find or open table sas_yenfood/wp_fbv_attachment_folder from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [Warning] '.\sas_yenfood\wp_gla_budget_recommendations' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_gla_merchant_issues' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_gla_shipping_rates' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_gla_shipping_times' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_itsec_bans.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_itsec_dashboard_events.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_itsec_distributed_storage.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_itsec_fingerprints.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_itsec_geolocation_cache.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_itsec_lockouts.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_itsec_logs.frm'
250610 11:12:35 [ERROR] Cannot find or open table sas_yenfood/wp_itsec_mutexes from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_itsec_opaque_tokens.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_itsec_temp.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_itsec_user_groups.frm'
250610 11:12:35 [ERROR] Cannot find or open table sas_yenfood/wp_kbp_countdown_entry from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_kbp_form_entry.frm'
250610 11:12:35 [ERROR] Cannot find or open table sas_yenfood/wp_kbp_form_entrymeta from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [Warning] '.\sas_yenfood\wp_links' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [ERROR] Cannot find or open table sas_yenfood/wp_litespeed_url from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] Cannot find or open table sas_yenfood/wp_litespeed_url_file from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_mailchimp_carts.frm'
250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_mailchimp_jobs.frm'
250610 11:12:35 [Warning] '.\sas_yenfood\wp_micro_revisions' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_options' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [ERROR] Cannot find or open table sas_yenfood/wp_post_views from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [Warning] '.\sas_yenfood\wp_postmeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_posts' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_term_relationships' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_term_taxonomy' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_termmeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_terms' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_usermeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_users' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_wc_admin_note_actions' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_wc_admin_notes' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_wc_category_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_wc_customer_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_wc_download_log' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_wc_order_coupon_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_wc_order_product_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_wc_order_stats' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_wc_order_tax_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_wc_product_meta_lookup' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_wc_rate_limits' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_wc_reserved_stock' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_wc_tax_rate_classes' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_wc_webhooks' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_woocommerce_api_keys' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_woocommerce_attribute_taxonomies' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_woocommerce_downloadable_product_permissions' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_woocommerce_log' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_woocommerce_order_itemmeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_woocommerce_order_items' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_woocommerce_payment_tokenmeta' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_woocommerce_payment_tokens' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_woocommerce_sessions' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_woocommerce_shipping_zone_locations' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_woocommerce_shipping_zone_methods' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_woocommerce_shipping_zones' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_woocommerce_tax_rate_locations' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [Warning] '.\sas_yenfood\wp_woocommerce_tax_rates' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:35 [ERROR] Cannot find or open table sas_yenfood/wp_wt_iew_action_history from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] Cannot find or open table sas_yenfood/wp_wt_iew_cron from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] Cannot find or open table sas_yenfood/wp_wt_iew_ftp from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] Cannot find or open table sas_yenfood/wp_wt_iew_mapping_template from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_yoast_indexable.frm'
250610 11:12:35 [ERROR] Cannot find or open table sas_yenfood/wp_yoast_indexable_hierarchy from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] Cannot find or open table sas_yenfood/wp_yoast_migrations from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Incorrect information in file: '.\sas_yenfood\wp_yoast_primary_term.frm'
250610 11:12:35 [ERROR] Cannot find or open table sas_yenfood/wp_yoast_seo_links from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:35 [ERROR] Cannot find or open table sas_yenfood/wp_ywcdd_calendar from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

250610 11:12:39 [Warning] '.\sas_acetech\wp_actionscheduler_logs' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:12:48 [Warning] '.\sas_acetech\wp_post_views' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed
250610 11:15:45 [Note] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Normal shutdown

250610 11:15:45 [Note] Event Scheduler: Purging the queue. 0 events
250610 11:15:47 [Warning] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Forcing close of thread 3  user: 'root'

250610 11:15:47 [Warning] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Forcing close of thread 2  user: 'root'

250610 11:15:47  InnoDB: Starting shutdown...
250610 11:15:48  InnoDB: Shutdown completed; log sequence number 1595685
250610 11:15:48 [Note] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Shutdown complete