asked on

Joomla 3.4 session error

Receive this error after the server was restarted.

Error displaying the error page: Application Instantiation Error: Table '<dbname>.<prefix>_session' doesn't exist SQL=DELETE FROM `<prefix>_session` WHERE `time` < '1431620203'

Terry

ASKER

I was able to resolve the problem above by deleting the <prefix>_session.frm file and running the following script from workbench. HOWEVER.... I now receive table does not exist errors for template_styles and usergroups tables.

drop table <prefix>_session;
CREATE TABLE IF NOT EXISTS `<prefix>_session` (
`session_id` varchar(200) NOT NULL DEFAULT '',
`client_id` tinyint(3) unsigned NOT NULL DEFAULT 0,
`guest` tinyint(4) unsigned DEFAULT 1,
`time` varchar(14) DEFAULT '',
`data` mediumtext,
`userid` int(11) DEFAULT 0,
`username` varchar(150) DEFAULT '',
PRIMARY KEY (`session_id`),
KEY `userid` (`userid`),
KEY `time` (`time`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

ASKER CERTIFIED SOLUTION

Peter Hart

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

Terry

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Terry

ASKER

I've requested that this question be closed as follows:

Accepted answer: 0 points for tri-data's comment #a40829857

for the following reason:

I accept my own solution. Sadly, I only received a few guesses, and they were weeks after the event.

Peter Hart

I suggested your database was corrupted.

I believe I gave you the answer
in your closing comment you have added new information that wasn't there in the question.

Terry

ASKER

Sorry. I can accept your answer as solution if this makes you happy, but the time has been so long for a reply on this post, that I have already solved this myself.

Peter Hart

I would delete the question as it had incomplete information to get an answer

Terry

ASKER

After much research, table corruption appears to happen often with the InnoDB engine. You can find numerous Joomla posts on the internet. Unfortunately, everyone thus far has only had one option, resort to backup. There does not appear to be a way to recover with current data when InnoDB eats the tables.