aspnet_wp.exe (PID: xxxx) stopped unexpectedly.

[Matt Sollars]

Hi all.

I'm having a nasty problem. A client's website was originally written with
classic ASP. They requested a new portion of the site that was deemed a
perfect candidate for ASP.NET. So, .NET was installed on their web server
and one of the subdirectories in the web site was converted to a virtual
application to support the new pages that would be added. The rest of the
site was left untouched. New aspx files were added to this subdirectory and
compiled code was put in it's \bin directory. All worked well in testing,
even on their server.

Then, one day, a report was made that a user could not access one of the new
pages in the new virtual. A server error was being reported to the user. The
client's IT dept rebooted the web server to "fix" the problem and all worked
well again until the next night. Again, the same problem. Only this time,
the server was fine by the time I was told to investigate and no reboot was
performed.

I looked through the event logs for application errors and have found 3
different errors involving .NET.
1.) aspnet_wp.exe (PID: xxxx) stopped unexpectedly.
2.) aspnet_wp.exe (PID: 3148) was recycled because it was suspected to
be in a deadlocked state. It did not send any responses for pending requests
in the last 180 seconds. This timeout may be adjusted using the
<processModel responseDeadlockInterval> setting in machine.config.
3.) The system has called a custom component and that component has
failed and generated an exception. This indicates a problem with the custom
component. Notify the developer of this component that a failure has
occurred and provide them with the information below.
Component Prog ID: SC.Pool 9 4
Method Name: IDispenserDriver:estroyResource
Process Name: aspnet_wp.exe
The serious nature of this error has caused the process to terminate.
Exception: C0000005
Address: 0x272116E4
Call Stack:
MSDART!MPInitializeCriticalSection + 0x11C
oledb32!CSCDispMan::GetDispenserManager(unsigned short *) + 0x3D
COMSVCS!ATL::CComPolyObject<class CStdTrustable>::QueryInterface(struct
_GUID const &,void * *) + 0x55

When I cross-reference the IIS logs with the timestamps reported in the
event logs for these errors, there doesn't appear to be any pattern. In 15
instances, only one of them seems to involve one of the new ASPX pages. All
other cases are in various directories, involving classic ASP pages. I don't
get it. Whenever the 3rd error occurs, it is always followed immediately by
the 1st error and whenever the 1st error is reported, no ASP.NET pages can
be displayed.

I cannot for the life of me get this to happen at will. They happen at
varying times of the day. I've even removed the new .NET pages and virtual
for the subdirectory, but it still happens.

Is there a way to prevent the process from stopping when things go wrong? Is
there a setting I'm missing? Why does it seem that these errors are
happening with pages that don't even use ASP.NET, yet the aspnet_wp.exe is
always the process generating the errors?

Please, help.

--
Matt Sollars
(e-mail address removed)
-------------------
The Hypersite Network
2002 N. Salisbury Blvd.
Suite C
Salisbury, Maryland 21801
T: 410.749.2000
F: 410.219.3400
http://www.hypersite.net

 

[Natty Gur]

Hi,

If you are using any VB6 dlls from your pages check that Retained in
memory and Unattended execution options are checked. I got it once, this
behavior documented in MS.

Natty Gur, CTO
Dao2Com Ltd.
34th Elkalay st. Raanana
Israel , 43000
Phone Numbers:
Office: +972-(0)9-7740261
Fax: +972-(0)9-7740261
Mobile: +972-(0)58-888377

 

[Yan-Hong Huang[MSFT]]

Hello Matt,

Natty is right. "ASP.NET Worker Process (Aspnet_wp.exe) Is Recycled Unexpectedly" error is documented in one Microsoft
KB article. Please refer to http://support.microsoft.com/?id=321792 for details.

Hope that helps.

Best regards,
Yanhong Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
!From: "Matt Sollars" <[email protected]>
!Subject: aspnet_wp.exe (PID: xxxx) stopped unexpectedly.
!Date: Fri, 1 Aug 2003 17:08:39 -0400
!Lines: 73
!Organization: Hypersite
!X-Priority: 3
!X-MSMail-Priority: Normal
!X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
!X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
!Message-ID: <[email protected]>
!Newsgroups: microsoft.public.dotnet.framework.aspnet
!NNTP-Posting-Host: 207.204.29.22
!Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
!Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet:164256
!X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
!
!Hi all.
!
!I'm having a nasty problem. A client's website was originally written with
!classic ASP. They requested a new portion of the site that was deemed a
!perfect candidate for ASP.NET. So, .NET was installed on their web server
!and one of the subdirectories in the web site was converted to a virtual
!application to support the new pages that would be added. The rest of the
!site was left untouched. New aspx files were added to this subdirectory and
!compiled code was put in it's \bin directory. All worked well in testing,
!even on their server.
!
!Then, one day, a report was made that a user could not access one of the new
!pages in the new virtual. A server error was being reported to the user. The
!client's IT dept rebooted the web server to "fix" the problem and all worked
!well again until the next night. Again, the same problem. Only this time,
!the server was fine by the time I was told to investigate and no reboot was
!performed.
!
!I looked through the event logs for application errors and have found 3
!different errors involving .NET.
! 1.) aspnet_wp.exe (PID: xxxx) stopped unexpectedly.
! 2.) aspnet_wp.exe (PID: 3148) was recycled because it was suspected to
!be in a deadlocked state. It did not send any responses for pending requests
!in the last 180 seconds. This timeout may be adjusted using the
!<processModel responseDeadlockInterval> setting in machine.config.
! 3.) The system has called a custom component and that component has
!failed and generated an exception. This indicates a problem with the custom
!component. Notify the developer of this component that a failure has
!occurred and provide them with the information below.
!Component Prog ID: SC.Pool 9 4
!Method Name: IDispenserDriver:estroyResource
!Process Name: aspnet_wp.exe
!The serious nature of this error has caused the process to terminate.
!Exception: C0000005
!Address: 0x272116E4
!Call Stack:
!MSDART!MPInitializeCriticalSection + 0x11C
!oledb32!CSCDispMan::GetDispenserManager(unsigned short *) + 0x3D
!COMSVCS!ATL::CComPolyObject<class CStdTrustable>::QueryInterface(struct
!_GUID const &,void * *) + 0x55
!
!When I cross-reference the IIS logs with the timestamps reported in the
!event logs for these errors, there doesn't appear to be any pattern. In 15
!instances, only one of them seems to involve one of the new ASPX pages. All
!other cases are in various directories, involving classic ASP pages. I don't
!get it. Whenever the 3rd error occurs, it is always followed immediately by
!the 1st error and whenever the 1st error is reported, no ASP.NET pages can
!be displayed.
!
!I cannot for the life of me get this to happen at will. They happen at
!varying times of the day. I've even removed the new .NET pages and virtual
!for the subdirectory, but it still happens.
!
!Is there a way to prevent the process from stopping when things go wrong? Is
!there a setting I'm missing? Why does it seem that these errors are
!happening with pages that don't even use ASP.NET, yet the aspnet_wp.exe is
!always the process generating the errors?
!
!Please, help.
!
!--
!Matt Sollars
[email protected]
! -------------------
!The Hypersite Network
!2002 N. Salisbury Blvd.
!Suite C
!Salisbury, Maryland 21801
!T: 410.749.2000
!F: 410.219.3400
!http://www.hypersite.net
!
!
!