Ok...
Hopefully I won't type too much in trying to explain this, but I'm trying to find out why my site (which worked last year just fine) has recurring issues this year (with minimal changes to the code) that are awful both to business and my blood pressure...
I get the errors mentioned in the subject of this thread almost daily at this point. I'm on a shared server but the tech support guys claim to have lumped us into a "dedicated priority and isolated application pool" which would in theory alleviate other sites from causing us to go down as a result of their shoddy code.
I have checked all of my pages (quite a few) through thousands of lines of code altogether to make sure that I am closing connections and destroying objects as necessary...and I am. I have made sure that I'm not storing recordsets or connections in session variables...and I'm not. I have gone through all the reasons I can think of as to why a site would bomb so frequently and I cannot find an issue with my code. The best scenario was a few days ago when the site went down (just stopped loading the asp files...no errors...just spinning and spinning). I contacted tech support, they restarted IIS (their solve-all fix)...it was at an off peak time and only a couple people hit the site (two of which were tech support and myself to make sure the site was back up) and it went down again. Within an hour.
Late last year they switched one of my connection strings (oh yeah, I'm using MySQL) to OleDB instead of ODBC. Could this be the culprit? Should I change it back to ODBC? Also, I apologize for writing a book to explain this but I thought I'd get it all out there as I won't be able to answer any questions immediately while at work tomorrow. Thanks in advance for any responses I get.
Hopefully I won't type too much in trying to explain this, but I'm trying to find out why my site (which worked last year just fine) has recurring issues this year (with minimal changes to the code) that are awful both to business and my blood pressure...
I get the errors mentioned in the subject of this thread almost daily at this point. I'm on a shared server but the tech support guys claim to have lumped us into a "dedicated priority and isolated application pool" which would in theory alleviate other sites from causing us to go down as a result of their shoddy code.
I have checked all of my pages (quite a few) through thousands of lines of code altogether to make sure that I am closing connections and destroying objects as necessary...and I am. I have made sure that I'm not storing recordsets or connections in session variables...and I'm not. I have gone through all the reasons I can think of as to why a site would bomb so frequently and I cannot find an issue with my code. The best scenario was a few days ago when the site went down (just stopped loading the asp files...no errors...just spinning and spinning). I contacted tech support, they restarted IIS (their solve-all fix)...it was at an off peak time and only a couple people hit the site (two of which were tech support and myself to make sure the site was back up) and it went down again. Within an hour.
Late last year they switched one of my connection strings (oh yeah, I'm using MySQL) to OleDB instead of ODBC. Could this be the culprit? Should I change it back to ODBC? Also, I apologize for writing a book to explain this but I thought I'd get it all out there as I won't be able to answer any questions immediately while at work tomorrow. Thanks in advance for any responses I get.
