aspnet_wp.exe crashing

[Tom]

I am having the following show up in my application event log:

=============== =============== =======
Source: .NET Runtime
Event ID: 0
Description:
The description for Event ID ( 0 ) in Source ( .NET Runtime ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. The following
information is part of the event: .NET Runtime version 1.1.4322.2032-
aspnet_wp.exe - Common Language Runtime Debugging Services: Application has
generated an exception that could not be handled.

Process id=0xecc (3788), Thread id=0xe20 (3616).

Click OK to terminate the application.
Click CANCEL to debug the application..
=============== =============== =========

immediately after that, the next entry in the application log is
Source ASP NET 1.1.4322.0
Event ID: 1000

Description:
aspnet_wp.exe (PID: 3788) stopped unexpectedly.

=============== =============== ===========

If I restart IIS, it works for a while, maybe a day, then it crashes again.
Any clues ?

Thanks,
Tom

[Scott Allen]

Hi Tom:
Unfortunately, there is no easy way to know why the process stopped
unexpectedly.

You'll have to do some digging around. Fortunately there are tools
that can take a snapshot of the process before it terminates and from
there you can look at threads and call stacks to see what it was doing
at the moment it decided it needed to terminate.

See:
Production Debugging for .NET Framework Applications
http://msdn.microsoft.com/library/de...html/DBGrm.asp

Particularity chapter 4 will guide you on how to debug unexpected
process terminations.

HTH,

--
Scott
http://www.OdeToCode.com/blogs/scott/
On Fri, 29 Apr 2005 09:32:09 -0700, Tom
<To*@discussion s.microsoft.com > wrote:

I am having the following show up in my application event log:

============== =============== ========
Source: .NET Runtime
Event ID: 0
Description:
The description for Event ID ( 0 ) in Source ( .NET Runtime ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. The following
information is part of the event: .NET Runtime version 1.1.4322.2032-
aspnet_wp.ex e - Common Language Runtime Debugging Services: Application has
generated an exception that could not be handled.

Process id=0xecc (3788), Thread id=0xe20 (3616).

Click OK to terminate the application.
Click CANCEL to debug the application..
============== =============== ==========

immediately after that, the next entry in the application log is
Source ASP NET 1.1.4322.0
Event ID: 1000

Description:
aspnet_wp.ex e (PID: 3788) stopped unexpectedly.

============== =============== ============

If I restart IIS, it works for a while, maybe a day, then it crashes again.
Any clues ?

Thanks,
Tom

[Robbe Morris [C# MVP]]

You aren't using try/catch/finally everywhere you should. Trap
your errors...

--
2005 Microsoft MVP C#
Robbe Morris
http://www.robbemorris.com
http://www.masterado.net/home/listings.aspx

"Tom" <To*@discussion s.microsoft.com > wrote in message
news:86******** *************** ***********@mic rosoft.com...

I am having the following show up in my application event log:

=============== =============== =======
Source: .NET Runtime
Event ID: 0
Description:
The description for Event ID ( 0 ) in Source ( .NET Runtime ) cannot be
found. The local computer may not have the necessary registry information
or
message DLL files to display messages from a remote computer. The
following
information is part of the event: .NET Runtime version 1.1.4322.2032-
aspnet_wp.exe - Common Language Runtime Debugging Services: Application
has
generated an exception that could not be handled.

Process id=0xecc (3788), Thread id=0xe20 (3616).

Click OK to terminate the application.
Click CANCEL to debug the application..
=============== =============== =========

immediately after that, the next entry in the application log is
Source ASP NET 1.1.4322.0
Event ID: 1000

Description:
aspnet_wp.exe (PID: 3788) stopped unexpectedly.

=============== =============== ===========

If I restart IIS, it works for a while, maybe a day, then it crashes
again.
Any clues ?

Thanks,
Tom

[Patrick Olurotimi Ige]

TOm as Robbe adviced try sing TRY/CATCH
It should help where to start from

*** Sent via Developersdex http://www.developersdex.com ***

[Scott Allen]

It doesn't sound like the problem is a managed exception - generally
something went terribly wrong in native code, or a memory threshold
was exceeded - something along those lines...

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Fri, 29 Apr 2005 21:19:54 -0400, "Robbe Morris [C# MVP]"
<in**@turnkeyto ols.com> wrote:

You aren't using try/catch/finally everywhere you should. Trap
your errors...

[Tom]

For now I have done the following:
1. Locate machine.config (try
C:\WINNT\Micros oft.NET\Framewo Â*rk\<VERSION FOLDER>\CONFIG) .
2. Open machine.config in Notepad or other text editor.
3. Search for this string: "<processMo del"
4. In the processModel element, change userName="machi ne" to
userName="SYSTE M"
This seems to be working so far....not sure why.
"Scott Allen" wrote:

It doesn't sound like the problem is a managed exception - generally
something went terribly wrong in native code, or a memory threshold
was exceeded - something along those lines...

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Fri, 29 Apr 2005 21:19:54 -0400, "Robbe Morris [C# MVP]"
<in**@turnkeyto ols.com> wrote:

You aren't using try/catch/finally everywhere you should. Trap
your errors...