The dbFront web application is being shut down hard by DynaTrace. The application fails with a FastFail which means that there is no opportunity to log any error messages.
The eventlog appears to point to w3wp.exe terminating on a FastFail. Triggering a memory dump using WER and examining the content shows that the w3wp.exe process called into an unknown process and was terminated with a FastFail. The final portion of the faulting thread is below.
- clr!SystemNative::GenericFailFast+156
- clr!SystemNative::FailFast+8e
- 0x263a68d2 <= Unknown
- 0x263a04a9 <= Unknown
- clr!CallDescrWorkerInternal+34
- clr!CallDescrWorkerWithHandler+6b
To create a memory dump, the simplest option is to load the following Reg file.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\w3wp.exe]
"DumpFolder"=hex(2):63,00,3a,00,5c,00,64,00,75,00,6d,00,70,00,73,00,00,00
"DumpCount"=dword:00000002
"DumpType"=dword:00000002
This will make a total of 2 full user dumps (not mini-dumps but full dumps) and write the dumps to C:\dumps. The memory dumps can be about 250 meg in size but they compress very well using ZIP.
Source: Steps to catch a simple crash dump of a crashing-process, for more detailed instructions.
You can then examine the dump files using DebugDiag. (http://debugdiag.com/)
The best place to examine the dump file is directly on the faulting server using DebugDiag. This is because all of the correct symbol files will be present. Otherwise you can spend extra time hunting for dependencies.
