Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

w3wp.exe requested the Runtime to terminate it in an unusual way

406 views
Skip to first unread message

LenaMsdn08

unread,
Jul 31, 2009, 5:38:02 PM7/31/09
to
We have a strange problem on our webserver, that has occurred randomly a
couple of times a day this week. The asp.net 2.0 websites stop responding. If
I look in task manager, the w3wp.exe worker process for the asp.net 2.0
application pool has allocated a large amount of memory, about 800MB – 1GB.
If I kill the worker process, the websites start responding again.

I'm trying to find a way to troubleshoot this problem.

There is one error in the eventlog that seems to show up around the time
when the websites stop responding:

Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 7/31/2009
Time: 1:52:40 PM
User: N/A
Computer: JUNO

Description:
Application popup: Microsoft Visual C++ Runtime Library : Runtime Error!

Program: c:\windows\system32\inetsrv\w3wp.exe
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

The server is Windows 2003 Web Edition SP2, running IIS 6 and ASP.Net, both
1.1 and 2.0

Any help troubleshooting this problem would be very appreciated!
Lena

Steven Cheng

unread,
Aug 3, 2009, 4:23:54 AM8/3/09
to
Hi Lena,

From your desciprtion, you're encoutering some high memory
consumption(cause app stop responding) issue in your ASP.NET web
application deployed in IIS, correct?

According to the eventlog entry and your symptom description, the problem
is related to high memory consumption. Since IIS can share app pool for
multiple application, you can first isolate your web application to use a
dedicated app pool so as to eliminate impact from other applications(share
the same pool).

For the application itself, generally we can perform code review on the web
application and try define some potential problem points(according to what
kind of components we've used) such as COM interop code or database access
code ....

If the problem cannot be easily found via high level review, sometimes some
live debugging or even dump analysis will help to identify the error point
and get more detailed information about the exception. Here are some good
debugging reference from Tess's blog:

#Outstanding Blog for Learning how to Debug ASP.NET App Issues (Memory
Leaks, Crashes, Deadlocks, etc)
http://weblogs.asp.net/scottgu/archive/2006/02/02/437231.aspx

#.NET Debugging Demos - Information and setup instructions
http://blogs.msdn.com/tess/pages/net-debugging-demos-information-and-setup-i
nstructions.aspx

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msd...@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.
--------------------
>From: =?Utf-8?B?TGVuYU1zZG4wOA==?= <LenaM...@newsgroup.nospam>
>Subject: w3wp.exe requested the Runtime to terminate it in an unusual way
>Date: Fri, 31 Jul 2009 14:38:02 -0700

>
>We have a strange problem on our webserver, that has occurred randomly a
>couple of times a day this week. The asp.net 2.0 websites stop responding.
If
>I look in task manager, the w3wp.exe worker process for the asp.net 2.0
>application pool has allocated a large amount of memory, about 800MB

�?1GB.

0 new messages