Database error message Dave!!

In clicking around in the "Jokes and chat forum" I got this error message a few times.

Database error: Cannot use Database Gardening
MySQL error:2014(Commands out of sync, you can't run this command now)
Session halted

Just thought I would let you know, I had to X out of it and come right back, wouldn't let me hit my < button or refresh button.
It only done it 3 times, like when I was looking at the threads.
Hope it's not a big problem, but I thought you might need to know about it.

It happened to me in the prayer forum, too, trying to access two different threads. I was able to hit back and come back to the threads again just fine on the second attempts, though.

Just got this when I clicked the graphic to go to the home page. I was at the forum reply confirmation page (return to forum/add to watch list, etc.) when I clicked the logo:

Database error: cannot use database gardening
MySQL Error: 2014 (Commands out of sync; You can't run this command now)
Session halted.

same thing -
Liz

Same here, numerous times in different forums. Debby

Me too. Glad it isn't just me.

Me too, the first attempt at every forum or thread or photo. I hit back and then re-click and it works.

E-mailing Mr. Dave this thread's URL.

Me too.

I just got the same thing when i tried to come on. I had to do a google search for davesgarden in order to click the site to let me in.....
Can't type it for some reason...
SYR

I get this message about every other time I try to do something, whether it be post, hit the back button or open a thread. I thought it was just me for a long time, because when I first tried to get in, I couldn't get in no matter what I did. Then I got in finally and saw that people were posting, but when I tried to post I got the error message again.

It's happening to me as well. Just hitting refresh when I see the error message will get me the page I was trying to get to. I'm using IE 6.0 as my browser.

AnnMarie

Well, I've thoroughly checked the server out this morning and I cannot see what happened to cause this error. Everything looks fine this morning.

I restarted the database and the web server daemons, so maybe they just needed a little kick in the pants. We'll see if this comes up again today. Thanks for the reports all.

dave