Skip to content
Visit ShipperHQ.com
  • There are no suggestions because the search field is empty.

How Do I Resolve a Failed SQL Run in Magento

Fix SQL errors in Magento installations for successful ShipperHQ setup

Table of Contents

Overview

When you install the ShipperHQ extension, it usually runs SQL as part of the installation. If you see an error report on the frontend afterward, it might be due to the SQL not running successfully or a mistake in file copying. Common reasons for SQL errors include:

  • Unique Index Too Long
  • The SQL has already run on this server, causing a conflict by attempting to run twice (rare and happens if the database was manually modified)
  • The frontend was updated during installation, attempting to run SQL install or upgrade before files were present

You may encounter errors like SQLSTATE[42S02]: Base Table Or View Not Found. Before proceeding, ensure:

  • All files are installed correctly (including Common/Logger)
  • Check the report in var/report for clues about the issue

If attributes are missing or tables not found, it's likely issue 3 above. You can resolve this by rewinding the core_resource.

Magento 1

Manually rewind core_resource

Follow these steps to resolve the issue. It's recommended to be familiar with phpMyAdmin; otherwise, consult a developer:

  1. Take a full database backup
  2. Locate the 'core_resource' table
  3. Browse the table for the entry causing the issue (e.g., shipperhq_shipper_setup)
  4. Remove that entry alone
  5. Ensure cache is switched off
  6. Refresh the frontend
  7. Check that the install script has now run and created the missing tables and attributes

Script delete/rewind core_resource (Recommended)

We offer a script to delete/rewind the core_resource entry. Ensure you have the latest WSA Common installed to run the script successfully.

Delete core_resource

Use this script only if it's the first installation of this extension. ⚠️ Disclaimer - Do not use this script unless confident. WebShopApps/ShipperHQ cannot be held responsible for the outcome.

  1. Take a full database backup
  2. Add the script file (setResource.php) to the base of your Magento install
  3. Navigate to your base Magento URL followed by '/setResource.php' (e.g., www.magento.com/setResource.php)
  4. Select the extension from the dropdown, which may require running in multiple parts. If you can't see your extension, add the core_resource code manually (e.g., shipperhq_shipper_setup)
  5. Click Show Current Resource Version to continue
  6. Click delete to remove the core_resource row corresponding to your extension
  7. Refresh the frontend
  8. Verify the script has run correctly, creating the attributes
  9. If there's an error related to another table, revisit setResource.php and select the next module
  10. Remove the script file after use
Rewind Resource

This same script includes a rewind option that rolls back to an earlier version, prompting Magento to run the upgrade script for the SQL. Use only if confident, as WebShopApps/ShipperHQ is not responsible for outcomes.

  1. Take a full database backup
  2. Add the script file (setResource.php) to the base of your Magento install
  3. Navigate to your base Magento URL followed by '/setResource.php'
  4. Select the extension from the dropdown. If not visible, add the core_resource code manually by referencing app/code/community/shipperhq/module name/etc/config.xml
  5. Click Show Current Resource Version to continue
  6. Note and roll-back the module version if needed (e.g., from 1.0.6 to 1.0.5)
  7. Click rewind
  8. Refresh the frontend
  9. Verify the script has run correctly, creating the attributes
  10. Remove the script file after use

Magento 2

To resolve the issue:

  1. Take a full database backup
  2. Locate the 'setup_module' table
  3. Browse the table for the entry causing the issue (e.g., shipperhq_shipper)
  4. Remove that entry alone
  5. Run php bin/magento setup:upgrade from the command line
  6. Refresh indexes, compiler (if enabled), and cache (if enabled)
  7. Refresh the frontend
  8. Verify that the install script has run and created the missing tables and attributes

Further Help 😊

If problems persist:

  1. Identify the actual error. If only a report number is given, locate the report in the var/reports directory
  2. Disable the extension for further inspection
  3. Contact ShipperHQ Support with your order details, error report, and description of the issue for diagnosis