debugdiag webengine.dll

[Guest]

Recently installed 2.0 framework. Running one site under 2.0 and every day
at about 7:00 p.m. I get one error in the event log, 1000 indicating w3wp.exe
faulting. After running debugdiag it indicates an error with "webengine.dll"
of which I can find absolutely nothing about on the internet. Any help would
be greatly appreciated.

Thank you,

In
w3wp__PID__2688__Date__03_03_2006__Time_06_55_42PM__765__Second_Chance_Exception_C0000005.dmp
the module \\?\c:\WINDOWS\microsoft.net\framework\v2.0.50727\webengine.dll
has caused an access violation exception (0xC0000005) when trying to read
from memory location 0x0061002e on thread 31

Entry point mscorwks!Thread::intermediateThreadProc
Create time 3/3/2006 6:55:42 PM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0






Function Arg 1 Arg 2 Arg 3 Source
61002e 018a2710 800703e3 00000000
webengine!CorThreadPoolCompletionCallback+35 000003e3 00000000
018a2eb0
mscorwks!ThreadpoolMgr::CompletionPortThreadStart+406 00000000
012cf604 00000000
mscorwks!Thread::intermediateThreadProc+49 0017e948 00000000
00000000
kernel32!BaseThreadStart+34 79ecafc5 0017e948 00000000

 

[Terry Burns]

My advice to to call Microsoft and pay for an incident call. This software
is new to market and as yet there is no large experience base to draw upon.
What I do know is that a fair few of people are reporting problems with 2.0
in production generally on the net, but that is to be expected this early on
in the lifecyle of the product. Once it comes of age, I think it will be a
great way to develop sites.

Bugless code simply doesent happen on something this big.

 

[Guest]

Hello stine,

I hesitate to offer something I found by googling but there is a kb article
written about an unhandled exception in w3wp.exe caused by webengine.dll
which results in a web application to be terminated:
http://support.microsoft.com/default.aspx?scid=kb;en-us;911816. The exception
occurs because of a policy change for how the .NET framework 2.0 is now
handling unhandled exceptions. It includes a workaround.

 

[Guest]

I did notice something that may have helped, I had front page extensions
installed. I decided to try for giggles uninstalling the FP extensions and
restarting IIS. So far I made it through the first night without a dump.
This would appear strange and I will update this if it is elimated after a
few days in the hopes of helping someone else discover the situation I did.

On a side note, Brian, Thank you for pointing out that KB article although I
did read it before hand. One note to point out is this "When this problem
occurs, no exception information that you must have to understanding the
issue is logged in the Application log. However, an event message that is
similar to the following may be logged in the System log".

Stine
It does log event ID 1000 in the application log and doesn't log anything to
the System log.

 

[Guest]

This issue is still not resolved and all leads have come to a dead end. The
only way to resolved the issues is to run the pool as "Local System".

Take a look at the following threads:

http://forums.asp.net/1203282/ShowPost.aspx