Fatal Error on Woocommerce after migration

  • Resolved johndalt

    (@johndalt)


    2 years, 9 months ago

    Hi there,

    I’ve used your plugin for several migrations successfully. This time I need to migrate a clone of a WooCommerce website to a subdomain in order to serve a specific country (India).

    The migration went well, everything was working and I deactivated the non-applicable plugins. However, after a while the site crashed with a “Fatal error: Uncaught RuntimeException: Error saving action: Error saving action: INSERT command denied to user ‘xxx’@’xxx’ for table ‘wp_actionscheduler_actions'”, and highlighting the line “store(Object(ActionScheduler_Action)) in xxx/wp-content/plugins/woocommerce/packages/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php on line 44”

    Is this related to Prime Mover or should I ask for help on WooCommerce? Any help will be appreciated.

    Thanks in advance,
    John

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Codexonics

    (@codexonics)

    Hi John,
    Thank you for using Prime Mover in your projects! Since the site is now migrated and every thing is working – Migration code does not anymore run at this stage. So this is not something related to Prime Mover. We also don’t find this reproduced in our test site.

    Looking at the error – it looks like it has something to do with WooCommerce ActionScheduler table. Maybe it would help refreshing the Scheduled action table to see if it works. Simply go to WooCommerce -> Status -> Scheduled Actions. Visiting this page will auto-refresh scheduled actions table.

    WooCommerce also includes several tools to refresh data. You can find this in WooCommerce -> Status -> Tools. Sometimes these data are cached and stay in the database which could result intermittent errors after a migration. So using these tools will help clearing things up and adjust to it’s latest state.

    These are just suggestions if you could encounter this error. And it’s recommended to backup your database before using these tools – to be sure. However it would be helpful if could share this error to WooCommerce support to get their input on this error. Maybe it’s a just caused by residual cached data after migration (which are cleared using WooCommmerce tools).

    If these things help and you don’t need anymore technical assistance. Please marked this ticket as resolved. Thank you!

    Cheers,
    Emerson

    Thread Starter johndalt

    (@johndalt)

    Hi Emerson,

    Thank you so much for the prompt reply.

    I’ll try the above, although everything breaks when WooCommerce is activated. I’ll contact their support also.

    Thanks again,
    John

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Fatal Error on Woocommerce after migration’ is closed to new replies.