Sudden Magento Failure - The session id is too long or contains illegal characters + Can't retrieve entity config

Magento Failure

You'll be cooking soon.
Suddenly, your magento starts showing error reports instead of shopping carts. Your product pages just show an error exception. And you cannot logon. One of the basic skills that a good Magento cart builder needs to know is how to recover their server from near death.  We are quite skilled at all things Magento. Here's how to fix it by deleting the cache and session pool, once you do this, you will be cooking with gas again.

So, you look in var/report and find the report file, and the first things it says is:

a:5:{i:0;s:46:"Can't retrieve entity config: sales/quote_item";i:1;s:4545:"#0 /home/needfulthings/public_html/app/code/core/Mage/Core/Model/Resource.php(282): Mage::throwException('Can't retrieve ...')
#1 /home/needfulthings/public_html/app/code/core/Mage/Core/Model/Resource/Db/Abstract.php(276): Mage_Core_Model_Resource->getTableName('sales/quote_ite...')

Plus in ./var/log/system.log, you see this:

...
2019-06-17T02:49:35+00:00 ERR (3): Warning: session_start(): The session id is too long or contains illegal characters, valid characters are a-z, A-Z, 0-9 and '-,'  in /home/needfulthings/public_html/app/code/core/Mage/Core/Model/Session/Abstract/Varien.php on line 134
2019-06-17T02:49:35+00:00 ERR (3): Warning: session_start(): The session id is too long or contains illegal characters, valid characters are a-z, A-Z, 0-9 and '-,'  in /home/needfulthings/public_html/app/code/core/Mage/Core/Model/Session/Abstract/Varien.php on line 134

It happens because there is junk in the magento cache.
clean out your cache and delete your sessions from:

Delete the contents of the following directories, assuming your magento is installed in ~/

~/public_html/var/cache
~/public_html/var/session



Comments

Popular posts from this blog

Microsoft Visio 2010 Premium Product Keys

Mercedes Benz Diesel CDI EGR Emulator Circuit Diagrams

Fix: The Diagnostic Service Host service failed to start due to the following error. [ solved, no kidding ]