ASP code that cause problem w/ IIS 6.0 isolation

In general, it is not IIS6 that is "freaking out" when running in native WP
isolation Mode -- it is the Application that is "freaking out" when running
in native WP isolation Mode.

The usual cause of applications "freaking out" on IIS6 is due to:
- State -- IIS6 proactively recycles its applications, and if ASP
applications do not manage their Session/state correctly to survive such a
recycle, the application will lose its state on the recycle and completely
freak out.
- Timeout -- IIS6 also proactively idle-timeouts applications, and if ASP
application expect a longer session timeout than this idle timeout, the
application can break.

In other words, IIS5 can keep the ASP application loaded in memory until it
ate up all system resources. IIS6 will step in and prevent that from
happening, but the side effect is that your applications have to gracefully
survive a recycle... something that never happened on IIS5.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Frank" <nospam.RemoveThis@nospam.org> wrote in message
news:eXnMjGggDHA.1648@TK2MSFTNGP09.phx.gbl...
Does anyone know of any specific code written in ASP will cause IIS 6
running in native WP isolation mode to freak out?

MS Engineer (in private news group) confirm that some ASP code will not run
in IIS6 WP isolation and I must switch to IIS5.0 isolation. However, they
weren't able to tell me exactly what will cause this problem.