sarmisen
asked on
NET framework 2.0 and IIS 6.0 problems: Faulting application w3wp.exe
Hello Experts:
I'm developing ASP.NET pages under IIS 6.0 om a Windows 2003 server. As long as I used the .NET framework provided with the server (1.4) everything worked fine. Recently I installed 2.0 Framework. Pages seem to work fine, but I got this persistent error in the application log
Faulting application w3wp.exe, version 6.0.3790.1830, stamp 42435be1, faulting module webengine.dll, version 2.0.50727.42, stamp 4333eca4, debug? 0, fault address 0x00002fec.
The Event id is 1000
The source is .NET runtime 2.0 error
I never got this error under 1.4, although web pages seem ok I am very concerned about it.
Any Ideas?
I'm developing ASP.NET pages under IIS 6.0 om a Windows 2003 server. As long as I used the .NET framework provided with the server (1.4) everything worked fine. Recently I installed 2.0 Framework. Pages seem to work fine, but I got this persistent error in the application log
Faulting application w3wp.exe, version 6.0.3790.1830, stamp 42435be1, faulting module webengine.dll, version 2.0.50727.42, stamp 4333eca4, debug? 0, fault address 0x00002fec.
The Event id is 1000
The source is .NET runtime 2.0 error
I never got this error under 1.4, although web pages seem ok I am very concerned about it.
Any Ideas?
ASKER
In one App, the Idle timeout is 120.
¿Is that the key?
¿Is that the key?
can you try change to this in Aspnet.config file that is located in the following folder:
%WINDIR%\Microsoft.NET\Fra
<configuration>
<runtime>
<legacyUnhandledExceptionP
</runtime>
</configuration>
take a backup of Aspnet.config and keep it so that you can revert back to the old one if the solution is not working
%WINDIR%\Microsoft.NET\Fra
<configuration>
<runtime>
<legacyUnhandledExceptionP
</runtime>
</configuration>
take a backup of Aspnet.config and keep it so that you can revert back to the old one if the solution is not working
ASKER
Dear Dnojcd:
Thanks for your answer, but that is not the response I was searching for. As I am concerned when you set that propery to "true" what you are doing is just ignore these errors. I'd rather fix'em than ignore'em.
Yesterday I contacted Microsoft, they are lookin at the problem to see what it is.
I'll keep you informed about their veredict at this post.
Cheers
Sergio.
Thanks for your answer, but that is not the response I was searching for. As I am concerned when you set that propery to "true" what you are doing is just ignore these errors. I'd rather fix'em than ignore'em.
Yesterday I contacted Microsoft, they are lookin at the problem to see what it is.
I'll keep you informed about their veredict at this post.
Cheers
Sergio.
:-) in the article MS itself is saying that this is by design. i dont think they are going to do anything abt this.if they want they could shave done that earlier when the issue came up .If they are willing to do anything for you its gr8 :-)
ASKER
They have already answered.
Literally they have told me its caused by "a known issue they have been detecting in 2.0 Framework" (sounds like a bug). They have given me some hints about what to do next (i.e. deleting temp files in the framwork). I'll let you know if this solves the problem.
Literally they have told me its caused by "a known issue they have been detecting in 2.0 Framework" (sounds like a bug). They have given me some hints about what to do next (i.e. deleting temp files in the framwork). I'll let you know if this solves the problem.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Is there any other error in the system longs related to this
Most probably the error may be due to unhandled exceptions in your code since earlier versions, the Microsoft .NET Framework 1.1 and in the Microsoft .NET Framework 1.0, unhandled exceptions on managed threads were ignored.
http://support.microsoft.com/default.aspx?scid=kb;en-us;911816