[SOLVED] Joomla Error 500

Problem installing CB-quickstart 1.1

Following message in Joomla backpanel occurs after having tried to install CB-quickstart-pro_1.1

In first install only 3 files installed with success:
002_mod_cb_adminnav
0007_mod_cb_gallery
008_mod_cbgroupjivc

all other files were listed on the right 'failed' column (fig 1 in manual)
then installing a second time as is suggested in manual, following message resulted

Joomla!
500 - An error has occurred.

MySQL server has gone away SQL=SELECT a.id, a.title, a.checked_out, a.checked_out_time, a.created, a.hits,l.title AS language_title,uc.name AS editor,ag.title AS access_level,c.title AS category_title,ua.name AS author_name FROM cfzl3_content AS a LEFT JOIN `cfzl3_languages` AS l ON l.lang_code = a.language LEFT JOIN cfzl3_users AS uc ON uc.id=a.checked_out LEFT JOIN cfzl3_viewlevels AS ag ON ag.id = a.access LEFT JOIN cfzl3_categories AS c ON c.id = a.catid LEFT JOIN cfzl3_users AS ua ON ua.id = a.created_by ORDER BY a.hits DESC LIMIT 0, 5

with subsequently following message:
Database connection error (2): Could not connect to MySQL.

and unability to access anymore the Joomla admin panel
(Joomla 2.5.7 - hosting ukhosting - last week with the former quickpro version install was without problem, so I do no dot think problem is with the server, as all requirements are fullfilled).

To fully inform you.
I am using Rockettheme Metropolis template installed with RocketLauncher for latest november template Metropolis. Instead of Joomla admin panel, I used the RT Mission Control admin panel. Then the admin panel disappeared and went unaccessible, had to reinstall everything. and used then the Joomla admin panel.

Now occurs another admin panel disappearing, after installing CB with CB Quickstart Pro
Database connection error (2): Could not connect to MySQL.
while admin panel totally disappeared.
I will not exclude that the template RT Metropolis is causing the disappearing or bad functioning of admin panel, but it occurs now at installing CB.


Any suggestion, help?
Thanks.
Jan Sansen
jansansen@gmail.com
travelclub.com

[quote="juanpaul" post=213979
Joomla!
500 - An error has occurred.

MySQL server has gone away SQL=SELECT a.id, a.title, a.checked_out, a.checked_out_time, a.created, a.hits,l.title AS language_title,uc.name AS editor,ag.title AS access_level,c.title AS category_title,ua.name AS author_name FROM cfzl3_content AS a LEFT JOIN `cfzl3_languages` AS l ON l.lang_code = a.language LEFT JOIN cfzl3_users AS uc ON uc.id=a.checked_out LEFT JOIN cfzl3_viewlevels AS ag ON ag.id = a.access LEFT JOIN cfzl3_categories AS c ON c.id = a.catid LEFT JOIN cfzl3_users AS ua ON ua.id = a.created_by ORDER BY a.hits DESC LIMIT 0, 5

with subsequently following message:
Database connection error (2): Could not connect to MySQL.

and unability to access anymore the Joomla admin panel
(Joomla 2.5.7 - hosting ukhosting - last week with the former quickpro version install was without problem, so I do no dot think problem is with the server, as all requirements are fullfilled).
[/quote]

The error message indicates that something went bad with your database services - please ask your hosting helpdesk if they are having issues (and show them the messages above).

Hello Nant
thank you for answering
I also contacted my server ukhosting and they answered as follows:

---

Hello Jan,
These errors should no longer be occurring as we have disabled the InnoDB engine for MySQL which was causing MySQL crashes due to corruption until we can finish completely restoring all corrupted databases.

---

so its was, as for now I have reinstalled CB quickpro and everything went smooth; right 'failed' column remains empty
thank you for your support

correction
well, one small issue:
after installation, when willing to access CB from components, it - Community Builder - did (at first) not appear, only as 'component profile' or something followed by an 404 error , then clicking back to Control Panel 'Community Builder' did appear under Components. I guess everything should be OK now.

Jan

Great - thanks for confirming it was a hosting failure.