Ok folks, it seems that we were indeed using excessive amounts of CPU, due to the size and condition of our database. I just optimized our database, which should help the problem. If it doesn't, I'll have to take more drastic measures, but those measures will have to be performed during the middle of the night or something, since I'll have to take the site down to perform them. Let's hope that's not necessary.
In the interim, I'm heading back out to get back to laying flooring. If anyone gets those same error messages, please update this thread, and please include the time you got the message. No need for a screen print showing the message, just a quick-n-dirty post with time recieved.
(By the way, I only need a general idea of when the problem occurs, so if someone already posted that they got the error msg, and you got it a few minutes later, no need for the duplicate posts. Thanks...)
Thanks for your patience...and again, sorry for the inconvenience.
- Marty -
P.S. For all you non-computer folks...We were trying to cram ten pounds of potatos into a five pound sack. The extra effort to cram them in was using too much computer power on our host, so they throttled us back to keep us from making their computer glow red-hot.
I've increased the size of the sack, and tossed out a few potatos.