Magento 2: Requested store is not foundcannot read property 'section loadurl' of undefinedMagento 2.3.0 - The store that was requested wasn't foundRequested store is not foundRequested store not foundMultistore - Magento 2 SetupConfigurable product does not have sub-products magento 2Magento 2: ACL Permission Call Manually for Logged In AdminMagento Upgrade to 2.1.3 Module Disable ErrorMagento 2: Captcha overwrite fatal error on PHP 7Found error when customer tried to login inPDOException: SQLSTATE[HY000] [1698] Access denied for user 'root'@'localhost'Magento2.2.4 : Uninstall a theme throw exceptions?Magento 2: Requested store is not found in productError after upgraded to 2.3.0

Why can my keyboard only digest 6 keypresses at a time?

1980s live-action movie where individually-coloured nations on clouds fight

Pre-1972 sci-fi short story or novel: alien(?) tunnel where people try new moves and get destroyed if they're not the correct ones

How to hide rifle during medieval town entrance inspection?

Is it expected that a reader will skip parts of what you write?

Soft question: Examples where lack of mathematical rigour cause security breaches?

Is it possible to have a wealthy country without a middle class?

Arriving at the same result with the opposite hypotheses

Fixing obscure 8080 emulator bug?

Electricity free spaceship

How to handle self harm scars on the arm in work environment?

Active low-pass filters --- good to what frequencies?

Rebus with 20 song titles

Were Alexander the Great and Hephaestion lovers?

What makes Ada the language of choice for the ISS's safety-critical systems?

How did old MS-DOS games utilize various graphic cards?

Cascading Switches. Will it affect performance?

Extreme flexible working hours: how to control people and activities?

Why didn't Voldemort recognize that Dumbledore was affected by his curse?

Wooden cooking layout

Jargon request: "Canonical Form" of a word

Playing a Character as Unobtrusive and Subservient, Yet Not Passive

How can this tool find out registered domains from an IP?

Bent Peugeot Carbolite 103 Frame



Magento 2: Requested store is not found


cannot read property 'section loadurl' of undefinedMagento 2.3.0 - The store that was requested wasn't foundRequested store is not foundRequested store not foundMultistore - Magento 2 SetupConfigurable product does not have sub-products magento 2Magento 2: ACL Permission Call Manually for Logged In AdminMagento Upgrade to 2.1.3 Module Disable ErrorMagento 2: Captcha overwrite fatal error on PHP 7Found error when customer tried to login inPDOException: SQLSTATE[HY000] [1698] Access denied for user 'root'@'localhost'Magento2.2.4 : Uninstall a theme throw exceptions?Magento 2: Requested store is not found in productError after upgraded to 2.3.0






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








1















I had two websites with different store and storeviews. I just deleted one website which is not the default one. After deleting it the admin panel page and also the front page shows this error



exception 'MagentoFrameworkExceptionNoSuchEntityException' with message 'Requested store is not found' in C:wampwwwmagentovendormagentomodule-storeModelStoreRepository.php:111 Stack trace: #0 

C:wampwwwmagentovendormagentomodule-storeModelStoreManager.php(164): MagentoStoreModelStoreRepository->getById('2') #1 C:wampwwwmagentovargenerationMagentoStoreModelStoreManagerInterfaceProxy.php(119): MagentoStoreModelStoreManager->getStore('2') #2 C:wampwwwmagentovendormagentomodule-storeModelResolverStore.php(29): MagentoStoreModelStoreManagerInterfaceProxy->getStore('2') #3 C:wampwwwmagentovendormagentoframeworkAppConfigScopeCodeResolver.php(49): MagentoStoreModelResolverStore->getScope('2') #4 C:wampwwwmagentovendormagentomodule-configAppConfigSourceRuntimeConfigSource.php(82): MagentoFrameworkAppConfigScopeCodeResolver->resolve('stores', '2') #5 C:wampwwwmagentovendormagentomodule-configAppConfigSourceRuntimeConfigSource.php(58): MagentoConfigAppConfigSourceRuntimeConfigSource->loadConfig() #6 C:wampwwwmagentovendormagentoframeworkAppConfigConfigSourceAggregated.php(40): MagentoConfigAppConfigSourceRuntimeConfigSource->get('') #7 C:wampwwwmagentovargenerationMagentoFrameworkAppConfigConfigSourceAggregatedProxy.php(95): MagentoFrameworkAppConfigConfigSourceAggregated->get('') #8 C:wampwwwmagentovendormagentomodule-configAppConfigTypeSystem.php(98): MagentoFrameworkAppConfigConfigSourceAggregatedProxy->get() #9 C:wampwwwmagentovendormagentoframeworkAppConfig.php(139): MagentoConfigAppConfigTypeSystem->get('default/web/sec...') #10 C:wampwwwmagentovendormagentoframeworkAppConfig.php(90): MagentoFrameworkAppConfig->get('system', 'default/web/sec...') #11 C:wampwwwmagentovendormagentoframeworkAppConfig.php(103): MagentoFrameworkAppConfig->getValue('web/secure/use_...', 'default', NULL) #12 C:wampwwwmagentovendormagentomodule-storeModelHeaderProviderHsts.php(48): MagentoFrameworkAppConfig->isSetFlag('web/secure/use_...') #13 C:wampwwwmagentovendormagentoframeworkAppResponseHeaderManager.php(41): MagentoStoreModelHeaderProviderHsts->canApply() #14 C:wampwwwmagentovendormagentoframeworkInterceptionInterceptor.php(123): MagentoFrameworkAppResponseHeaderManager->beforeSendResponse(Object(MagentoFrameworkAppResponseHttpInterceptor)) #15 C:wampwwwmagentovargenerationMagentoFrameworkAppResponseHttpInterceptor.php(117): MagentoFrameworkAppResponseHttpInterceptor->___callPlugins('sendResponse', Array, Array) #16 C:wampwwwmagentovendormagentoframeworkAppHttp.php(185): MagentoFrameworkAppResponseHttpInterceptor->sendResponse() #17 C:wampwwwmagentovendormagentoframeworkAppHttp.php(156): MagentoFrameworkAppHttp->handleDeveloperMode(Object(MagentoFrameworkAppBootstrap), Object(MagentoFrameworkExceptionNoSuchEntityException)) #18 C:wampwwwmagentovendormagentoframeworkAppBootstrap.php(263): MagentoFrameworkAppHttp->catchException(Object(MagentoFrameworkAppBootstrap), Object(MagentoFrameworkExceptionNoSuchEntityException)) #19 C:wampwwwmagentoindex.php(39): MagentoFrameworkAppBootstrap->run(Object(MagentoFrameworkAppHttp)) #20 main


What should I do now? I tried



php bin/magento setup:upgrade
php bin/magento setup:static-content:deploy
php bin/magento indexer:reindex


from command prompt. But it shows the same error in command prompt also. The cmd error is :



C:wampbinphpphp5.6.30>php C:wampwwwmagentobinmagento indexer:reindex
Xdebug requires Zend Engine API version 220121212.
The Zend Engine API version 220131226 which is installed, is newer.
Contact Derick Rethans at http://xdebug.org/docs/faq#api for a later version of Xdebug.




[MagentoFrameworkExceptionNoSuchEntityException]
Requested store is not found



indexer:reindex [index1] ... [indexN]









share|improve this question
























  • Remove var folder and check it again.

    – Suresh Chikani
    Jan 24 '17 at 10:33












  • share the error which command promt show to you.

    – Dhiren Vasoya
    Jan 25 '17 at 3:04











  • @DhirenVasoya : Added the error in question

    – Zammuuz
    Jan 25 '17 at 4:22

















1















I had two websites with different store and storeviews. I just deleted one website which is not the default one. After deleting it the admin panel page and also the front page shows this error



exception 'MagentoFrameworkExceptionNoSuchEntityException' with message 'Requested store is not found' in C:wampwwwmagentovendormagentomodule-storeModelStoreRepository.php:111 Stack trace: #0 

C:wampwwwmagentovendormagentomodule-storeModelStoreManager.php(164): MagentoStoreModelStoreRepository->getById('2') #1 C:wampwwwmagentovargenerationMagentoStoreModelStoreManagerInterfaceProxy.php(119): MagentoStoreModelStoreManager->getStore('2') #2 C:wampwwwmagentovendormagentomodule-storeModelResolverStore.php(29): MagentoStoreModelStoreManagerInterfaceProxy->getStore('2') #3 C:wampwwwmagentovendormagentoframeworkAppConfigScopeCodeResolver.php(49): MagentoStoreModelResolverStore->getScope('2') #4 C:wampwwwmagentovendormagentomodule-configAppConfigSourceRuntimeConfigSource.php(82): MagentoFrameworkAppConfigScopeCodeResolver->resolve('stores', '2') #5 C:wampwwwmagentovendormagentomodule-configAppConfigSourceRuntimeConfigSource.php(58): MagentoConfigAppConfigSourceRuntimeConfigSource->loadConfig() #6 C:wampwwwmagentovendormagentoframeworkAppConfigConfigSourceAggregated.php(40): MagentoConfigAppConfigSourceRuntimeConfigSource->get('') #7 C:wampwwwmagentovargenerationMagentoFrameworkAppConfigConfigSourceAggregatedProxy.php(95): MagentoFrameworkAppConfigConfigSourceAggregated->get('') #8 C:wampwwwmagentovendormagentomodule-configAppConfigTypeSystem.php(98): MagentoFrameworkAppConfigConfigSourceAggregatedProxy->get() #9 C:wampwwwmagentovendormagentoframeworkAppConfig.php(139): MagentoConfigAppConfigTypeSystem->get('default/web/sec...') #10 C:wampwwwmagentovendormagentoframeworkAppConfig.php(90): MagentoFrameworkAppConfig->get('system', 'default/web/sec...') #11 C:wampwwwmagentovendormagentoframeworkAppConfig.php(103): MagentoFrameworkAppConfig->getValue('web/secure/use_...', 'default', NULL) #12 C:wampwwwmagentovendormagentomodule-storeModelHeaderProviderHsts.php(48): MagentoFrameworkAppConfig->isSetFlag('web/secure/use_...') #13 C:wampwwwmagentovendormagentoframeworkAppResponseHeaderManager.php(41): MagentoStoreModelHeaderProviderHsts->canApply() #14 C:wampwwwmagentovendormagentoframeworkInterceptionInterceptor.php(123): MagentoFrameworkAppResponseHeaderManager->beforeSendResponse(Object(MagentoFrameworkAppResponseHttpInterceptor)) #15 C:wampwwwmagentovargenerationMagentoFrameworkAppResponseHttpInterceptor.php(117): MagentoFrameworkAppResponseHttpInterceptor->___callPlugins('sendResponse', Array, Array) #16 C:wampwwwmagentovendormagentoframeworkAppHttp.php(185): MagentoFrameworkAppResponseHttpInterceptor->sendResponse() #17 C:wampwwwmagentovendormagentoframeworkAppHttp.php(156): MagentoFrameworkAppHttp->handleDeveloperMode(Object(MagentoFrameworkAppBootstrap), Object(MagentoFrameworkExceptionNoSuchEntityException)) #18 C:wampwwwmagentovendormagentoframeworkAppBootstrap.php(263): MagentoFrameworkAppHttp->catchException(Object(MagentoFrameworkAppBootstrap), Object(MagentoFrameworkExceptionNoSuchEntityException)) #19 C:wampwwwmagentoindex.php(39): MagentoFrameworkAppBootstrap->run(Object(MagentoFrameworkAppHttp)) #20 main


What should I do now? I tried



php bin/magento setup:upgrade
php bin/magento setup:static-content:deploy
php bin/magento indexer:reindex


from command prompt. But it shows the same error in command prompt also. The cmd error is :



C:wampbinphpphp5.6.30>php C:wampwwwmagentobinmagento indexer:reindex
Xdebug requires Zend Engine API version 220121212.
The Zend Engine API version 220131226 which is installed, is newer.
Contact Derick Rethans at http://xdebug.org/docs/faq#api for a later version of Xdebug.




[MagentoFrameworkExceptionNoSuchEntityException]
Requested store is not found



indexer:reindex [index1] ... [indexN]









share|improve this question
























  • Remove var folder and check it again.

    – Suresh Chikani
    Jan 24 '17 at 10:33












  • share the error which command promt show to you.

    – Dhiren Vasoya
    Jan 25 '17 at 3:04











  • @DhirenVasoya : Added the error in question

    – Zammuuz
    Jan 25 '17 at 4:22













1












1








1


0






I had two websites with different store and storeviews. I just deleted one website which is not the default one. After deleting it the admin panel page and also the front page shows this error



exception 'MagentoFrameworkExceptionNoSuchEntityException' with message 'Requested store is not found' in C:wampwwwmagentovendormagentomodule-storeModelStoreRepository.php:111 Stack trace: #0 

C:wampwwwmagentovendormagentomodule-storeModelStoreManager.php(164): MagentoStoreModelStoreRepository->getById('2') #1 C:wampwwwmagentovargenerationMagentoStoreModelStoreManagerInterfaceProxy.php(119): MagentoStoreModelStoreManager->getStore('2') #2 C:wampwwwmagentovendormagentomodule-storeModelResolverStore.php(29): MagentoStoreModelStoreManagerInterfaceProxy->getStore('2') #3 C:wampwwwmagentovendormagentoframeworkAppConfigScopeCodeResolver.php(49): MagentoStoreModelResolverStore->getScope('2') #4 C:wampwwwmagentovendormagentomodule-configAppConfigSourceRuntimeConfigSource.php(82): MagentoFrameworkAppConfigScopeCodeResolver->resolve('stores', '2') #5 C:wampwwwmagentovendormagentomodule-configAppConfigSourceRuntimeConfigSource.php(58): MagentoConfigAppConfigSourceRuntimeConfigSource->loadConfig() #6 C:wampwwwmagentovendormagentoframeworkAppConfigConfigSourceAggregated.php(40): MagentoConfigAppConfigSourceRuntimeConfigSource->get('') #7 C:wampwwwmagentovargenerationMagentoFrameworkAppConfigConfigSourceAggregatedProxy.php(95): MagentoFrameworkAppConfigConfigSourceAggregated->get('') #8 C:wampwwwmagentovendormagentomodule-configAppConfigTypeSystem.php(98): MagentoFrameworkAppConfigConfigSourceAggregatedProxy->get() #9 C:wampwwwmagentovendormagentoframeworkAppConfig.php(139): MagentoConfigAppConfigTypeSystem->get('default/web/sec...') #10 C:wampwwwmagentovendormagentoframeworkAppConfig.php(90): MagentoFrameworkAppConfig->get('system', 'default/web/sec...') #11 C:wampwwwmagentovendormagentoframeworkAppConfig.php(103): MagentoFrameworkAppConfig->getValue('web/secure/use_...', 'default', NULL) #12 C:wampwwwmagentovendormagentomodule-storeModelHeaderProviderHsts.php(48): MagentoFrameworkAppConfig->isSetFlag('web/secure/use_...') #13 C:wampwwwmagentovendormagentoframeworkAppResponseHeaderManager.php(41): MagentoStoreModelHeaderProviderHsts->canApply() #14 C:wampwwwmagentovendormagentoframeworkInterceptionInterceptor.php(123): MagentoFrameworkAppResponseHeaderManager->beforeSendResponse(Object(MagentoFrameworkAppResponseHttpInterceptor)) #15 C:wampwwwmagentovargenerationMagentoFrameworkAppResponseHttpInterceptor.php(117): MagentoFrameworkAppResponseHttpInterceptor->___callPlugins('sendResponse', Array, Array) #16 C:wampwwwmagentovendormagentoframeworkAppHttp.php(185): MagentoFrameworkAppResponseHttpInterceptor->sendResponse() #17 C:wampwwwmagentovendormagentoframeworkAppHttp.php(156): MagentoFrameworkAppHttp->handleDeveloperMode(Object(MagentoFrameworkAppBootstrap), Object(MagentoFrameworkExceptionNoSuchEntityException)) #18 C:wampwwwmagentovendormagentoframeworkAppBootstrap.php(263): MagentoFrameworkAppHttp->catchException(Object(MagentoFrameworkAppBootstrap), Object(MagentoFrameworkExceptionNoSuchEntityException)) #19 C:wampwwwmagentoindex.php(39): MagentoFrameworkAppBootstrap->run(Object(MagentoFrameworkAppHttp)) #20 main


What should I do now? I tried



php bin/magento setup:upgrade
php bin/magento setup:static-content:deploy
php bin/magento indexer:reindex


from command prompt. But it shows the same error in command prompt also. The cmd error is :



C:wampbinphpphp5.6.30>php C:wampwwwmagentobinmagento indexer:reindex
Xdebug requires Zend Engine API version 220121212.
The Zend Engine API version 220131226 which is installed, is newer.
Contact Derick Rethans at http://xdebug.org/docs/faq#api for a later version of Xdebug.




[MagentoFrameworkExceptionNoSuchEntityException]
Requested store is not found



indexer:reindex [index1] ... [indexN]









share|improve this question
















I had two websites with different store and storeviews. I just deleted one website which is not the default one. After deleting it the admin panel page and also the front page shows this error



exception 'MagentoFrameworkExceptionNoSuchEntityException' with message 'Requested store is not found' in C:wampwwwmagentovendormagentomodule-storeModelStoreRepository.php:111 Stack trace: #0 

C:wampwwwmagentovendormagentomodule-storeModelStoreManager.php(164): MagentoStoreModelStoreRepository->getById('2') #1 C:wampwwwmagentovargenerationMagentoStoreModelStoreManagerInterfaceProxy.php(119): MagentoStoreModelStoreManager->getStore('2') #2 C:wampwwwmagentovendormagentomodule-storeModelResolverStore.php(29): MagentoStoreModelStoreManagerInterfaceProxy->getStore('2') #3 C:wampwwwmagentovendormagentoframeworkAppConfigScopeCodeResolver.php(49): MagentoStoreModelResolverStore->getScope('2') #4 C:wampwwwmagentovendormagentomodule-configAppConfigSourceRuntimeConfigSource.php(82): MagentoFrameworkAppConfigScopeCodeResolver->resolve('stores', '2') #5 C:wampwwwmagentovendormagentomodule-configAppConfigSourceRuntimeConfigSource.php(58): MagentoConfigAppConfigSourceRuntimeConfigSource->loadConfig() #6 C:wampwwwmagentovendormagentoframeworkAppConfigConfigSourceAggregated.php(40): MagentoConfigAppConfigSourceRuntimeConfigSource->get('') #7 C:wampwwwmagentovargenerationMagentoFrameworkAppConfigConfigSourceAggregatedProxy.php(95): MagentoFrameworkAppConfigConfigSourceAggregated->get('') #8 C:wampwwwmagentovendormagentomodule-configAppConfigTypeSystem.php(98): MagentoFrameworkAppConfigConfigSourceAggregatedProxy->get() #9 C:wampwwwmagentovendormagentoframeworkAppConfig.php(139): MagentoConfigAppConfigTypeSystem->get('default/web/sec...') #10 C:wampwwwmagentovendormagentoframeworkAppConfig.php(90): MagentoFrameworkAppConfig->get('system', 'default/web/sec...') #11 C:wampwwwmagentovendormagentoframeworkAppConfig.php(103): MagentoFrameworkAppConfig->getValue('web/secure/use_...', 'default', NULL) #12 C:wampwwwmagentovendormagentomodule-storeModelHeaderProviderHsts.php(48): MagentoFrameworkAppConfig->isSetFlag('web/secure/use_...') #13 C:wampwwwmagentovendormagentoframeworkAppResponseHeaderManager.php(41): MagentoStoreModelHeaderProviderHsts->canApply() #14 C:wampwwwmagentovendormagentoframeworkInterceptionInterceptor.php(123): MagentoFrameworkAppResponseHeaderManager->beforeSendResponse(Object(MagentoFrameworkAppResponseHttpInterceptor)) #15 C:wampwwwmagentovargenerationMagentoFrameworkAppResponseHttpInterceptor.php(117): MagentoFrameworkAppResponseHttpInterceptor->___callPlugins('sendResponse', Array, Array) #16 C:wampwwwmagentovendormagentoframeworkAppHttp.php(185): MagentoFrameworkAppResponseHttpInterceptor->sendResponse() #17 C:wampwwwmagentovendormagentoframeworkAppHttp.php(156): MagentoFrameworkAppHttp->handleDeveloperMode(Object(MagentoFrameworkAppBootstrap), Object(MagentoFrameworkExceptionNoSuchEntityException)) #18 C:wampwwwmagentovendormagentoframeworkAppBootstrap.php(263): MagentoFrameworkAppHttp->catchException(Object(MagentoFrameworkAppBootstrap), Object(MagentoFrameworkExceptionNoSuchEntityException)) #19 C:wampwwwmagentoindex.php(39): MagentoFrameworkAppBootstrap->run(Object(MagentoFrameworkAppHttp)) #20 main


What should I do now? I tried



php bin/magento setup:upgrade
php bin/magento setup:static-content:deploy
php bin/magento indexer:reindex


from command prompt. But it shows the same error in command prompt also. The cmd error is :



C:wampbinphpphp5.6.30>php C:wampwwwmagentobinmagento indexer:reindex
Xdebug requires Zend Engine API version 220121212.
The Zend Engine API version 220131226 which is installed, is newer.
Contact Derick Rethans at http://xdebug.org/docs/faq#api for a later version of Xdebug.




[MagentoFrameworkExceptionNoSuchEntityException]
Requested store is not found



indexer:reindex [index1] ... [indexN]






websites exception stores magento-2.1.3






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 20 '17 at 18:34









Rafael Corrêa Gomes

4,88523367




4,88523367










asked Jan 24 '17 at 10:25









ZammuuzZammuuz

2121314




2121314












  • Remove var folder and check it again.

    – Suresh Chikani
    Jan 24 '17 at 10:33












  • share the error which command promt show to you.

    – Dhiren Vasoya
    Jan 25 '17 at 3:04











  • @DhirenVasoya : Added the error in question

    – Zammuuz
    Jan 25 '17 at 4:22

















  • Remove var folder and check it again.

    – Suresh Chikani
    Jan 24 '17 at 10:33












  • share the error which command promt show to you.

    – Dhiren Vasoya
    Jan 25 '17 at 3:04











  • @DhirenVasoya : Added the error in question

    – Zammuuz
    Jan 25 '17 at 4:22
















Remove var folder and check it again.

– Suresh Chikani
Jan 24 '17 at 10:33






Remove var folder and check it again.

– Suresh Chikani
Jan 24 '17 at 10:33














share the error which command promt show to you.

– Dhiren Vasoya
Jan 25 '17 at 3:04





share the error which command promt show to you.

– Dhiren Vasoya
Jan 25 '17 at 3:04













@DhirenVasoya : Added the error in question

– Zammuuz
Jan 25 '17 at 4:22





@DhirenVasoya : Added the error in question

– Zammuuz
Jan 25 '17 at 4:22










8 Answers
8






active

oldest

votes


















14














I just recently came across this same situation after migrating from Magento 1.6.1.0 to 2.1.4 and hope my answer can be of assistance. The problem came from deleting multiple stores 96 of them to be exact. I tried all the other answers here but was still getting the same error.



The fix for me was removing the old store data from inside of the "core_config_data". The problem is that when the Magento is loading the run time configuration data it is finding the old stores and trying to resolve them. Before cleaning the data from the database I HIGHLY recommend you run the SELECT query below to make sure you delete the correct stores.



SELECT * FROM core_config_data WHERE scope = 'stores';



WARNING: MAKE SURE TO BACKUP YOUR DATABASE BEFORE RUNNING THIS!



DELETE FROM core_config_data WHERE scope_id != 1 AND scope = 'stores';





share|improve this answer























  • I re-installed my magento and now this issue is not coming. Thanks for your help :) . Now i'm facing another issue. Can you plz look into this question magento.stackexchange.com/questions/160707/…

    – Zammuuz
    Feb 21 '17 at 5:36


















10














You need to run following query in your database, and then try to open website.



SET FOREIGN_KEY_CHECKS=0;
UPDATE `store` SET store_id = 0 WHERE code='admin';
UPDATE `store_group` SET group_id = 0 WHERE name='Default';
UPDATE `store_website` SET website_id = 0 WHERE code='admin';
UPDATE `customer_group` SET customer_group_id = 0 WHERE customer_group_code='NOT LOGGED IN';
SET FOREIGN_KEY_CHECKS=1;





share|improve this answer























  • No this didn't solved the issue. :(

    – Zammuuz
    Jan 25 '17 at 2:17











  • This is the only thing that worked for me!

    – Wildcard27
    Apr 29 '17 at 2:18











  • Thank you very much Dhiren Vasoya, it worked for me to. Tested on Magento 2.2

    – Andhi Irawan
    Jan 24 '18 at 13:09











  • @Dhiren Vasoya what this command actually do ?

    – ephemeral
    Feb 8 '18 at 12:09











  • Some times dua to some reason, default store_id may be changes, So above command set it default again, and magento working fine.

    – Dhiren Vasoya
    Feb 8 '18 at 14:09


















1














In this case, I have to restore that tables store, store_group, store_website. As it was before the migration Magento 2



enter image description here






share|improve this answer
































    0














    The error occurred for me during a reindex of Catalog Search while using the Elasticsearch engine. Magento 2.0.0 Commerce (and possibly other versions) have a bug resolved by the following patch.



    diff --git a/vendor/magento/module-elasticsearch/Model/Adapter/BatchDataMapper/PriceFieldsProvider.php b/vendor/magento/module-elasticsearch/Model/Adapter/BatchDataMapper/PriceFieldsProvider.php
    index aa89657..f5e8a23 100644
    --- a/vendor/magento/module-elasticsearch/Model/Adapter/BatchDataMapper/PriceFieldsProvider.php
    +++ b/vendor/magento/module-elasticsearch/Model/Adapter/BatchDataMapper/PriceFieldsProvider.php
    @@ -50,9 +50,8 @@ class PriceFieldsProvider implements AdditionalFieldsProviderInterface
    */
    public function getFields(array $productIds, $storeId)
    {
    - $websiteId = $this->storeManager->getStore($storeId)->getWebsiteId();
    $priceData = $this->dataProvider->getSearchableAttribute('price')
    - ? $this->resourceIndex->getPriceIndexData($productIds, $websiteId)
    + ? $this->resourceIndex->getPriceIndexData($productIds, $storeId)
    : [];

    $fields = [];





    share|improve this answer






























      0














      Confirm your store id and delete all the records of store which doesn't exist 'cms_page_store' & 'cms_block_store'...






      share|improve this answer






























        0














        in my case , magento 1.9 upgrade to magento 2.3



        I re-added the store item.



        I re-added the store item.






        share|improve this answer






























          -2














          It's a bug in Magento 2 already fixed in develop.



          All query results to tables store, store_group, store_websites are being cached. The problem occurs because cache isn't cleaned properly after store, store group or website is added/deleted.



          To get a fix see changes in app/code/Magento/Store/etc/di.xml and app/code/Magento/Store/Model/StoreManager.php.



          It must resolve the issue.






          share|improve this answer

























          • What does "To get a fix see changes in..." mean?

            – Adam Lavery
            Dec 15 '17 at 9:26


















          -2














          If anyone faces this similar issue. Run the following commands in your database.



          UPDATE `store` SET store_id = 0 WHERE code='admin';

          UPDATE `store_group` SET group_id = 0 WHERE name='Default';

          UPDATE `store_website` SET website_id = 0 WHERE code='admin';





          share|improve this answer


















          • 7





            @Dhiren provided this answer months prior to you accepting it as your own solution.

            – themanwhoknowstheman
            Nov 12 '17 at 17:33









          protected by Community Sep 28 '17 at 12:49



          Thank you for your interest in this question.
          Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



          Would you like to answer one of these unanswered questions instead?














          8 Answers
          8






          active

          oldest

          votes








          8 Answers
          8






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          14














          I just recently came across this same situation after migrating from Magento 1.6.1.0 to 2.1.4 and hope my answer can be of assistance. The problem came from deleting multiple stores 96 of them to be exact. I tried all the other answers here but was still getting the same error.



          The fix for me was removing the old store data from inside of the "core_config_data". The problem is that when the Magento is loading the run time configuration data it is finding the old stores and trying to resolve them. Before cleaning the data from the database I HIGHLY recommend you run the SELECT query below to make sure you delete the correct stores.



          SELECT * FROM core_config_data WHERE scope = 'stores';



          WARNING: MAKE SURE TO BACKUP YOUR DATABASE BEFORE RUNNING THIS!



          DELETE FROM core_config_data WHERE scope_id != 1 AND scope = 'stores';





          share|improve this answer























          • I re-installed my magento and now this issue is not coming. Thanks for your help :) . Now i'm facing another issue. Can you plz look into this question magento.stackexchange.com/questions/160707/…

            – Zammuuz
            Feb 21 '17 at 5:36















          14














          I just recently came across this same situation after migrating from Magento 1.6.1.0 to 2.1.4 and hope my answer can be of assistance. The problem came from deleting multiple stores 96 of them to be exact. I tried all the other answers here but was still getting the same error.



          The fix for me was removing the old store data from inside of the "core_config_data". The problem is that when the Magento is loading the run time configuration data it is finding the old stores and trying to resolve them. Before cleaning the data from the database I HIGHLY recommend you run the SELECT query below to make sure you delete the correct stores.



          SELECT * FROM core_config_data WHERE scope = 'stores';



          WARNING: MAKE SURE TO BACKUP YOUR DATABASE BEFORE RUNNING THIS!



          DELETE FROM core_config_data WHERE scope_id != 1 AND scope = 'stores';





          share|improve this answer























          • I re-installed my magento and now this issue is not coming. Thanks for your help :) . Now i'm facing another issue. Can you plz look into this question magento.stackexchange.com/questions/160707/…

            – Zammuuz
            Feb 21 '17 at 5:36













          14












          14








          14







          I just recently came across this same situation after migrating from Magento 1.6.1.0 to 2.1.4 and hope my answer can be of assistance. The problem came from deleting multiple stores 96 of them to be exact. I tried all the other answers here but was still getting the same error.



          The fix for me was removing the old store data from inside of the "core_config_data". The problem is that when the Magento is loading the run time configuration data it is finding the old stores and trying to resolve them. Before cleaning the data from the database I HIGHLY recommend you run the SELECT query below to make sure you delete the correct stores.



          SELECT * FROM core_config_data WHERE scope = 'stores';



          WARNING: MAKE SURE TO BACKUP YOUR DATABASE BEFORE RUNNING THIS!



          DELETE FROM core_config_data WHERE scope_id != 1 AND scope = 'stores';





          share|improve this answer













          I just recently came across this same situation after migrating from Magento 1.6.1.0 to 2.1.4 and hope my answer can be of assistance. The problem came from deleting multiple stores 96 of them to be exact. I tried all the other answers here but was still getting the same error.



          The fix for me was removing the old store data from inside of the "core_config_data". The problem is that when the Magento is loading the run time configuration data it is finding the old stores and trying to resolve them. Before cleaning the data from the database I HIGHLY recommend you run the SELECT query below to make sure you delete the correct stores.



          SELECT * FROM core_config_data WHERE scope = 'stores';



          WARNING: MAKE SURE TO BACKUP YOUR DATABASE BEFORE RUNNING THIS!



          DELETE FROM core_config_data WHERE scope_id != 1 AND scope = 'stores';






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 21 '17 at 5:09









          Yamaha32088Yamaha32088

          227414




          227414












          • I re-installed my magento and now this issue is not coming. Thanks for your help :) . Now i'm facing another issue. Can you plz look into this question magento.stackexchange.com/questions/160707/…

            – Zammuuz
            Feb 21 '17 at 5:36

















          • I re-installed my magento and now this issue is not coming. Thanks for your help :) . Now i'm facing another issue. Can you plz look into this question magento.stackexchange.com/questions/160707/…

            – Zammuuz
            Feb 21 '17 at 5:36
















          I re-installed my magento and now this issue is not coming. Thanks for your help :) . Now i'm facing another issue. Can you plz look into this question magento.stackexchange.com/questions/160707/…

          – Zammuuz
          Feb 21 '17 at 5:36





          I re-installed my magento and now this issue is not coming. Thanks for your help :) . Now i'm facing another issue. Can you plz look into this question magento.stackexchange.com/questions/160707/…

          – Zammuuz
          Feb 21 '17 at 5:36













          10














          You need to run following query in your database, and then try to open website.



          SET FOREIGN_KEY_CHECKS=0;
          UPDATE `store` SET store_id = 0 WHERE code='admin';
          UPDATE `store_group` SET group_id = 0 WHERE name='Default';
          UPDATE `store_website` SET website_id = 0 WHERE code='admin';
          UPDATE `customer_group` SET customer_group_id = 0 WHERE customer_group_code='NOT LOGGED IN';
          SET FOREIGN_KEY_CHECKS=1;





          share|improve this answer























          • No this didn't solved the issue. :(

            – Zammuuz
            Jan 25 '17 at 2:17











          • This is the only thing that worked for me!

            – Wildcard27
            Apr 29 '17 at 2:18











          • Thank you very much Dhiren Vasoya, it worked for me to. Tested on Magento 2.2

            – Andhi Irawan
            Jan 24 '18 at 13:09











          • @Dhiren Vasoya what this command actually do ?

            – ephemeral
            Feb 8 '18 at 12:09











          • Some times dua to some reason, default store_id may be changes, So above command set it default again, and magento working fine.

            – Dhiren Vasoya
            Feb 8 '18 at 14:09















          10














          You need to run following query in your database, and then try to open website.



          SET FOREIGN_KEY_CHECKS=0;
          UPDATE `store` SET store_id = 0 WHERE code='admin';
          UPDATE `store_group` SET group_id = 0 WHERE name='Default';
          UPDATE `store_website` SET website_id = 0 WHERE code='admin';
          UPDATE `customer_group` SET customer_group_id = 0 WHERE customer_group_code='NOT LOGGED IN';
          SET FOREIGN_KEY_CHECKS=1;





          share|improve this answer























          • No this didn't solved the issue. :(

            – Zammuuz
            Jan 25 '17 at 2:17











          • This is the only thing that worked for me!

            – Wildcard27
            Apr 29 '17 at 2:18











          • Thank you very much Dhiren Vasoya, it worked for me to. Tested on Magento 2.2

            – Andhi Irawan
            Jan 24 '18 at 13:09











          • @Dhiren Vasoya what this command actually do ?

            – ephemeral
            Feb 8 '18 at 12:09











          • Some times dua to some reason, default store_id may be changes, So above command set it default again, and magento working fine.

            – Dhiren Vasoya
            Feb 8 '18 at 14:09













          10












          10








          10







          You need to run following query in your database, and then try to open website.



          SET FOREIGN_KEY_CHECKS=0;
          UPDATE `store` SET store_id = 0 WHERE code='admin';
          UPDATE `store_group` SET group_id = 0 WHERE name='Default';
          UPDATE `store_website` SET website_id = 0 WHERE code='admin';
          UPDATE `customer_group` SET customer_group_id = 0 WHERE customer_group_code='NOT LOGGED IN';
          SET FOREIGN_KEY_CHECKS=1;





          share|improve this answer













          You need to run following query in your database, and then try to open website.



          SET FOREIGN_KEY_CHECKS=0;
          UPDATE `store` SET store_id = 0 WHERE code='admin';
          UPDATE `store_group` SET group_id = 0 WHERE name='Default';
          UPDATE `store_website` SET website_id = 0 WHERE code='admin';
          UPDATE `customer_group` SET customer_group_id = 0 WHERE customer_group_code='NOT LOGGED IN';
          SET FOREIGN_KEY_CHECKS=1;






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jan 24 '17 at 11:41









          Dhiren VasoyaDhiren Vasoya

          4,74051946




          4,74051946












          • No this didn't solved the issue. :(

            – Zammuuz
            Jan 25 '17 at 2:17











          • This is the only thing that worked for me!

            – Wildcard27
            Apr 29 '17 at 2:18











          • Thank you very much Dhiren Vasoya, it worked for me to. Tested on Magento 2.2

            – Andhi Irawan
            Jan 24 '18 at 13:09











          • @Dhiren Vasoya what this command actually do ?

            – ephemeral
            Feb 8 '18 at 12:09











          • Some times dua to some reason, default store_id may be changes, So above command set it default again, and magento working fine.

            – Dhiren Vasoya
            Feb 8 '18 at 14:09

















          • No this didn't solved the issue. :(

            – Zammuuz
            Jan 25 '17 at 2:17











          • This is the only thing that worked for me!

            – Wildcard27
            Apr 29 '17 at 2:18











          • Thank you very much Dhiren Vasoya, it worked for me to. Tested on Magento 2.2

            – Andhi Irawan
            Jan 24 '18 at 13:09











          • @Dhiren Vasoya what this command actually do ?

            – ephemeral
            Feb 8 '18 at 12:09











          • Some times dua to some reason, default store_id may be changes, So above command set it default again, and magento working fine.

            – Dhiren Vasoya
            Feb 8 '18 at 14:09
















          No this didn't solved the issue. :(

          – Zammuuz
          Jan 25 '17 at 2:17





          No this didn't solved the issue. :(

          – Zammuuz
          Jan 25 '17 at 2:17













          This is the only thing that worked for me!

          – Wildcard27
          Apr 29 '17 at 2:18





          This is the only thing that worked for me!

          – Wildcard27
          Apr 29 '17 at 2:18













          Thank you very much Dhiren Vasoya, it worked for me to. Tested on Magento 2.2

          – Andhi Irawan
          Jan 24 '18 at 13:09





          Thank you very much Dhiren Vasoya, it worked for me to. Tested on Magento 2.2

          – Andhi Irawan
          Jan 24 '18 at 13:09













          @Dhiren Vasoya what this command actually do ?

          – ephemeral
          Feb 8 '18 at 12:09





          @Dhiren Vasoya what this command actually do ?

          – ephemeral
          Feb 8 '18 at 12:09













          Some times dua to some reason, default store_id may be changes, So above command set it default again, and magento working fine.

          – Dhiren Vasoya
          Feb 8 '18 at 14:09





          Some times dua to some reason, default store_id may be changes, So above command set it default again, and magento working fine.

          – Dhiren Vasoya
          Feb 8 '18 at 14:09











          1














          In this case, I have to restore that tables store, store_group, store_website. As it was before the migration Magento 2



          enter image description here






          share|improve this answer





























            1














            In this case, I have to restore that tables store, store_group, store_website. As it was before the migration Magento 2



            enter image description here






            share|improve this answer



























              1












              1








              1







              In this case, I have to restore that tables store, store_group, store_website. As it was before the migration Magento 2



              enter image description here






              share|improve this answer















              In this case, I have to restore that tables store, store_group, store_website. As it was before the migration Magento 2



              enter image description here







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Jul 20 '17 at 18:33









              Rafael Corrêa Gomes

              4,88523367




              4,88523367










              answered Jul 20 '17 at 18:32









              Israel GuidoIsrael Guido

              2318




              2318





















                  0














                  The error occurred for me during a reindex of Catalog Search while using the Elasticsearch engine. Magento 2.0.0 Commerce (and possibly other versions) have a bug resolved by the following patch.



                  diff --git a/vendor/magento/module-elasticsearch/Model/Adapter/BatchDataMapper/PriceFieldsProvider.php b/vendor/magento/module-elasticsearch/Model/Adapter/BatchDataMapper/PriceFieldsProvider.php
                  index aa89657..f5e8a23 100644
                  --- a/vendor/magento/module-elasticsearch/Model/Adapter/BatchDataMapper/PriceFieldsProvider.php
                  +++ b/vendor/magento/module-elasticsearch/Model/Adapter/BatchDataMapper/PriceFieldsProvider.php
                  @@ -50,9 +50,8 @@ class PriceFieldsProvider implements AdditionalFieldsProviderInterface
                  */
                  public function getFields(array $productIds, $storeId)
                  {
                  - $websiteId = $this->storeManager->getStore($storeId)->getWebsiteId();
                  $priceData = $this->dataProvider->getSearchableAttribute('price')
                  - ? $this->resourceIndex->getPriceIndexData($productIds, $websiteId)
                  + ? $this->resourceIndex->getPriceIndexData($productIds, $storeId)
                  : [];

                  $fields = [];





                  share|improve this answer



























                    0














                    The error occurred for me during a reindex of Catalog Search while using the Elasticsearch engine. Magento 2.0.0 Commerce (and possibly other versions) have a bug resolved by the following patch.



                    diff --git a/vendor/magento/module-elasticsearch/Model/Adapter/BatchDataMapper/PriceFieldsProvider.php b/vendor/magento/module-elasticsearch/Model/Adapter/BatchDataMapper/PriceFieldsProvider.php
                    index aa89657..f5e8a23 100644
                    --- a/vendor/magento/module-elasticsearch/Model/Adapter/BatchDataMapper/PriceFieldsProvider.php
                    +++ b/vendor/magento/module-elasticsearch/Model/Adapter/BatchDataMapper/PriceFieldsProvider.php
                    @@ -50,9 +50,8 @@ class PriceFieldsProvider implements AdditionalFieldsProviderInterface
                    */
                    public function getFields(array $productIds, $storeId)
                    {
                    - $websiteId = $this->storeManager->getStore($storeId)->getWebsiteId();
                    $priceData = $this->dataProvider->getSearchableAttribute('price')
                    - ? $this->resourceIndex->getPriceIndexData($productIds, $websiteId)
                    + ? $this->resourceIndex->getPriceIndexData($productIds, $storeId)
                    : [];

                    $fields = [];





                    share|improve this answer

























                      0












                      0








                      0







                      The error occurred for me during a reindex of Catalog Search while using the Elasticsearch engine. Magento 2.0.0 Commerce (and possibly other versions) have a bug resolved by the following patch.



                      diff --git a/vendor/magento/module-elasticsearch/Model/Adapter/BatchDataMapper/PriceFieldsProvider.php b/vendor/magento/module-elasticsearch/Model/Adapter/BatchDataMapper/PriceFieldsProvider.php
                      index aa89657..f5e8a23 100644
                      --- a/vendor/magento/module-elasticsearch/Model/Adapter/BatchDataMapper/PriceFieldsProvider.php
                      +++ b/vendor/magento/module-elasticsearch/Model/Adapter/BatchDataMapper/PriceFieldsProvider.php
                      @@ -50,9 +50,8 @@ class PriceFieldsProvider implements AdditionalFieldsProviderInterface
                      */
                      public function getFields(array $productIds, $storeId)
                      {
                      - $websiteId = $this->storeManager->getStore($storeId)->getWebsiteId();
                      $priceData = $this->dataProvider->getSearchableAttribute('price')
                      - ? $this->resourceIndex->getPriceIndexData($productIds, $websiteId)
                      + ? $this->resourceIndex->getPriceIndexData($productIds, $storeId)
                      : [];

                      $fields = [];





                      share|improve this answer













                      The error occurred for me during a reindex of Catalog Search while using the Elasticsearch engine. Magento 2.0.0 Commerce (and possibly other versions) have a bug resolved by the following patch.



                      diff --git a/vendor/magento/module-elasticsearch/Model/Adapter/BatchDataMapper/PriceFieldsProvider.php b/vendor/magento/module-elasticsearch/Model/Adapter/BatchDataMapper/PriceFieldsProvider.php
                      index aa89657..f5e8a23 100644
                      --- a/vendor/magento/module-elasticsearch/Model/Adapter/BatchDataMapper/PriceFieldsProvider.php
                      +++ b/vendor/magento/module-elasticsearch/Model/Adapter/BatchDataMapper/PriceFieldsProvider.php
                      @@ -50,9 +50,8 @@ class PriceFieldsProvider implements AdditionalFieldsProviderInterface
                      */
                      public function getFields(array $productIds, $storeId)
                      {
                      - $websiteId = $this->storeManager->getStore($storeId)->getWebsiteId();
                      $priceData = $this->dataProvider->getSearchableAttribute('price')
                      - ? $this->resourceIndex->getPriceIndexData($productIds, $websiteId)
                      + ? $this->resourceIndex->getPriceIndexData($productIds, $storeId)
                      : [];

                      $fields = [];






                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered May 18 '18 at 22:36









                      Joe SheltonJoe Shelton

                      386




                      386





















                          0














                          Confirm your store id and delete all the records of store which doesn't exist 'cms_page_store' & 'cms_block_store'...






                          share|improve this answer



























                            0














                            Confirm your store id and delete all the records of store which doesn't exist 'cms_page_store' & 'cms_block_store'...






                            share|improve this answer

























                              0












                              0








                              0







                              Confirm your store id and delete all the records of store which doesn't exist 'cms_page_store' & 'cms_block_store'...






                              share|improve this answer













                              Confirm your store id and delete all the records of store which doesn't exist 'cms_page_store' & 'cms_block_store'...







                              share|improve this answer












                              share|improve this answer



                              share|improve this answer










                              answered Mar 18 at 9:29









                              Arvind HathiyaArvind Hathiya

                              325




                              325





















                                  0














                                  in my case , magento 1.9 upgrade to magento 2.3



                                  I re-added the store item.



                                  I re-added the store item.






                                  share|improve this answer



























                                    0














                                    in my case , magento 1.9 upgrade to magento 2.3



                                    I re-added the store item.



                                    I re-added the store item.






                                    share|improve this answer

























                                      0












                                      0








                                      0







                                      in my case , magento 1.9 upgrade to magento 2.3



                                      I re-added the store item.



                                      I re-added the store item.






                                      share|improve this answer













                                      in my case , magento 1.9 upgrade to magento 2.3



                                      I re-added the store item.



                                      I re-added the store item.







                                      share|improve this answer












                                      share|improve this answer



                                      share|improve this answer










                                      answered May 31 at 10:26









                                      Patrick-PengPatrick-Peng

                                      6610




                                      6610





















                                          -2














                                          It's a bug in Magento 2 already fixed in develop.



                                          All query results to tables store, store_group, store_websites are being cached. The problem occurs because cache isn't cleaned properly after store, store group or website is added/deleted.



                                          To get a fix see changes in app/code/Magento/Store/etc/di.xml and app/code/Magento/Store/Model/StoreManager.php.



                                          It must resolve the issue.






                                          share|improve this answer

























                                          • What does "To get a fix see changes in..." mean?

                                            – Adam Lavery
                                            Dec 15 '17 at 9:26















                                          -2














                                          It's a bug in Magento 2 already fixed in develop.



                                          All query results to tables store, store_group, store_websites are being cached. The problem occurs because cache isn't cleaned properly after store, store group or website is added/deleted.



                                          To get a fix see changes in app/code/Magento/Store/etc/di.xml and app/code/Magento/Store/Model/StoreManager.php.



                                          It must resolve the issue.






                                          share|improve this answer

























                                          • What does "To get a fix see changes in..." mean?

                                            – Adam Lavery
                                            Dec 15 '17 at 9:26













                                          -2












                                          -2








                                          -2







                                          It's a bug in Magento 2 already fixed in develop.



                                          All query results to tables store, store_group, store_websites are being cached. The problem occurs because cache isn't cleaned properly after store, store group or website is added/deleted.



                                          To get a fix see changes in app/code/Magento/Store/etc/di.xml and app/code/Magento/Store/Model/StoreManager.php.



                                          It must resolve the issue.






                                          share|improve this answer















                                          It's a bug in Magento 2 already fixed in develop.



                                          All query results to tables store, store_group, store_websites are being cached. The problem occurs because cache isn't cleaned properly after store, store group or website is added/deleted.



                                          To get a fix see changes in app/code/Magento/Store/etc/di.xml and app/code/Magento/Store/Model/StoreManager.php.



                                          It must resolve the issue.







                                          share|improve this answer














                                          share|improve this answer



                                          share|improve this answer








                                          edited Feb 13 '17 at 10:35

























                                          answered Feb 13 '17 at 10:29









                                          yaronishyaronish

                                          62223




                                          62223












                                          • What does "To get a fix see changes in..." mean?

                                            – Adam Lavery
                                            Dec 15 '17 at 9:26

















                                          • What does "To get a fix see changes in..." mean?

                                            – Adam Lavery
                                            Dec 15 '17 at 9:26
















                                          What does "To get a fix see changes in..." mean?

                                          – Adam Lavery
                                          Dec 15 '17 at 9:26





                                          What does "To get a fix see changes in..." mean?

                                          – Adam Lavery
                                          Dec 15 '17 at 9:26











                                          -2














                                          If anyone faces this similar issue. Run the following commands in your database.



                                          UPDATE `store` SET store_id = 0 WHERE code='admin';

                                          UPDATE `store_group` SET group_id = 0 WHERE name='Default';

                                          UPDATE `store_website` SET website_id = 0 WHERE code='admin';





                                          share|improve this answer


















                                          • 7





                                            @Dhiren provided this answer months prior to you accepting it as your own solution.

                                            – themanwhoknowstheman
                                            Nov 12 '17 at 17:33















                                          -2














                                          If anyone faces this similar issue. Run the following commands in your database.



                                          UPDATE `store` SET store_id = 0 WHERE code='admin';

                                          UPDATE `store_group` SET group_id = 0 WHERE name='Default';

                                          UPDATE `store_website` SET website_id = 0 WHERE code='admin';





                                          share|improve this answer


















                                          • 7





                                            @Dhiren provided this answer months prior to you accepting it as your own solution.

                                            – themanwhoknowstheman
                                            Nov 12 '17 at 17:33













                                          -2












                                          -2








                                          -2







                                          If anyone faces this similar issue. Run the following commands in your database.



                                          UPDATE `store` SET store_id = 0 WHERE code='admin';

                                          UPDATE `store_group` SET group_id = 0 WHERE name='Default';

                                          UPDATE `store_website` SET website_id = 0 WHERE code='admin';





                                          share|improve this answer













                                          If anyone faces this similar issue. Run the following commands in your database.



                                          UPDATE `store` SET store_id = 0 WHERE code='admin';

                                          UPDATE `store_group` SET group_id = 0 WHERE name='Default';

                                          UPDATE `store_website` SET website_id = 0 WHERE code='admin';






                                          share|improve this answer












                                          share|improve this answer



                                          share|improve this answer










                                          answered Jun 21 '17 at 5:17









                                          ZammuuzZammuuz

                                          2121314




                                          2121314







                                          • 7





                                            @Dhiren provided this answer months prior to you accepting it as your own solution.

                                            – themanwhoknowstheman
                                            Nov 12 '17 at 17:33












                                          • 7





                                            @Dhiren provided this answer months prior to you accepting it as your own solution.

                                            – themanwhoknowstheman
                                            Nov 12 '17 at 17:33







                                          7




                                          7





                                          @Dhiren provided this answer months prior to you accepting it as your own solution.

                                          – themanwhoknowstheman
                                          Nov 12 '17 at 17:33





                                          @Dhiren provided this answer months prior to you accepting it as your own solution.

                                          – themanwhoknowstheman
                                          Nov 12 '17 at 17:33





                                          protected by Community Sep 28 '17 at 12:49



                                          Thank you for your interest in this question.
                                          Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                                          Would you like to answer one of these unanswered questions instead?



                                          Popular posts from this blog

                                          Category:9 (number) SubcategoriesMedia in category "9 (number)"Navigation menuUpload mediaGND ID: 4485639-8Library of Congress authority ID: sh85091979ReasonatorScholiaStatistics

                                          Circuit construction for execution of conditional statements using least significant bitHow are two different registers being used as “control”?How exactly is the stated composite state of the two registers being produced using the $R_zz$ controlled rotations?Efficiently performing controlled rotations in HHLWould this quantum algorithm implementation work?How to prepare a superposed states of odd integers from $1$ to $sqrtN$?Why is this implementation of the order finding algorithm not working?Circuit construction for Hamiltonian simulationHow can I invert the least significant bit of a certain term of a superposed state?Implementing an oracleImplementing a controlled sum operation

                                          Magento 2 “No Payment Methods” in Admin New OrderHow to integrate Paypal Express Checkout with the Magento APIMagento 1.5 - Sales > Order > edit order and shipping methods disappearAuto Invoice Check/Money Order Payment methodAdd more simple payment methods?Shipping methods not showingWhat should I do to change payment methods if changing the configuration has no effects?1.9 - No Payment Methods showing upMy Payment Methods not Showing for downloadable/virtual product when checkout?Magento2 API to access internal payment methodHow to call an existing payment methods in the registration form?