Well it wasn’t just a hardware upgrade the OS registry was resetting itself to a fresh state.
I am unsure what is causing this error other than it looks like it is keeping a file lock on it forever, the ODBC engine is then hanging making this happen.
I am checking for what may be causing it in logs.
I have been checking your site many times each day and not seen it, I am doing a manual check and may not hit it sometimes for 30 minutes, but not seeing this continually by any means.
We have a log going of the issue and are mailing those responsible when we see it occur.
we have monitoring every minute we just can’t do it for every site on every server, I will stick with manually checking it for now as anytime I’ve signed up for something such as this I’ve been stuck with it forever
(I mean by spam, ads, etc, no offense to your suggestion I am not saying it is bad)
I still get alerts that wake me up for a server I logged into one time for a client in my freelancing days in 2003, really annoying!
It monitors the server and CF itself, but sometimes the ODBC issues can slip past as it doesn’t freeze up all CF or anything.
I have assigned the level1(low level) techs and customer support agents to check it at least every 15 min manually and tell us if any issue. We are checking the logs and working to get it resolved as well but just so you know it has NOTHING to do with hardware change, it is purely a software issue and would be happening on the old CF hardware as well.
The new hardware is a huge upgrade overall as well :music:
I have just done a Access DB repair on one that DB that was taking an insane amount of time to process and keeping an eye on it now.
“Warning”,“jrpp-1435”,“12/03/08”,“15:03:06”,“Thread: jrpp-1435, processing template: E:\hshome\xxxxxxx\xxxxxx.com.xxxx\xxxxxx_principal.cfm, completed in 2,449 seconds, exceeding the 30 second warning limit”