3

I migrate settings from Magento 1.9.3.10 to Magento 2.3, after the migration was successful when I try to reindex or flush de cache from command line I have this error:

  The website with id 0 that was requested wasn't found. Verify the website a
  nd try again.

Also in the exception.log file I see this error:

main.CRITICAL: The website with id 0 that was requested wasn't found. Verify the website and try again. {"exception":"[object] (Magento\\Framework\\Exception\\NoSuchEntityException(code: 0): The website with id 0 that was requested wasn't found. Verify the website and try again. at /var/www/clients/client0/web15/web/vendor/magento/module-store/Model/WebsiteRepository.php:110)"} []

What I can do to fix this? or what can be the problem?

Thank you

enter image description here

Core_config_data with the scope=websites

enter image description here

Improve this question
7
  • So have you tried migration in empty Magento 2 instance? From error I can guess something in core_config data is pointing to a website with id 0 whereas the website id doesn't exist. Can you please share your store_website table
    – Raj Mohan R
    Jul 2, 2019 at 12:22
  • @RajMohanR indeed I migrate the settings in a empty Magento 2.3.2 instance. I edit my post and I add the store_website table, can you check please?
    – Robert
    Jul 2, 2019 at 12:26
  • There is no website with website id 0. Can you please check in core_config data if there some config for website id 0\
    – Raj Mohan R
    Jul 2, 2019 at 12:28
  • @RajMohanR how I can check this?
    – Robert
    Jul 2, 2019 at 12:30
  • 1
    @RajMohanR indeed you have right I change the scope_id for a few fields and everything seems to be fine now
    – Robert
    Jul 2, 2019 at 12:51

1 Answer 1

Reset to default
4

Please check the website ID. Some of the configurations are there for the website with ID 0 which we can conclude from the error message. So check your store_website table. If there is no website with website_id 0, please check your core_config_data table for configurations with scope_id 0. You can manually change those to solve this issue at the go. Moreover please check for those configurations in Magento 1 with scope_id 0. It will give an idea about the scope_id mismatch.

Improve this answer

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.