Rev - thanks for your efforts to keep us up and running smoothly!

Rev..

and I thoughtI had no life!!!

Well... I have a life. Just that, I have motivation to keep vinocellar.com a part of it. :-)

REMINDER AGAIN: VINOCELLAR.COM WILL BE UNAVAILABLE for a little while tonight.

Would it be trite on Hallow'een to say, "That's scarey!".

revlis, i hope you can make all this hard work pay off one of these days. surely you aren't just doing this out of some great affection for wine & winos. as you may have noticed, however, the winos, myself included, do appreciate your efforts.

Rev...

How did it go last night?
Were you able to fix it?

Hey Rev, everything seems to have been working extremely well lately. You may want to remove that banner text warning of hardware difficulties

What he said!

that's just a reminder on how hard he works to bring us happiness

I'll just revive this thread...

I received this error just now:

"Fatal error: Maximum execution time of 30 seconds exceeded in c:\inetpub\wwwroot\forums\mysql.inc.php on line 107"

I was viewing a post for a specific user and hit the index button to return to the list of all of the user's post. It sat there for, duh, 30 seconds and finally timed out.

I'm getting a bit of latency on the site and was wondering if it was from my end or not. I click on a link and it either goes to an error page or it just sits there. This has been going on since last Saturday or so.

Any ideas? TIA.

I'm posing from just outside of Philly and everything's fine.
Could be a network slowdown.

Just got it again doing the exact same thing. Based on the error message it appears to be a SQL timeout. I hit this all the time working with SQL Server trying to update a row twice inside the same BeginTrans/CommitTrans transaction. Looks like a bug to me.

what kind ofposing are you doing, budman?

I'm cruising along fine

Gus... ya got me!!!!!

what did wiml just say? was that of the english language

It could be something else Tony. After all, the InfoPop forum we're on apparently is using MySql for its' queries. I'm not that familar with MySql. Could be an ODBC timeout issue.

Clear things up?