http://blogs.msdn.com/david.wang/archive/2005/08/29/HOWTO_Understand_a...Diagnos
Worker Process usually crash due to bad user code executed by it.
Since people usually run their own code that is not copied from anyone
else, you will rarely find anything concrete by looking at someone
else's problem. Best solution is to directly debug your own crash to
figure out the reason. You can only learn to debug/triage issues by
looking at someone else's problem -- which you reapply to your problem
to determine the cause.
Any debugger can attach by Process ID of the w3wp.exe. Once you make
sure that IIS6 is not automatically recycling Application Pool (which
will change the Process ID), you can do whatever you want to attach
the debugger onto the process and wait for the crash.
w3wp.exe are restarted automatically following a crash -- unless the
crash happens again... and again, in rapid succession to force IIS to
stop retrying.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
On Mar 1, 7:55 am, sri_... RemoveThis @mailcity.com wrote:
> Hello,
> I looked at the groups to figure out the reason behind the
> worker process crashing but couldnt find anything concrete. I am
> running IIS 7.0 on Vista. It seems to crash during the debug process
> when left for a while(might have to do with the timeout ??) and
> sometimes when an unhandled exception happens. Below are the couple of
> warnings I could find in the event log:
>
> Warning -- 1
> ---------
> A process serving application pool 'Classic .NET AppPool' suffered a
> fatal communication error with the Windows Process Activation Service.
> The process id was '4172'. The data field contains the error number.
> --------------
>
> I found the application pool info is below:
>
> Framework : 2.0.50727
> Managed pipeline mode:classic
> Start application pool immediately -- checked
>
> Warning -- 2
> ----------
>
> Event code: 3005
> Event message: An unhandled exception has occurred.
> Event time: 3/1/2007 10:36:18 AM
> Event time (UTC): 3/1/2007 3:36:18 PM
> Event ID: ad37407d878746ae8cd38f3528aba8f8
> Event sequence: 105
> Event occurrence: 4
> Event detail code: 0
>
> Application information:
> Application domain: /LM/W3SVC/1/ROOT-1-128172335832141452
> Trust level: Full
> Application Virtual Path: /
> Application Path: C:\inetpub\wwwroot\AMS\
> Machine name: PHI1-SRINIT
>
> Process information:
> Process ID: 4172
> Process name: w3wp.exe
> Account name: NT AUTHORITY\NETWORK SERVICE
>
> Exception information:
> Exception type: NullReferenceException
> Exception message: Object reference not set to an instance of an
> object.
>
> --------------------
>
> And, in case it crashes, is there a way to start the w3wp.exe process
> manually.
>
> Thanks for your help,
> Sam. 
FAQ
Profile
Private Messages
Log in
