Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a classic ASP application that's under significantly more load than usual.

We are from time to time been getting "out of memory" and "out of string space" in the httperr. We do not usually see these errors.

For the moment we cannot change the application.

Is there anything we can do to the IIS config which will help to reduce or stop these errors occurring ?

The application pool is set to default values currently.

share|improve this question
up vote 1 down vote accepted

Does not changing the application mean not looking into why the load has increased or what pages are leading to this error?

Based on what you've stated in your question, that's the place I'd start with.

Otherwise, you've said application pool - I only support Classic ASP code, but can you increase the app pool recycling?

share|improve this answer
See also… which I'd say backs-up my suggestion of looking into what pages are causing the issues, now that the application is under load. If there's a programming issue, you'll keep running into it until it's fixed. – James Skemp Jun 28 '11 at 22:39
Thanks for your response. We do know both the page that is causing the problem and why the load has gone up (basically 5x as many users were asked to use the application temporarily). However internal controls on change mean that altering the application is not feasible within 48 hours. – glaucon Jun 28 '11 at 22:45
Would you suggest just recycling every x minutes or get involved in setting memory limits ? – glaucon Jun 28 '11 at 22:47
Having now read the stackoverflow question you linked to - yes it is a string concatentaion which was never optimal but which was 'OK' in the context of the original user base - it seems it's now causing problems. – glaucon Jun 28 '11 at 22:48
Honestly, I'd either set up some performance checks or do it manually and see what CPU/memory is looking like. If you can bump up the memory you could start there, but the one time we had to do a quick fix we ended up having the app pool recycle much more frequently. If you're using defaults, IIRC that's a little over a day. So you could look at x hours, or if it's coming in at certain times, switch it to recycle during/after those periods of time. – James Skemp Jun 28 '11 at 23:02

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.