Hi, i am dying to get my hands on testing out magento but faced the below problem when i tried to install via simplescripts. Will anyone be able to help?
Fatal error: Uncaught exception ‘Mage_Core_Model_Store_Exception’ in /home/imbccoms/public_html/shop/app/code/core/Mage/Core/Model/App.php:1056 Stack trace: #0 /home/imbccoms/public_html/shop/app/code/core/Mage/Core/Model/App.php(545): Mage_Core_Model_App->throwStoreException() #1 /home/imbccoms/public_html/shop/app/Mage.php(577): Mage_Core_Model_App->getStore() #2 /home/imbccoms/public_html/shop/app/Mage.php(439): Mage::printException(Object(Zend_Db_Adapter_Exception)) #3 /home/imbccoms/public_html/shop/index.php(40): Mage::run() #4 {main} thrown in /home/imbccoms/public_html/shop/app/code/core/Mage/Core/Model/App.php on line 1056
Same thing here on BlueHost. I’d really like to see if this does what I need, but ...
Fatal error: Uncaught exception ‘Mage_Core_Model_Store_Exception’ in /home/sixoneze/public_html/blinn-com/MagentoTest/app/code/core/Mage/Core/Model/App.php:1056 Stack trace: #0 /home/sixoneze/public_html/blinn-com/MagentoTest/app/code/core/Mage/Core/Model/App.php(545): Mage_Core_Model_App->throwStoreException() #1 /home/sixoneze/public_html/blinn-com/MagentoTest/app/Mage.php(577): Mage_Core_Model_App->getStore() #2 /home/sixoneze/public_html/blinn-com/MagentoTest/app/Mage.php(439): Mage::printException(Object(Zend_Db_Adapter_Exception)) #3 /home/sixoneze/public_html/blinn-com/MagentoTest/index.php(40): Mage::run() #4 {main} thrown in /home/sixoneze/public_html/blinn-com/MagentoTest/app/code/core/Mage/Core/Model/App.php on line 1056
I see posts here and elsewhere about this problem, but so far no solutions.
1. These errors are the result of a low memory condition. This could be related to a lot of configuration factors; Everything from the environment available memory to the php.ini memory configurations and as complex as the apache keepalive and MPM module configurations.
Each of these things would make it so that the system work work, until it ran out of memory - then it would throw the error. I think a system restart can rule out this problem.
2. PHP extensions directory location changes. This is common with the very popular CPanel control panel. CPanel has a nasty habit of changing your lib dir to it’s own custom location. This can cause a lot of problems if your PDO is not located in this new setting. However, this issue could only be caused by some sort of php/apache recompilation/upgrade. Keep in mind that many CPanels are set to ‘automatically’ upgrade themselves when patches are available, which could easily lead to this lib directory changing.
I would think this would be common only in shared hosting environments. Shared hosts sometimes rebuild apache without paying close enough attention to this particular configuration value and it’s certainly not an ‘expected’ result of recompilation.
I’m going to run some tests on lab hosting environments to see if I can find a way to replicate this error
If anyone has any other idea’s or things that you think would be important to look at it would be appreciated.
I accidentally chopped my original reply by editing it.
I was asking if you guys could give any details regarding your hosting environment?
Things like;
1. VPS / Shared hosting?
2. If VPS how much RAM/Memory (guaranteed)
3. Apache/PHP configuration details
4. Caching systems in place? eAcellerator/APC?
5. Anything unusual about your configuration that might be able to help replicate this issue?
Appreciate any feedback you can gxive.
My client’s site suddenly is having the exact same problem, I was in panic until I saw your post. Thank you!
Here is the server info:
1. Shared hosting with Cpanel.
I don’t know anything about the caching systems, as for the Apache/PHP confiiguration, I think it’s up to par as I have not encountered any problem testing Magento store until now.
If you want the PHP info, let me know, I will PM you.
I realized that code you asked me to replace, matches the latest version, which I have not upgraded yet based on these :
@ryanb - since the packages are over-writing the code there should not be an issue to skip a version.
@ryanb: You can skip it, unless you are unhappy with the other bugs we have provided fixes for. It’s up to you, just review the release notes carefully.
I thought I will skip it till the next major upgrade in June. Now with this error, must I upgrade?
and here my the php info: http://74.52.59.43/phpinfo.php
I think the server is up to par.
Oh, also, here the replaced code in the Mage.php - I actually replaced it with the latest version soon after I saw the new error. THought it will make a different but obviously not.
public static function getIsDeveloperMode() { return self::$_isDeveloperMode; }
/** * Display exception * * @param Exception $e */ public static function printException(Exception $e, $extra = '') { if (self::$_isDeveloperMode) { print '<pre>';
@chinesedream: you do not have PDO installed. Also make sure pdo_mysql is installed.
Moshe, thank you so much and so sorry! I should have double check many times the phpinfo - the scrolling of the file made me lose sight of it (though that shouldn’t be an excuse!). The host didn’t upgrade the sever properly I believe.