This project is read-only.

The conflict with .net 1.1

Sep 14, 2007 at 7:47 AM
Edited Sep 14, 2007 at 8:56 AM
This Filter.Net use as .net 2.0. When I install it, one of my website was crash.
This website is Discuz!NT (http://nt.discuz.net/), use of .net 1.1
The IIS AppPool crash, in Windows event can see:

Source W3SVC
Type Warning
A process serving application pool "DefaultAppPool" terminated unexpectedly. The process id was "587". The process exit code was "0x800703e9".

Source .NET Runtime 2.0 Error Reporting
Type Error
Description EventType clr20r3, P1 w3wp.exe, P2 6.0.3790.1830, P3 42435be1, P4 appweb7437ep-9, P5 0.0.0.0, P6 433b1670, P7 9, P8 a, P9 system.exception, P10 NIL.


I have no idea about this. did Filter.Net Frameword has .net 1.1 one?
Sep 17, 2007 at 10:42 AM
Edited Feb 15, 2008 at 9:09 PM
keenx,

Filter.NET is built in .NET 2.0, and therefore it should only be applied on IIS when running with ASP.NET 2.0. To make sure you do that you can install Filter.NET at server level (to the whole IIS, in which case ASP.NET should be v2.0 only). Or you can install Filter.NET at the site level, in which case you need to make sure that all virtual directories under that site are running ASP.NET 2.0.

See here:
http://filterdotnet.blogspot.com/2007/08/avoiding-clr-versioning-issues.html

Filter.NET, by itself, is a simple framework and does not perform actions besides starting the CLR 2.0 and should not be causing the crash itself. You may have a managed filter installed that is causing the corruption. You error code:
  • 0x800703e9
  • 0x800703e9 & 0x0000FFFF = 0x0309
  • 0x0309 = 1001
  • 1001 = "Recursion too deep; the stack overflowed"
indicates a stack overflow, which may be caused by the managed filter or by the ASP.NET code itself.