Magento 2 reindex returns No such entity












13















I have successfully migrated the catalog from Magento 1.9.2.3 to Magento 2.0.2.
After the migration, I did reindex using the command php bin/magento indexer:reindex.



All is reindexed successfully, except indexes catalog_category_product and catalog_product_category, returning No such entity. in shell and notification Reindex Required in admin.
I've checked var/log/ but no errors.



As a result, products are added to categories in the backend but categories show up empty on the frontend.



What might cause this problem?
How can I debug?










share|improve this question

























  • basically the same magento.stackexchange.com/questions/102739/…

    – Patrick-Peng
    Jul 17 '16 at 0:59
















13















I have successfully migrated the catalog from Magento 1.9.2.3 to Magento 2.0.2.
After the migration, I did reindex using the command php bin/magento indexer:reindex.



All is reindexed successfully, except indexes catalog_category_product and catalog_product_category, returning No such entity. in shell and notification Reindex Required in admin.
I've checked var/log/ but no errors.



As a result, products are added to categories in the backend but categories show up empty on the frontend.



What might cause this problem?
How can I debug?










share|improve this question

























  • basically the same magento.stackexchange.com/questions/102739/…

    – Patrick-Peng
    Jul 17 '16 at 0:59














13












13








13


1






I have successfully migrated the catalog from Magento 1.9.2.3 to Magento 2.0.2.
After the migration, I did reindex using the command php bin/magento indexer:reindex.



All is reindexed successfully, except indexes catalog_category_product and catalog_product_category, returning No such entity. in shell and notification Reindex Required in admin.
I've checked var/log/ but no errors.



As a result, products are added to categories in the backend but categories show up empty on the frontend.



What might cause this problem?
How can I debug?










share|improve this question
















I have successfully migrated the catalog from Magento 1.9.2.3 to Magento 2.0.2.
After the migration, I did reindex using the command php bin/magento indexer:reindex.



All is reindexed successfully, except indexes catalog_category_product and catalog_product_category, returning No such entity. in shell and notification Reindex Required in admin.
I've checked var/log/ but no errors.



As a result, products are added to categories in the backend but categories show up empty on the frontend.



What might cause this problem?
How can I debug?







magento2 reindex magento-2.0 migration






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 7 '18 at 0:40









Rafael Corrêa Gomes

4,29222962




4,29222962










asked Mar 17 '16 at 19:35









Gerard de VisserGerard de Visser

3151419




3151419













  • basically the same magento.stackexchange.com/questions/102739/…

    – Patrick-Peng
    Jul 17 '16 at 0:59



















  • basically the same magento.stackexchange.com/questions/102739/…

    – Patrick-Peng
    Jul 17 '16 at 0:59

















basically the same magento.stackexchange.com/questions/102739/…

– Patrick-Peng
Jul 17 '16 at 0:59





basically the same magento.stackexchange.com/questions/102739/…

– Patrick-Peng
Jul 17 '16 at 0:59










5 Answers
5






active

oldest

votes


















7














In addition to Raphael:



I Debugged this code with altering the exception constructor for debug purposes (either by xdebug or old dumps).
Alter the construct of the exception for now (the file is libinternalMagentoFrameworkExceptionNoSuchEntityException.php)



$trace = debug_backtrace();
var_dump($trace[1]['class'] . '::' . $trace[1]['function'] . '('.$trace[1]['line'] .')';
die();


After that go up one stack and check the arguments given (the args are also available in the debug backtrace, but dumping magento objects isn't really browser friendly).



Came to the conclusion, that it was in the storeGroupRepository where it couldn't find the group id. Dived into the store tables and saw a few lines in the store table that were referencing a store_group that wasn't in the store_group table(store group not exist in relevant table).



Removed the faulty store lines and the error has been gone ever since.



But, keep in mind that it can also be in a different table/other reason. for example website, store itself or store group in this case. So that is always a little search you have to perform yourself.



Also found out that there were quite a lot of references to these stores and also removed them manually in the db. This can be a tedious work but it will solve the problem.



And don't forget to remove your hacks.






share|improve this answer


























  • why don't you use xdebug instead?

    – Luke
    Oct 2 '17 at 13:23











  • @TimVroom I have also same error.Please help me magento.stackexchange.com/q/236187/24878

    – akgola
    Jul 27 '18 at 7:58



















9














Not sure if this is too late to add, but when I had this It appeared to be caused by some entity ids that needed to be set to 0.



This script worked for me:



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;


Hope it helps.






share|improve this answer
























  • this helped me a lot, thank you for sharing!

    – favo
    May 17 '17 at 14:10











  • This also worked for me :)

    – Owen
    Jan 27 '18 at 9:18



















3














Ok so the No such entity. error message comes from libinternalMagentoFrameworkExceptionNoSuchEntityException.php.



This class is a custom exception class of Magento and it is used a lot in Magento 2.



Whenever you see code like:



catch (NoSuchEntityException $e)


Or



throw NoSuchEntityException;


This class is being used.



The problem in your case is that it's hard to find out from where that exception is being thrown.



So to narrow it a bit, you can start debugging the two classes related to your indexes that fail:





  • MagentoCatalogModelIndexerCategoryProduct => catalog_category_product index


  • MagentoCatalogModelIndexerProductCategory => catalog_product_category index


Fortunately, the second one extends the first one so you've got one starting point.



You've got to keep in mind that each of this indexer class uses action rows classes to process the reindexing:




  • MagentoCatalogModelIndexerProductCategoryActionRows

  • MagentoCatalogModelIndexerCategoryProductActionRows


To me that's where you should start debugging as those action row classes are the direct classes which are reindexing those two indexes.



I really hope it will help you find your problem.






share|improve this answer
























  • Hi @Raphael , I have similar issue for customer creation after migration.Please help me magento.stackexchange.com/q/236187/24878

    – akgola
    Jul 27 '18 at 7:59



















0














THIS WORKED FOR ME AFTER TRYING EVERYTHING.



Assuming your site is in Developer Mode, you can change it to Production Mode and clear/flush cache and then switch back to Developer Mode.



I had this issue in the front end, as i recently moved the database from one server to another. I have managed to solve by this way.



HOPE THIS HELPS SOME ONE.






share|improve this answer































    0














    Basically the same



    Magento 2 - Moving site - 'No such entity'



    cd /magento-root-path/var



    rm -rf *



    cd ../



    php bin/magento setup:upgrade



    rm -rf ./var/di



    php bin/magento setup:di:compile



    php bin/magento setup:static-content:deploy



    chown -R www-data .






    share|improve this answer

























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "479"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f106793%2fmagento-2-reindex-returns-no-such-entity%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      5 Answers
      5






      active

      oldest

      votes








      5 Answers
      5






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      7














      In addition to Raphael:



      I Debugged this code with altering the exception constructor for debug purposes (either by xdebug or old dumps).
      Alter the construct of the exception for now (the file is libinternalMagentoFrameworkExceptionNoSuchEntityException.php)



      $trace = debug_backtrace();
      var_dump($trace[1]['class'] . '::' . $trace[1]['function'] . '('.$trace[1]['line'] .')';
      die();


      After that go up one stack and check the arguments given (the args are also available in the debug backtrace, but dumping magento objects isn't really browser friendly).



      Came to the conclusion, that it was in the storeGroupRepository where it couldn't find the group id. Dived into the store tables and saw a few lines in the store table that were referencing a store_group that wasn't in the store_group table(store group not exist in relevant table).



      Removed the faulty store lines and the error has been gone ever since.



      But, keep in mind that it can also be in a different table/other reason. for example website, store itself or store group in this case. So that is always a little search you have to perform yourself.



      Also found out that there were quite a lot of references to these stores and also removed them manually in the db. This can be a tedious work but it will solve the problem.



      And don't forget to remove your hacks.






      share|improve this answer


























      • why don't you use xdebug instead?

        – Luke
        Oct 2 '17 at 13:23











      • @TimVroom I have also same error.Please help me magento.stackexchange.com/q/236187/24878

        – akgola
        Jul 27 '18 at 7:58
















      7














      In addition to Raphael:



      I Debugged this code with altering the exception constructor for debug purposes (either by xdebug or old dumps).
      Alter the construct of the exception for now (the file is libinternalMagentoFrameworkExceptionNoSuchEntityException.php)



      $trace = debug_backtrace();
      var_dump($trace[1]['class'] . '::' . $trace[1]['function'] . '('.$trace[1]['line'] .')';
      die();


      After that go up one stack and check the arguments given (the args are also available in the debug backtrace, but dumping magento objects isn't really browser friendly).



      Came to the conclusion, that it was in the storeGroupRepository where it couldn't find the group id. Dived into the store tables and saw a few lines in the store table that were referencing a store_group that wasn't in the store_group table(store group not exist in relevant table).



      Removed the faulty store lines and the error has been gone ever since.



      But, keep in mind that it can also be in a different table/other reason. for example website, store itself or store group in this case. So that is always a little search you have to perform yourself.



      Also found out that there were quite a lot of references to these stores and also removed them manually in the db. This can be a tedious work but it will solve the problem.



      And don't forget to remove your hacks.






      share|improve this answer


























      • why don't you use xdebug instead?

        – Luke
        Oct 2 '17 at 13:23











      • @TimVroom I have also same error.Please help me magento.stackexchange.com/q/236187/24878

        – akgola
        Jul 27 '18 at 7:58














      7












      7








      7







      In addition to Raphael:



      I Debugged this code with altering the exception constructor for debug purposes (either by xdebug or old dumps).
      Alter the construct of the exception for now (the file is libinternalMagentoFrameworkExceptionNoSuchEntityException.php)



      $trace = debug_backtrace();
      var_dump($trace[1]['class'] . '::' . $trace[1]['function'] . '('.$trace[1]['line'] .')';
      die();


      After that go up one stack and check the arguments given (the args are also available in the debug backtrace, but dumping magento objects isn't really browser friendly).



      Came to the conclusion, that it was in the storeGroupRepository where it couldn't find the group id. Dived into the store tables and saw a few lines in the store table that were referencing a store_group that wasn't in the store_group table(store group not exist in relevant table).



      Removed the faulty store lines and the error has been gone ever since.



      But, keep in mind that it can also be in a different table/other reason. for example website, store itself or store group in this case. So that is always a little search you have to perform yourself.



      Also found out that there were quite a lot of references to these stores and also removed them manually in the db. This can be a tedious work but it will solve the problem.



      And don't forget to remove your hacks.






      share|improve this answer















      In addition to Raphael:



      I Debugged this code with altering the exception constructor for debug purposes (either by xdebug or old dumps).
      Alter the construct of the exception for now (the file is libinternalMagentoFrameworkExceptionNoSuchEntityException.php)



      $trace = debug_backtrace();
      var_dump($trace[1]['class'] . '::' . $trace[1]['function'] . '('.$trace[1]['line'] .')';
      die();


      After that go up one stack and check the arguments given (the args are also available in the debug backtrace, but dumping magento objects isn't really browser friendly).



      Came to the conclusion, that it was in the storeGroupRepository where it couldn't find the group id. Dived into the store tables and saw a few lines in the store table that were referencing a store_group that wasn't in the store_group table(store group not exist in relevant table).



      Removed the faulty store lines and the error has been gone ever since.



      But, keep in mind that it can also be in a different table/other reason. for example website, store itself or store group in this case. So that is always a little search you have to perform yourself.



      Also found out that there were quite a lot of references to these stores and also removed them manually in the db. This can be a tedious work but it will solve the problem.



      And don't forget to remove your hacks.







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited Jul 6 '16 at 11:06









      denish vachhani

      3,2651838




      3,2651838










      answered Apr 22 '16 at 13:51









      TimVroomTimVroom

      32918




      32918













      • why don't you use xdebug instead?

        – Luke
        Oct 2 '17 at 13:23











      • @TimVroom I have also same error.Please help me magento.stackexchange.com/q/236187/24878

        – akgola
        Jul 27 '18 at 7:58



















      • why don't you use xdebug instead?

        – Luke
        Oct 2 '17 at 13:23











      • @TimVroom I have also same error.Please help me magento.stackexchange.com/q/236187/24878

        – akgola
        Jul 27 '18 at 7:58

















      why don't you use xdebug instead?

      – Luke
      Oct 2 '17 at 13:23





      why don't you use xdebug instead?

      – Luke
      Oct 2 '17 at 13:23













      @TimVroom I have also same error.Please help me magento.stackexchange.com/q/236187/24878

      – akgola
      Jul 27 '18 at 7:58





      @TimVroom I have also same error.Please help me magento.stackexchange.com/q/236187/24878

      – akgola
      Jul 27 '18 at 7:58













      9














      Not sure if this is too late to add, but when I had this It appeared to be caused by some entity ids that needed to be set to 0.



      This script worked for me:



      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;


      Hope it helps.






      share|improve this answer
























      • this helped me a lot, thank you for sharing!

        – favo
        May 17 '17 at 14:10











      • This also worked for me :)

        – Owen
        Jan 27 '18 at 9:18
















      9














      Not sure if this is too late to add, but when I had this It appeared to be caused by some entity ids that needed to be set to 0.



      This script worked for me:



      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;


      Hope it helps.






      share|improve this answer
























      • this helped me a lot, thank you for sharing!

        – favo
        May 17 '17 at 14:10











      • This also worked for me :)

        – Owen
        Jan 27 '18 at 9:18














      9












      9








      9







      Not sure if this is too late to add, but when I had this It appeared to be caused by some entity ids that needed to be set to 0.



      This script worked for me:



      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;


      Hope it helps.






      share|improve this answer













      Not sure if this is too late to add, but when I had this It appeared to be caused by some entity ids that needed to be set to 0.



      This script worked for me:



      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;


      Hope it helps.







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered May 18 '16 at 8:04









      Adam StaceyAdam Stacey

      40349




      40349













      • this helped me a lot, thank you for sharing!

        – favo
        May 17 '17 at 14:10











      • This also worked for me :)

        – Owen
        Jan 27 '18 at 9:18



















      • this helped me a lot, thank you for sharing!

        – favo
        May 17 '17 at 14:10











      • This also worked for me :)

        – Owen
        Jan 27 '18 at 9:18

















      this helped me a lot, thank you for sharing!

      – favo
      May 17 '17 at 14:10





      this helped me a lot, thank you for sharing!

      – favo
      May 17 '17 at 14:10













      This also worked for me :)

      – Owen
      Jan 27 '18 at 9:18





      This also worked for me :)

      – Owen
      Jan 27 '18 at 9:18











      3














      Ok so the No such entity. error message comes from libinternalMagentoFrameworkExceptionNoSuchEntityException.php.



      This class is a custom exception class of Magento and it is used a lot in Magento 2.



      Whenever you see code like:



      catch (NoSuchEntityException $e)


      Or



      throw NoSuchEntityException;


      This class is being used.



      The problem in your case is that it's hard to find out from where that exception is being thrown.



      So to narrow it a bit, you can start debugging the two classes related to your indexes that fail:





      • MagentoCatalogModelIndexerCategoryProduct => catalog_category_product index


      • MagentoCatalogModelIndexerProductCategory => catalog_product_category index


      Fortunately, the second one extends the first one so you've got one starting point.



      You've got to keep in mind that each of this indexer class uses action rows classes to process the reindexing:




      • MagentoCatalogModelIndexerProductCategoryActionRows

      • MagentoCatalogModelIndexerCategoryProductActionRows


      To me that's where you should start debugging as those action row classes are the direct classes which are reindexing those two indexes.



      I really hope it will help you find your problem.






      share|improve this answer
























      • Hi @Raphael , I have similar issue for customer creation after migration.Please help me magento.stackexchange.com/q/236187/24878

        – akgola
        Jul 27 '18 at 7:59
















      3














      Ok so the No such entity. error message comes from libinternalMagentoFrameworkExceptionNoSuchEntityException.php.



      This class is a custom exception class of Magento and it is used a lot in Magento 2.



      Whenever you see code like:



      catch (NoSuchEntityException $e)


      Or



      throw NoSuchEntityException;


      This class is being used.



      The problem in your case is that it's hard to find out from where that exception is being thrown.



      So to narrow it a bit, you can start debugging the two classes related to your indexes that fail:





      • MagentoCatalogModelIndexerCategoryProduct => catalog_category_product index


      • MagentoCatalogModelIndexerProductCategory => catalog_product_category index


      Fortunately, the second one extends the first one so you've got one starting point.



      You've got to keep in mind that each of this indexer class uses action rows classes to process the reindexing:




      • MagentoCatalogModelIndexerProductCategoryActionRows

      • MagentoCatalogModelIndexerCategoryProductActionRows


      To me that's where you should start debugging as those action row classes are the direct classes which are reindexing those two indexes.



      I really hope it will help you find your problem.






      share|improve this answer
























      • Hi @Raphael , I have similar issue for customer creation after migration.Please help me magento.stackexchange.com/q/236187/24878

        – akgola
        Jul 27 '18 at 7:59














      3












      3








      3







      Ok so the No such entity. error message comes from libinternalMagentoFrameworkExceptionNoSuchEntityException.php.



      This class is a custom exception class of Magento and it is used a lot in Magento 2.



      Whenever you see code like:



      catch (NoSuchEntityException $e)


      Or



      throw NoSuchEntityException;


      This class is being used.



      The problem in your case is that it's hard to find out from where that exception is being thrown.



      So to narrow it a bit, you can start debugging the two classes related to your indexes that fail:





      • MagentoCatalogModelIndexerCategoryProduct => catalog_category_product index


      • MagentoCatalogModelIndexerProductCategory => catalog_product_category index


      Fortunately, the second one extends the first one so you've got one starting point.



      You've got to keep in mind that each of this indexer class uses action rows classes to process the reindexing:




      • MagentoCatalogModelIndexerProductCategoryActionRows

      • MagentoCatalogModelIndexerCategoryProductActionRows


      To me that's where you should start debugging as those action row classes are the direct classes which are reindexing those two indexes.



      I really hope it will help you find your problem.






      share|improve this answer













      Ok so the No such entity. error message comes from libinternalMagentoFrameworkExceptionNoSuchEntityException.php.



      This class is a custom exception class of Magento and it is used a lot in Magento 2.



      Whenever you see code like:



      catch (NoSuchEntityException $e)


      Or



      throw NoSuchEntityException;


      This class is being used.



      The problem in your case is that it's hard to find out from where that exception is being thrown.



      So to narrow it a bit, you can start debugging the two classes related to your indexes that fail:





      • MagentoCatalogModelIndexerCategoryProduct => catalog_category_product index


      • MagentoCatalogModelIndexerProductCategory => catalog_product_category index


      Fortunately, the second one extends the first one so you've got one starting point.



      You've got to keep in mind that each of this indexer class uses action rows classes to process the reindexing:




      • MagentoCatalogModelIndexerProductCategoryActionRows

      • MagentoCatalogModelIndexerCategoryProductActionRows


      To me that's where you should start debugging as those action row classes are the direct classes which are reindexing those two indexes.



      I really hope it will help you find your problem.







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Apr 7 '16 at 15:34









      Raphael at Digital PianismRaphael at Digital Pianism

      53.5k19112270




      53.5k19112270













      • Hi @Raphael , I have similar issue for customer creation after migration.Please help me magento.stackexchange.com/q/236187/24878

        – akgola
        Jul 27 '18 at 7:59



















      • Hi @Raphael , I have similar issue for customer creation after migration.Please help me magento.stackexchange.com/q/236187/24878

        – akgola
        Jul 27 '18 at 7:59

















      Hi @Raphael , I have similar issue for customer creation after migration.Please help me magento.stackexchange.com/q/236187/24878

      – akgola
      Jul 27 '18 at 7:59





      Hi @Raphael , I have similar issue for customer creation after migration.Please help me magento.stackexchange.com/q/236187/24878

      – akgola
      Jul 27 '18 at 7:59











      0














      THIS WORKED FOR ME AFTER TRYING EVERYTHING.



      Assuming your site is in Developer Mode, you can change it to Production Mode and clear/flush cache and then switch back to Developer Mode.



      I had this issue in the front end, as i recently moved the database from one server to another. I have managed to solve by this way.



      HOPE THIS HELPS SOME ONE.






      share|improve this answer




























        0














        THIS WORKED FOR ME AFTER TRYING EVERYTHING.



        Assuming your site is in Developer Mode, you can change it to Production Mode and clear/flush cache and then switch back to Developer Mode.



        I had this issue in the front end, as i recently moved the database from one server to another. I have managed to solve by this way.



        HOPE THIS HELPS SOME ONE.






        share|improve this answer


























          0












          0








          0







          THIS WORKED FOR ME AFTER TRYING EVERYTHING.



          Assuming your site is in Developer Mode, you can change it to Production Mode and clear/flush cache and then switch back to Developer Mode.



          I had this issue in the front end, as i recently moved the database from one server to another. I have managed to solve by this way.



          HOPE THIS HELPS SOME ONE.






          share|improve this answer













          THIS WORKED FOR ME AFTER TRYING EVERYTHING.



          Assuming your site is in Developer Mode, you can change it to Production Mode and clear/flush cache and then switch back to Developer Mode.



          I had this issue in the front end, as i recently moved the database from one server to another. I have managed to solve by this way.



          HOPE THIS HELPS SOME ONE.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Oct 22 '18 at 9:56









          ThowzifThowzif

          384




          384























              0














              Basically the same



              Magento 2 - Moving site - 'No such entity'



              cd /magento-root-path/var



              rm -rf *



              cd ../



              php bin/magento setup:upgrade



              rm -rf ./var/di



              php bin/magento setup:di:compile



              php bin/magento setup:static-content:deploy



              chown -R www-data .






              share|improve this answer






























                0














                Basically the same



                Magento 2 - Moving site - 'No such entity'



                cd /magento-root-path/var



                rm -rf *



                cd ../



                php bin/magento setup:upgrade



                rm -rf ./var/di



                php bin/magento setup:di:compile



                php bin/magento setup:static-content:deploy



                chown -R www-data .






                share|improve this answer




























                  0












                  0








                  0







                  Basically the same



                  Magento 2 - Moving site - 'No such entity'



                  cd /magento-root-path/var



                  rm -rf *



                  cd ../



                  php bin/magento setup:upgrade



                  rm -rf ./var/di



                  php bin/magento setup:di:compile



                  php bin/magento setup:static-content:deploy



                  chown -R www-data .






                  share|improve this answer















                  Basically the same



                  Magento 2 - Moving site - 'No such entity'



                  cd /magento-root-path/var



                  rm -rf *



                  cd ../



                  php bin/magento setup:upgrade



                  rm -rf ./var/di



                  php bin/magento setup:di:compile



                  php bin/magento setup:static-content:deploy



                  chown -R www-data .







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited 12 mins ago









                  Community

                  1




                  1










                  answered Jul 17 '16 at 1:02









                  Patrick-PengPatrick-Peng

                  5610




                  5610






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Magento Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f106793%2fmagento-2-reindex-returns-no-such-entity%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Magento 2 controller redirect on button click in phtml file

                      Polycentropodidae