I just found a solution: When i install ExpressionEngine on a completely new Database instead of overwrite the old one, the error doesn´t appear. Maybe it also works, when i manually drop all tables from the database.

mhale0, was this a brand new install, or an upgrade? If an upgrade, which build/version were you on previously?

I’ve just been experiencing a similar problem.  It’s with an under-development site, so I haven’t been able to experiment with a fresh install.  I was made aware of the issue after one of the content editors emailed me to let me know that after deleting some comments, she could no longer access the Content > Edit page.  After checking it myself, I receive the exact same SQL error as jparavisini.

Some odd things I discovered while banging my head against this yesterday:

-  the error only occurs on the server (hosted via Engine Hosting).  A local copy of the files (identical save the database/file path config) and a local copy of the database don’t exhibit the error at all

-  I updated to the latest build (to 20100810 from 20100720) and that didn’t fix it

-  I dropped all tables from the database and tried recreating it from a couple of different dump files.  One from after the error started showing, and one from several weeks back before the error started showing up.  Neither had any effect on the Edit page and I continued to receive the SQL error.

As changing the files and changing the database has no affect, I assume that it’s something to do with a cache somewhere that’s interfering.  I’ve cleared all of the server caches to the best of my ability, to no effect.

This morning I had an idea to check in with a different browser.  I was receiving the error yesterday in Chrome (5.0.375.127), so I tried Safari 5 and Firefox 3.6.6 (all on a Mac).  To my surprise, the edit screen came up just fine in Safari and Firefox!  I can only guess that this is some issue with Chrome caching something that posts to the Edit page, breaking the SQL query.  Can anyone else who has experienced this issue weigh in on what browser they were having trouble with and if switching browsers had any affect for them?

I think I might have the culprit: cookies.

I followed the browser thought further and removed all my cookies from the domain causing trouble and that cleared up the problem.  I should have been a bit more surgical, removing each cookie in turn to see which was the problem, but unfortunately blasted the lot at once.  However, comparing the new cookies to my sketchy memory of the offending cookies, I think I recall seeing “exp_perpage” set to “per”, instead of 50.  If so, that might be the one.  Hopefully this’ll be of some help to anyone who hits this issue in the future.

Richard, welcome to the forums and thank you for the highly detailed analysis.

Content is indeed loaded into the main Edit page dynamically, and it’s possible that old (no longer valid) filtering settings could cause this.

Is anyone still experiencing this issue? mhale0? jparavisini?

My errors only occur when attempting to edit an entry (specifically to delete some spam comments.)
As soon as I click “Content > Edit” I get the error.

And yes: fresh install, not using the Agile Records theme.

I’m hosted on EngineHosting.

My ee_wizard results came back as “supported” in all cases.

Whoops-

Only saw the second page of this thread after posting my previous.
(I’ve been away for a bit, sorry!)

Deleting the exp_perpage cookie fixed the problem.
Thanks to Richard and all the mods for sticking it out and finding a solution.

Matt

Glad to see that fixed the problem. Please post again in case there’s anything else.