D
Dave
Hi All,
I was wondering if anyone had any tips or configurations in IIS 5.5 running
on Win2K Server (SP4) running FW1.1
to keep a failed ASP.Net application from taking down all of the others.
It, unfortunately, does not do this by default. For some reason, an app we
have that occassionally locks up (we have been trying to debug it for a week
with no luck) for no apparent reason. While we debug it over the next few
weeks, it would be nice if there was a way to completely isolate it from the
other ASP.Net apps running (Classic ASP apps run just fine and do not crash
when the ASP.Net applications crash) on the server.
Setting the parameters inside IIS: Application Protection to "High
(Isolated)" has no effect on this problem.
TIA,
Dave
I was wondering if anyone had any tips or configurations in IIS 5.5 running
on Win2K Server (SP4) running FW1.1
to keep a failed ASP.Net application from taking down all of the others.
It, unfortunately, does not do this by default. For some reason, an app we
have that occassionally locks up (we have been trying to debug it for a week
with no luck) for no apparent reason. While we debug it over the next few
weeks, it would be nice if there was a way to completely isolate it from the
other ASP.Net apps running (Classic ASP apps run just fine and do not crash
when the ASP.Net applications crash) on the server.
Setting the parameters inside IIS: Application Protection to "High
(Isolated)" has no effect on this problem.
TIA,
Dave