Re: Problem w/ASP and MS PWS

Mike,
I'm sure you're right about the omens. My dilemma has been going on for 
several weeks now. I have a little intranet web server (PWS on '98) set up 
for my engineering group and thought it would be nice if the guys could 
enter their weekly project work times through a simple browser form to an 
Access database that I already have. It's beginning to look like Access and 
ASP just aren't worth the trouble.
Regards,
Dave G.

At 10:41 AM 2/12/00 -0500, Mike Taylor wrote:
>All of your problems getting it to work might prove to be a good omen, in
>the end.  Our web site has been using ASP pretty heavily since around August
>of 1999.  Since October, we have experienced major problems with ASP pages
>locking up and requests not being processed.
>
>This seems to be an issue the source of which can not be identified by
>Microsoft or anyone else.
>
>The symptoms?  Your web server will suddenly stop serving/processing ASP
>pages.  Plain HTML pages will continue to work fine.  If you view
>performance monitor from IIS, the moment you notice the hang-up you will see
>a gradual increase in "requests queued" that builds and builds until finally
>your CPU utilization maxes out at 100%.
>
>Yes, we've made sure all our recordset connections get closed after
>processed.  Yes, we've tested each and every ASP page individually, and each
>runs and completes the task fine.  But something --for whatever reason--
>causes the server to stop processing ASP and there seems to be no solution.
>We've gotten suggestions such as "get more CPU's,"  "re-install your MDAC,"
>"get more memory," "cut off the head of a chicken and sprinkle the blood
>around your IT room" --you name it, and the "solution" has been suggested.
>We've tried it all (except the chicken thing), and nothing works.
>
>Beware.  ASP is *not* your answer and I assure you it will generate needless
>hours of headache.  This much I guarantee.
>
>Mike

HWG hwg-techniques mailing list archives, maintained by Webmasters @ IWA