Asp_0147

Tuning IIS - ASP errors

[FlashDan]

Got some great info from a thread that was closed, but have some more questions pertaining to ASP_0147 and other ASP errors.

I have ASP_0147 errors (and others) showing up sporadically on my website log. The parameters passed to these pages all show up and they normally execute fine so my question is:

1. Is ASP_0147 caused by strictly by lack of resources, and if so, making sure all objects are closed truly the remedy,

or,

2. Is is that we are running some third party, process intensive apps on the server that gobble up resources.

P.S. I have been told that IIS kills all objects once the (ASP) page
is done executing, True or False?

Dan

[wardbekker]

Hi FlashDan,

Explicit closing of all objects & connections is always a good practice. So, make if this is done in all of your asp pages, and monitor if the ASP_0147 error are still occuring in the same frequency as before the change.

[FlashDan]

Thanks for the input. Closing objects always the prefered option however, when writing code on the Fly doesn't always happen. Can this realy cause these ASP errors such as 0147 or others?

I had been informed that IIS will kill htese objects once the page is doen but if there is a script error (page execution doesn't end properly) I can see how they might still be there.

Any input into this would be greatly appreciated.

Dan

[wardbekker]

IIS should kill those object, in theory ;-)

[aspdaddy]

>when writing code on the Fly doesn't always happen.

You should test using on error resume next, then script will always finish running, so you wont have this problem.

I would not rely on IIS, if you allocate some memory you should give it back when finished.

[FlashDan]

Thanks for the input folks. You all affirmed what I've been thinking hope this has been helpful to others.

Dan