Oh boy.
An unhandled exception in a running ASP.NET 2.0 application will usually
terminate the W3WP.exe process, and leave you with a very cryptic EventLog
entry something like this:
EventType clr20r3, P1 w3wp.exe, P2 6.0.3790.1830, P3 42435be1, P4
app_web_ncsnb2-n, P5 0.0.0.0, P6 440a4082, P7 5, P8 1, P9
system.nullreferenceexception, P10 NIL.
There is a KB that covers this here
http://support.microsoft.com/?id=911816
It's not well-written IMHO but at least its a start. The main thing is to go
back and check your code so that you don't have any unhandled exceptions.
Make sure you do not have 1.1 and 2.0 apps running in the same Application
Pool.
Peter
With IIS 6, w3wp.exe abruptly terminates.
--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com
"rh" wrote:
hi,
we just migrated to x64 and .net 2.0 and getting a debugger popup with
the system.cannotunloadappdomainexception caused by w3wp.exe. it
happens intermittently, and doesn't seem like it's gonna lend itself to
easy troubleshooting. anyone's experiencing this? where should i start
digging?
thanks,
rh