Resolve the category flow "base table" error on the Magento 2.4.0 edition

If you’re getting the below error when you run the Magento Category to NetSuite Add/Update flow, and if the error is from Magento 2 server, to update the Magento 2 server and resolve the error, see Fix for empty category field values in REST calls #28828

Base table or view not found: 1146 Table 'ent240.catalog_category_product_index_store0' doesn't exist, query was: SELECT `cat_index`.`category_id`, count(cat_index.product_id) AS `count` FROM `catalog_category_product_index_store0` AS `cat_index` WHERE (cat_index.category_id in (3, 4, 5, 6)) GROUP BY `cat_index`.`category_i

Note: If you’re an existing customer migrating the Magento 2 instance from the previous Magento 2 edition, the category flow will not cause any error.

0

Comments

5 comments
Date Votes
  • Hi There - I'm getting the following response from magento when running this flow. It's a 503 error.  Any ideas?

    <html>
    <head>
    <meta charset="UTF-8">
    <title>503</title>
    </head>
    <body>
    <div><img src="https://xxxx.xxx.com/media/theme_customization/503.jpg" /> </div>
    </body></html>

     

    0
  • Hi David, 

    It looks like some issue in the Magento 2 server configuration, 
    Please try to get the category from postman using </all/V1/categories> url, if this is also giving the same error then follow the instructions from the article https://support.magento.com/hc/en-us/articles/360034631211-Troubleshooting-503-error-caused-by-necessity-to-change-default-Varnish-settings 
    If you are not using Varnish then try to clear the cache from backend and rerun the flow

    0
  • Hi Sanjay,

    The call works with /V1/categories in postman.  There's only one store id defined in this Magento setup.  Do you know more about the /all?? I read the article you posted and it doesn't seem very relevant but I'll have the Magento team review it.   

    0
  • David Gollom

    /all is used to get all category from each and every stores. It looks like permission issue, login into the M2 admin portal and click on system->userRoles and check the role scope permission to your user, if its is custom then change this to all. then it will work fine with all* in the URL.

    0
  • Thanks Sanjay!! I'll give that a try.  

    0

Please sign in to leave a comment.

 

Didn't find what you were looking for?

New post