-
- UGD

-
Total Posts: 22
Joined: 2008-09-08
|
Now that I found the error code I am getting the following message. I understand it has to do with sql & the database but how to I fix it? Full code is:
a:5:{i:0;s:242:"Error in file: “/app/code/core/Mage/Paypal/sql/paypal_setup/mysql4-upgrade-0.7.3-0.7.4.php” - SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘sales_order_entity_varchar’ doesn’t exist";i:1;s:1038:"#0 /app/code/core/Mage/Core/Model/Resource/Setup.php(390): Mage::exception(’Mage_Core’, ‘Error in file: ...’)
#1/app/code/core/Mage/Core/Model/Resource/Setup.php(289): Mage_Core_Model_Resource_Setup->_modifyResourceDb(’upgrade’, ‘0.7.3’, ‘1.4.0.2’)
#2 /app/code/core/Mage/Core/Model/Resource/Setup.php(233): Mage_Core_Model_Resource_Setup->_upgradeResourceDb(’0.7.3’, ‘1.4.0.2’)
#3/app/code/core/Mage/Core/Model/Resource/Setup.php(161): Mage_Core_Model_Resource_Setup->applyUpdates()
#4/app/code/core/Mage/Core/Model/App.php(399): Mage_Core_Model_Resource_Setup::applyAllUpdates()
#5/app/code/core/Mage/Core/Model/App.php(329): Mage_Core_Model_App->_initModules()
#6/app/Mage.php(627): Mage_Core_Model_App->run(Array)
#7 /index.php(80): Mage::run(’’, ‘store’)
#8 {main}”;s:3:"url”;s:16:"/Store/index.php”;s:11:"script_name”;s:16:"/Store/index.php”;s:4:"skin”;s:7:"default";}
|
| |
-
- Posted: March 14 2011
-
| top
-
|
 |
 |
 |
|
|
-
- ladle

-
Total Posts: 175
Joined: 2009-06-11
|
Honestly, with that message, your best bet is to get familiar with the Database Repair tool offered in the download section. I’ll tell you why.
You have a missing table, so you can either
A. Find the sql query to create it, but chances are there might be others you are missing.
B. Delete the record of the upgrade from the core_resources table so that you force the reinstall, but then you will get errors about tables already existing, and you will have to deal with that one way or another. Either dropping tables and letting the installer re-create, or commenting out the particular query in the php files (pain in the ass)
C. Install a clean copy of Magento on another directory of the same version you are running, and then read and follow the instructions for the DB repair tool. This will cleanly add the missing tables for you, and any missing foreign keys etc from existing tables. I’ve found it’s a really good tool, but not many people talk about it much here, and I’m not sure why, as I’ve solved some major problems with it.
Of Course, BACKUP YOUR DATABASE prior to any of the above methods.
|
| |
-
- Posted: March 14 2011
-
| top
| # 1
-
|
 |
 |
 |
|
|
-
- ladle

-
Total Posts: 175
Joined: 2009-06-11
|
And to be more precise. Looking at your error message, it looks like the installer is trying to create a table that is dependent upon another table or view that doesn’t exist, so it can’t create the new one.
Again, the DB repair tool, WILL fix this.
|
| |
-
- Posted: March 14 2011
-
| top
| # 2
-
|
 |
 |
 |
|
|
-
- UGD

-
Total Posts: 22
Joined: 2008-09-08
|
Thank you for the help so far. After downloading the database repair tool and entering my information I now get an error in the database tool screen that reads:
Reference database connection error: #0
what does this mean? I have set-up the new reference database without any information in it. Setup a new User & Password because I wasn’t sure about my other user information. Linked it to that database but this is the error I get.
|
| |
-
- Posted: March 16 2011
-
| top
| # 3
-
|
 |
 |
 |
|
|
-
- UGD

-
Total Posts: 22
Joined: 2008-09-08
|
I finally got it to run the database tool. There are several modules that have wrong version numbers and I’m not sure how to fix them. If I click continue in the database tool it doesn’t find anything to fix (fixed it all the first time I ran it) but it still comes up with the module version issue and the frontend is still not working.
|
| |
-
- Posted: March 16 2011
-
| top
| # 4
-
|
 |
 |
 |
|
|
-
- ladle

-
Total Posts: 175
Joined: 2009-06-11
|
UGD - 15 March 2011 05:31 PM I finally got it to run the database tool. There are several modules that have wrong version numbers and I’m not sure how to fix them. If I click continue in the database tool it doesn’t find anything to fix (fixed it all the first time I ran it) but it still comes up with the module version issue and the frontend is still not working.
Is your admin working?
Also have you cleared out your cache?
|
| |
-
- Posted: March 16 2011
-
| top
| # 5
-
|
 |
 |
 |
|
|
-
- UGD

-
Total Posts: 22
Joined: 2008-09-08
|
Nothing is working expect for the error message and running the database repair tool.
I have cleaned out the var/cache & var/session folders multiple times trying to get it to work. I have no idea how to get these modules repaired and couldn’t find anything through the magento site search. i keep looking though.
This is what the Database repair tool is giving me
Module versions differences
* Module “bundle_setup” has wrong version 0.1.7 in corrupted DB (reference DB contains “bundle_setup” ver. 0.1.14)
* Module “downloadable_setup” has wrong version 0.1.14 in corrupted DB (reference DB contains “downloadable_setup” ver. 1.4.0.2)
* Module “find_feed_setup” is not installed in corrupted DB
* Module “importexport_setup” is not installed in corrupted DB
* Module “log_setup” has wrong version 0.7.6 in corrupted DB (reference DB contains “log_setup” ver. 0.7.7)
* Module “paypal_setup” has wrong version 0.7.3 in corrupted DB (reference DB contains “paypal_setup” ver. 1.4.0.2)
* Module “review_setup” has wrong version 0.7.4 in corrupted DB (reference DB contains “review_setup” ver. 0.7.6)
* Module “tag_setup” has wrong version 0.7.2 in corrupted DB (reference DB contains “tag_setup” ver. 0.7.7)
* Module “tax_setup” has wrong version 0.7.8 in corrupted DB (reference DB contains “tax_setup” ver. 1.4.0.1)
* Module “xmlconnect_setup” is not installed in corrupted DB
|
| |
-
- Posted: March 16 2011
-
| top
| # 6
-
|
 |
 |
 |
|
|
-
- ladle

-
Total Posts: 175
Joined: 2009-06-11
|
Have you gotten any further? I’ve been pretty busy last couple days.
|
| |
-
- Posted: March 19 2011
-
| top
| # 7
-
|
 |
 |
 |
|
|
-
- ladle

-
Total Posts: 175
Joined: 2009-06-11
|
UGD - 15 March 2011 09:07 PM Nothing is working expect for the error message and running the database repair tool.
I have cleaned out the var/cache & var/session folders multiple times trying to get it to work. I have no idea how to get these modules repaired and couldn’t find anything through the magento site search. i keep looking though.
This is what the Database repair tool is giving me
Module versions differences
* Module “bundle_setup” has wrong version 0.1.7 in corrupted DB (reference DB contains “bundle_setup” ver. 0.1.14)
* Module “downloadable_setup” has wrong version 0.1.14 in corrupted DB (reference DB contains “downloadable_setup” ver. 1.4.0.2)
* Module “find_feed_setup” is not installed in corrupted DB
* Module “importexport_setup” is not installed in corrupted DB
* Module “log_setup” has wrong version 0.7.6 in corrupted DB (reference DB contains “log_setup” ver. 0.7.7)
* Module “paypal_setup” has wrong version 0.7.3 in corrupted DB (reference DB contains “paypal_setup” ver. 1.4.0.2)
* Module “review_setup” has wrong version 0.7.4 in corrupted DB (reference DB contains “review_setup” ver. 0.7.6)
* Module “tag_setup” has wrong version 0.7.2 in corrupted DB (reference DB contains “tag_setup” ver. 0.7.7)
* Module “tax_setup” has wrong version 0.7.8 in corrupted DB (reference DB contains “tax_setup” ver. 1.4.0.1)
* Module “xmlconnect_setup” is not installed in corrupted DB
Assuming you have a good backup of your “corrupt” database. You can go the core_resources table and change the version numbers to match that of the reference database for all the above mentioned modules. For example change your bundle_setup to 0.1.14, there will be two columns where you’ll need to update the version number. Just make them match all the reference database versions.
You’ll be telling magento that it has completed the module updates already (which it hasn’t), and you’ll be missing the tables it should have created. But then, you can re-run the db repair tool, and it will fix it by adding the tables and foreign keys.
But, then, you might still get errors, that certain php scripts are trying to execute because base table or view already exists. At this point you can comment out the particular php files. And it won’t matter that they ever run, because the database repair tool has already added everything you need.
Hope this makes sense.
EDIT: After thinking on this some more, you shouldn’t see the final problem mentioned of the scripts trying to execute, because it should recognize the version numbers as already being up to date. Let me know if it works for you. Good luck!
|
| |
-
- Posted: March 19 2011
-
| top
| # 8
-
|
 |
 |
 |
|
|
-
- Alex Krenvalk

-
Total Posts: 6
Joined: 2009-09-04
|
UGD - 14 March 2011 08:08 AM Now that I found the error code I am getting the following message. I understand it has to do with sql & the database but how to I fix it? Full code is:
a:5:{i:0;s:242:"Error in file: “/app/code/core/Mage/Paypal/sql/paypal_setup/mysql4-upgrade-0.7.3-0.7.4.php” - SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘sales_order_entity_varchar’ doesn’t exist";i:1;s:1038:"#0 /app/code/core/Mage/Core/Model/Resource/Setup.php(390): Mage::exception(’Mage_Core’, ‘Error in file: ...’)
#1/app/code/core/Mage/Core/Model/Resource/Setup.php(289): Mage_Core_Model_Resource_Setup->_modifyResourceDb(’upgrade’, ‘0.7.3’, ‘1.4.0.2’)
#2 /app/code/core/Mage/Core/Model/Resource/Setup.php(233): Mage_Core_Model_Resource_Setup->_upgradeResourceDb(’0.7.3’, ‘1.4.0.2’)
#3/app/code/core/Mage/Core/Model/Resource/Setup.php(161): Mage_Core_Model_Resource_Setup->applyUpdates()
#4/app/code/core/Mage/Core/Model/App.php(399): Mage_Core_Model_Resource_Setup::applyAllUpdates()
#5/app/code/core/Mage/Core/Model/App.php(329): Mage_Core_Model_App->_initModules()
#6/app/Mage.php(627): Mage_Core_Model_App->run(Array)
#7 /index.php(80): Mage::run(’’, ‘store’)
#8 {main}”;s:3:"url”;s:16:"/Store/index.php”;s:11:"script_name”;s:16:"/Store/index.php”;s:4:"skin”;s:7:"default";}
recover sql database allows you to save critical data and avoid losing it. Tool recovers System Tables and User Tables, Stored Procedures, Views, User Defined Data Types and Functions. It works with big databases more than 16TB. Application doesn’t modify source database file.
|
| |
-
- Posted: March 3 2012
-
| top
| # 9
-
|
 |
 |
 |
|
|