Question Fatal error: Unable to load messages [SOLVED]

Hi there,

I recently installed Kunena on my site and have been getting the following message when selecting the discussions tabs regardless of template selected:


Fatal error: Unable to load messages.\nDB function failed with error number 1064
You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'SELECT thread, MAX(time) AS lastpost FROM jos_f SQL=SELECT a.thread, a.subject, b.lastpost FROM jos_fb_messages AS a JOIN ( SELECT thread, MAX(time) AS lastpost FROM jos_fb_messages WHERE time >'1231772480' AND hold=0 AND moved=0 AND catid IN (1,2,3,4,5,6,7) GROUP BY 1) AS b ON b.thread = a.thread WHERE a.parent=0 AND a.moved=0 AND a.hold=0 GROUP BY a.thread ORDER BY b.lastpost DESC LIMIT 100
SQL =
SELECT
a.thread,
a.subject,
b.lastpost
FROM
jos_fb_messages AS a
JOIN ( SELECT thread, MAX(time) AS lastpost
FROM jos_fb_messages
WHERE time >'12317724 in /homepages/6/d252528374/htdocs/.../components/com_kunena/lib/kunena.debug.php on line 37


I have read through all threads pertaining to similar issues with no success. I am not experiencing a timeout on install and my servers PHP version is 5.x

All tables in the database appear to be intact and populated.

Lastly, I tried installing fireboard before coming across Kunena with the same problem. Fireboard was uninstalled and all relevant tables dropped before re-installing Kunena.

I'd love to use this app with my website - it has tons of great features! Hope we can solve the problem!

Thanks for your input!
Randall

You have too old MySQL server. Upgrade MySQL to version 5.0.x.

Sorry!

Meant to say my servers MYsql version is 5.x

PHP version is 5.28
MYsql version is 5.0.67

I believe both are current enough to satisfy the operating requirements.

Your MySQL client is version 5.0.67. You should also check server version, because of we have seen this error already 2 times with MySQL client 5.0.67. Both times the server had been too old (4.0.x). That query is supported from MySQL 4.1. Maybe you have the same service provider?

Matias,

Thanks for the help!

Turns out although my server was offering MySQL 5.0 capabilities, my websites database was version 4.0 which is why certain db query's were throwing errors: just as you said!

I transferred all of my data to a MySQL 5.0 database and am no longer getting any errors!

The forum is GREAT!