Maximum Recovery Limit

[Boomerang]

Hi,

Our site works on IIS with asp-pages.

This morning there was a Server Application Error:

"The server has reached the maximum recovery limit for the application during the processing of your request. Please contact the server administrator for asistance"

I viewed the log-files bud couldn't discover the problem.

Has anyone an idea what can caused this problem, or where i should look to find it??

Erik

 

[bra1niac]

I know *sort* of what you are talking about. I searched hi&lo and couldn't locate where I last saw the little blurb concerning your problem.

If you want to know the best place to look, you would need the msdn library either on disk or surf it at microsoft.com.

Sorry I don't have more... "Absorb what is useful, discard what is not. Add what is uniquely your own." - Bruce Lee - The Tao of Jeet Kune Do

 

[MikeGarrison]

I've also been getting this message.
It seems to be, for us, caused by failed ISAPI calls
to a Powerbuilder application.

I swear I found something on

http://www.microsoft.com

a few months ago about this that even had directions on increasing the limit. Which I did.. but I didn't increase it enough and we still haven't found the problems.... dang, wish i'd kept that documentation.

Our IIS logical application (website) runs "out process". Each time the web application error occurs, IIS will reload the application until it hits this limit. When that happens the users get the message you are seeing. The first thing we try is to click the "Unload" button on the iis web app page... sometimes that works... sometimes it just hangs and we have to reload.

so, the search continues... but you are not alone.

Mike Garrison

 

[Monsta]

We are experiencing this problem too.

Part of the answer can be found on the following two links:

http://support.microsoft.com/suppor...verLimit&rnk=1&src=DHCS_MSPSS_gn_SRCH&SPR=IIS

http://support.microsoft.com/suppor...verLimit&rnk=2&src=DHCS_MSPSS_gn_SRCH&SPR=IIS

This is all I have managed to find out so far. It's a property in the metabase called AppOopRecoverLimit which can be set much higher than the help suggests. It can be set using ADSUtil.vbs.

Good luck!