2

When upgrading a site from Magento 2.2.6 to 2.3.0, the following error occurs during setup:upgrade

...
Module 'Magento_AdminNotification':
Module 'Magento_Search':
Module 'Magento_Amqp':
Running schema recurring...
Module 'Magento_Config':
Module 'Magento_User':
Module 'Magento_Authorization':
Module 'Magento_Indexer':
Running schema recurring...Constraint "email_order_to_sales_order" references table that does not exist.
1
  • Do you install any third-party module? I think you should disable all of them and try run s:up once again
    – bachlee89
    Dec 20, 2018 at 23:17

1 Answer 1

7

This problem occurs when running the setup:upgrade command while having the newer Dotdigitalgroup_Enterprise module enabled and the Dotdigitalgroup_Email module disabled.

Prior to this Enterprise module the Dotdigitalgroup_Email was not compatible with the split database setup that Magento2 Commerce offers, but this doesn't have to be the reason for disabling the Email module.

2
  • For me, it worked when I disable Dotdigitalgroup_Enterprise and run the setup upgrade. Then enable it and again run the setup upgrade Apr 26, 2022 at 7:53
  • Hi Bas, nice to see you here! I've had the same problem but in my case it was because Elasticsearch somehow fell asleep. Simply restarting elasticsearch and running set:up again solved it for me.
    – bdbdbd
    Nov 27, 2023 at 10:51

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.