I am finding the several instances of the following error in my log file after upgrading from Drupal 4.52 to 4.6:

Location:
/node/add/forum?edit[og_groups][]=1

Message:
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 'DISTINCT(c.nid), c.subject, c.pid, u.name FROM mmex_comments c query: SELECT DISTINCT(c.cid), DISTINCT(c.nid), c.subject, c.pid, u.name FROM mmex_comments c INNER JOIN mmex_users u ON u.uid = c.uid WHERE c.status = 0 AND c.timestamp > 1113868936 ORDER BY c.nid, c.timestamp in /...my_host_path/includes/database.mysql.inc on line 66.

Severity:
error

I believe it is related to the Organic Groups module, but cannot isolate it to anything that I can correct. Is anyone else having this problem?

Comments

Donovan’s picture

Here is another related error message that I am receiving:

user error: 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 'DISTINCT(c.nid), c.subject, c.pid, u.name FROM mmex_comments c
query: SELECT DISTINCT(c.cid), DISTINCT(c.nid), c.subject, c.pid, u.name FROM mmex_comments c INNER JOIN mmex_users u ON u.uid = c.uid WHERE c.status = 0 AND c.timestamp > 1113877409 ORDER BY c.nid, c.timestamp in /homepages/38/d97894505/htdocs/mmex/includes/database.mysql.inc on line 66.

I get one of these for every member in an organic group so the problem is definitely related; however, I have searched the og module for the referenced code and cannot find it anywhere. Any thoughts on causes and remedies are greatly appreciated.

"It always seems impossible, until it is done."
- Nelson Mandela

sepeck’s picture

Have you updated your OG module? If not make sure that there is a supported module for 4.6

-sp
---------
Test site...always start with a test site.
Drupal Best Practices Guide

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

Donovan’s picture

Thanks sepek. I am using the latest 4.6 version of the OG module; however, I could not find and update instructions so I manually updated the existing og table (from 4.5.2) to ad the new fields, then executed the SQL for the new og_uid table. It's quite possible that the problem might be related to this but I can't find anything concrete to go on.

"It always seems impossible, until it is done."
- Nelson Mandela

green monkey’s picture

I've just completed a clean install of 4.6 and received this error in the log.

page not found 04/18/2005 - 03:46

scripts/..\\../winnt/system32/cmd.exe not found. Anonymous

what could be casuing this

I tried to "search" the fourm to see if there was any info on this error msg, but the search module bombs out on the phrase

thanks for any ideas

Donovan’s picture

UPDATE: Problem was caused by Notify module. It turns out that the CVS version of the Notify module had a bug that caused the SQL errors. This is not a Drupal core bug or issue. Gerhard (Killes) will be posting an update to Notify shortly.

"It always seems impossible, until it is done."
- Nelson Mandela