• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 819
  • Last Modified:

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?
0
sarmisen
Asked:
sarmisen
  • 3
  • 3
1 Solution
 
dnojcdCommented:
What is the Idle timeout setting under  Performance in the properties of the application pool ?

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
0
 
sarmisenAuthor Commented:
In one App, the Idle timeout is 120.

¿Is that the key?
0
 
dnojcdCommented:
can you try change to this in Aspnet.config file that is located in the following folder:
%WINDIR%\Microsoft.NET\Framework\v2.0.50727

<configuration>
    <runtime>
        <legacyUnhandledExceptionPolicy enabled="true" />
    </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
0
Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

 
sarmisenAuthor Commented:
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.
0
 
dnojcdCommented:
:-) 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 :-)
0
 
sarmisenAuthor Commented:
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.
0
 
CetusMODCommented:
PAQed with points refunded (500)

CetusMOD
Community Support Moderator
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now