I have a re-occuring problem with my website. To set the stage, I've been writing ASP for many years, I used to run this website in an earlier form on my own Windows /IIS6 Server and have now moved to a commercial ISP.
Everyday I randomly get a System Resources Exceeded error. The website runs fine all day, then starts falling over from about 4pm onwards until it gets rebooted at some point early evening. I've have been onto the ISP and they say "check your code"!!!
There are 5 DNSless connections (using JET) to my Access database that are opened at the very beginning of the page build in an INC file, and are closed at the very end of the page build in another INC. In between, depending on what the page is doing there can be upto 30 other RecordSets created during the build, but I am metriculous about ensureing each open has a close and a nothing associated with it. this also happens when I use a DSN connection.
When I had my own IIS Server I never had this problem, even though that version of the code was more resource hungry than this one, and was very multi user, hosting about 10-20 concurrent users at the same time. I get one or two visitors now and it all falls over.
The ISP say it's my code, but I don't beleive them!
Is there any hidden ASP options I can use to up the connection limit? I always use Response.Buffer = True and Response.Expires = -1 to ensure the latest data is delivered.
I'm supposed to be starting out as a commercial web designer, and I emailed our local business community earlier today to tell them of my great achievement ... and it fell over! How embarassing!
Any information I can use against the ISP who I'm convinced are crippling the server would be really useful ... as would any hidden ASP commands to force up the connection pool.
thanks
STEFFI