After upgrading Magento 1.9.1 to manually via FTP, the site works fine except when you get to the checkout success page. It is blank.

The exception log shows that the core_email_queue_recipients table is missing.

Checking the database with MySQL Workbench shows that it is indeed missing. I am assuming that the SQL upgrade script did not fire, but I have no idea how to fire this.

Some sources say to go to the core_resources table and modify the database version value there to make it fire, but they don't mention which 'code' field value is the database version. See https://community.magento.com/t5/Version-Upgrades/1-9-0-1-to-1-9-2-2-missing-core-email-queue-table/td-p/22350

Any ideas?


It's little tricky and requires some research.

You can go to core_resources table and find the core_setup.

Now, check the version and data_version.

Then, go to Mage/Core/sql/core_setup/upgrade-

If you don't find this file, then you might not have copied all files properly.

If you can confirm you have missed that file then simply see what is your last file in Mage/Core/sql/core_setup folder and get the version number from there.

For example if you find the file name as: mysql4-upgrade-0.8.5-0.8.6.php then I will copy 0.8.6 as my version.

Now, copy all missing files in that folder and change core_setup's version and data_version as 0.8.6 in database. Then, go to Mage/etc/config.xml and change the version name here too.

And clear the cache.

Hope this helps.

  • Thanks for the quick response! I don't see this path on the server or in the Magento download for CE at magento.com/tech-resources/download under the 8th section labeled ver - Added Nov 14, 2016. The closest thing to it is app/code/core/Mage but there isn't a sql folder there. Jan 12 '17 at 0:47
  • It's app/code/core/ then the Mage/Core/sql/core_setup Jan 12 '17 at 0:48
  • Thanks - found it. In that folder there are the following files install- mysql4-data-upgrade- mysql4-install-0.7.0.php mysql4-install-0.8.0.php mysql4-upgrade-0.6.26-0.7.0.php mysql4-upgrade-0.7.1-0.7.2.php mysql4-upgrade-0.7.2-0.7.3.php mysql4-upgrade-0.7.3-0.7.4.php mysql4-upgrade-0.7.4-0.7.5.php mysql4-upgrade-0.7.5-0.7.6.php mysql4-upgrade-0.7.6-0.7.7.php mysql4-upgrade-0.7.7-0.7.8.php mysql4-upgrade-0.7.8-0.7.9.php mysql4-upgrade-0.8.0-0.8.1.php mysql4-upgrade-0.8.1-0.8.2.php mysql4-upgrade-0.8.2-0.8.3.php mysql4-upgrade-0.8.3-0.8.4.php Jan 12 '17 at 1:05
  • mysql4-upgrade-0.8.4-0.8.5.php mysql4-upgrade-0.8.5-0.8.6.php mysql4-upgrade-0.8.6-0.8.7.php mysql4-upgrade-0.8.7-0.8.8.php mysql4-upgrade-0.8.8-0.8.9.php mysql4-upgrade-0.8.9-0.8.10.php mysql4-upgrade-0.8.10-0.8.11.php mysql4-upgrade-0.8.11-0.8.12.php mysql4-upgrade-0.8.12-0.8.13.php mysql4-upgrade-0.8.13-0.8.14.php mysql4-upgrade-0.8.14-0.8.15.php mysql4-upgrade-0.8.15-0.8.16.php mysql4-upgrade-0.8.16-0.8.17.php mysql4-upgrade-0.8.17-0.8.18.php mysql4-upgrade-0.8.18-0.8.19.php mysql4-upgrade-0.8.19-0.8.20.php mysql4-upgrade-0.8.20-0.8.21.php Jan 12 '17 at 1:07
  • 1
    I rolled the server back due to uneasiness about these tables missing. The database version in core_resource was likely set to before I updated from to 1.9.1 due to a security patch error. When the website completed its update it did not execute the .SQL update file. Changing core_setup in core_resource table from to caused the SQL file to run and properly update the database. So your solution was correct and I confirmed at community.magento.com/t5/Version-Upgrades/… Jan 12 '17 at 19:17

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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