IIS Crash on Microsoft ASP page (.NET 2.0)

We are running Microsoft Small Business Server R2. We have many of these
servers installed and are only experiencing this issue on one. The problem
is that when going to the Remote Web Workplace we get a .NET unhandled
exception. I've run IIS Debug Diag and received the following dump and am
looking for some help.


Analysis Summary
Type Description Recommendation
Error In
w3wp__PID__7652__Date__06_19_2007__Time_11_40_10AM__80__Seco nd_Chance_Exception_E0434F4D.dmp
the assembly instruction at kernel32!RaiseException+53 in
C:\WINDOWS\system32\kernel32.dll from Microsoft Corporation has caused an
unknown exception (0xe0434f4d) on thread 14



This exception originated from mscorwks!RaiseTheExceptionInternalOnly+226.
Review the faulting call stack for thread 14 to determine root cause for the
exception.





Please follow up with vendor Microsoft Corporation for problem resolution
concerning the following file:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll.
Information DebugDiag determined that this dump file
(w3wp__PID__7652__Date__06_19_2007__Time_11_40_10AM__80__Sec ond_Chance_Exception_E0434F4D.dmp)
is a crash dump and did not perform any hang analysis. If you wish to enable
combined crash and hang analysis for crash dumps, edit the IISAnalysis.asp
script (located in the DebugDiag\Scripts folder) and set the
g_DoCombinedAnalysis constant to True.





Analysis Details
Table Of Contents
w3wp__PID__7652__Date__06_19_2007__Time_11_40_10AM__80__Seco nd_Chance_Exception_E0434F4D.dmp

Faulting Thread

Faulting Module Information




Report for
w3wp__PID__7652__Date__06_19_2007__Time_11_40_10AM__80__Seco nd_Chance_Exception_E0434F4D.dmp
Type of Analysis Performed Crash Analysis
Machine Name SERVER
Operating System Windows Server 2003 Service Pack 2
Number Of Processors 2
Process ID 7652
Process Image c:\WINDOWS\system32\inetsrv\w3wp.exe
System Up-Time 0 day(s) 09:20:12
Process Up-Time 0 day(s) 00:00:45


Thread 14 - System ID 7176
Entry point mscorwks!ThreadpoolMgr::intermediateThreadProc
Create time 6/19/2007 11:39:26 AM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.15






Function Arg 1 Arg 2 Arg 3 Source
kernel32!RaiseException+53 e0434f4d 00000001 00000001
mscorwks!RaiseTheExceptionInternalOnly+226 01f09290 00000000
00000000
mscorwks!RaiseTheException+4c 01f09290 00000000 01cffbf8
mscorwks!RaiseTheException+be 00000000 0ec309e0 9695272b
mscorwks!RealCOMPlusThrow+37 01f09290 00000000 7a0e0701
mscorwks!RealCOMPlusThrow+a 01f09290 955af301 7a36a7d0
mscorwks!Thread::RaiseCrossContextException+63 00000000 01cffca8
01cffd18
mscorwks!Thread::DoADCallBack+26c 00000002 79f3a0a1 01cffe18
mscorwks!Thread::UserResumeThread+e1 01cffe18 01cffdc4 79f93fe6

mscorwks!Thread::DoADCallBack+355 01cffe18 955af109 0ec309e0
mscorwks!Thread::DoADCallBack+541 01cffe18 00000002 00000000
mscorwks!Thread::DoADCallBack+575 00000002 7a07bdfe 01cffe6c
mscorwks!ManagedThreadBase::ThreadPool+13 00000002 7a07bdfe
01cffe6c
mscorwks!BindIoCompletionCallbackStubEx+8c 00000079 00000000
01eec464
mscorwks!BindIoCompletionCallbackStub+13 00000079 00000000
01eec464
mscorwks!ThreadpoolMgr::CompletionPortThreadStart+406 00000000
00000000 b6da3d08
mscorwks!ThreadpoolMgr::intermediateThreadProc+49 000cd9a8 00000000
00000000
kernel32!BaseThreadStart+34 79f710dd 000cd9a8 00000000




In
w3wp__PID__7652__Date__06_19_2007__Time_11_40_10AM__80__Seco nd_Chance_Exception_E0434F4D.dmp
the assembly instruction at kernel32!RaiseException+53 in
C:\WINDOWS\system32\kernel32.dll from Microsoft Corporation has caused an
unknown exception (0xe0434f4d) on thread 14



This exception originated from mscorwks!RaiseTheExceptionInternalOnly+226.
Module Information
Image Name: C:\WINDOWS\system32\kernel32.dll Symbol Type: PDB
Base address: 0x77e40000 Time Stamp: Wed Apr 18 10:25:36 2007
Checksum: 0x001083fc Comments:
COM DLL: False Company Name: Microsoft Corporation
ISAPIExtension: False File Description: Windows NT BASE API Client DLL
ISAPIFilter: False File Version: 5.2.3790.4062 (srv03_sp2_gdr.070417-0203)
Managed DLL: False Internal Name: kernel32
VB DLL: False Legal Copyright: © Microsoft Corporation. All rights
reserved.
Loaded Image Name: kernel32.dll Legal Trademarks:
Mapped Image Name: Original filename: kernel32
Module name: kernel32 Private Build:
Single Threaded: False Product Name: Microsoft® Windows® Operating System
Module Size: 1.01 MBytes Product Version: 5.2.3790.4062
Symbol File Name:
c:\symcache\kernel32.pdb\7FD4C98964054C24B2C472948D829DF52\k ernel32.pdb
Special Build: &








Script Summary
Script Name Status Error Code Error Source Error Description Source Line
IISAnalysis.asp Completed

Re: IIS Crash on Microsoft ASP page (.NET 2.0)

The exception happened in managed code - so we can't see what the problem
is. If you had a dump created, you can take a look using WinDBG.


Pat

"Rob" wrote in message
news:8314FEFB-D8A2-49E7-A589-2043AD6A2A28@microsoft.com...
> We are running Microsoft Small Business Server R2. We have many of these
> servers installed and are only experiencing this issue on one. The
> problem
> is that when going to the Remote Web Workplace we get a .NET unhandled
> exception. I've run IIS Debug Diag and received the following dump and am
> looking for some help.
>
>
> Analysis Summary
> Type Description Recommendation
> Error In
> w3wp__PID__7652__Date__06_19_2007__Time_11_40_10AM__80__Seco nd_Chance_Exception_E0434F4D.dmp
> the assembly instruction at kernel32!RaiseException+53 in
> C:\WINDOWS\system32\kernel32.dll from Microsoft Corporation has caused an
> unknown exception (0xe0434f4d) on thread 14
>
>
>
> This exception originated from mscorwks!RaiseTheExceptionInternalOnly+226.
> Review the faulting call stack for thread 14 to determine root cause for
> the
> exception.
>
>
>
>
>
> Please follow up with vendor Microsoft Corporation for problem resolution
> concerning the following file:
> C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll.
> Information DebugDiag determined that this dump file
> (w3wp__PID__7652__Date__06_19_2007__Time_11_40_10AM__80__Sec ond_Chance_Exception_E0434F4D.dmp)
> is a crash dump and did not perform any hang analysis. If you wish to
> enable
> combined crash and hang analysis for crash dumps, edit the IISAnalysis.asp
> script (located in the DebugDiag\Scripts folder) and set the
> g_DoCombinedAnalysis constant to True.
>
>
>
>
>
> Analysis Details
> Table Of Contents
> w3wp__PID__7652__Date__06_19_2007__Time_11_40_10AM__80__Seco nd_Chance_Exception_E0434F4D.dmp
>
> Faulting Thread
>
> Faulting Module Information
>
>
>
>
> Report for
> w3wp__PID__7652__Date__06_19_2007__Time_11_40_10AM__80__Seco nd_Chance_Exception_E0434F4D.dmp
> Type of Analysis Performed Crash Analysis
> Machine Name SERVER
> Operating System Windows Server 2003 Service Pack 2
> Number Of Processors 2
> Process ID 7652
> Process Image c:\WINDOWS\system32\inetsrv\w3wp.exe
> System Up-Time 0 day(s) 09:20:12
> Process Up-Time 0 day(s) 00:00:45
>
>
> Thread 14 - System ID 7176
> Entry point mscorwks!ThreadpoolMgr::intermediateThreadProc
> Create time 6/19/2007 11:39:26 AM
> Time spent in user mode 0 Days 0:0:0.0
> Time spent in kernel mode 0 Days 0:0:0.15
>
>
>
>
>
>
> Function Arg 1 Arg 2 Arg 3 Source
> kernel32!RaiseException+53 e0434f4d 00000001 00000001
> mscorwks!RaiseTheExceptionInternalOnly+226 01f09290 00000000
> 00000000
> mscorwks!RaiseTheException+4c 01f09290 00000000 01cffbf8
> mscorwks!RaiseTheException+be 00000000 0ec309e0 9695272b
> mscorwks!RealCOMPlusThrow+37 01f09290 00000000 7a0e0701
> mscorwks!RealCOMPlusThrow+a 01f09290 955af301 7a36a7d0
> mscorwks!Thread::RaiseCrossContextException+63 00000000 01cffca8
> 01cffd18
> mscorwks!Thread::DoADCallBack+26c 00000002 79f3a0a1 01cffe18
> mscorwks!Thread::UserResumeThread+e1 01cffe18 01cffdc4
> 79f93fe6
>
> mscorwks!Thread::DoADCallBack+355 01cffe18 955af109 0ec309e0
> mscorwks!Thread::DoADCallBack+541 01cffe18 00000002 00000000
> mscorwks!Thread::DoADCallBack+575 00000002 7a07bdfe 01cffe6c
> mscorwks!ManagedThreadBase::ThreadPool+13 00000002 7a07bdfe
> 01cffe6c
> mscorwks!BindIoCompletionCallbackStubEx+8c 00000079 00000000
> 01eec464
> mscorwks!BindIoCompletionCallbackStub+13 00000079 00000000
> 01eec464
> mscorwks!ThreadpoolMgr::CompletionPortThreadStart+406 00000000
> 00000000 b6da3d08
> mscorwks!ThreadpoolMgr::intermediateThreadProc+49 000cd9a8
> 00000000
> 00000000
> kernel32!BaseThreadStart+34 79f710dd 000cd9a8 00000000
>
>
>
>
> In
> w3wp__PID__7652__Date__06_19_2007__Time_11_40_10AM__80__Seco nd_Chance_Exception_E0434F4D.dmp
> the assembly instruction at kernel32!RaiseException+53 in
> C:\WINDOWS\system32\kernel32.dll from Microsoft Corporation has caused an
> unknown exception (0xe0434f4d) on thread 14
>
>
>
> This exception originated from mscorwks!RaiseTheExceptionInternalOnly+226.
> Module Information
> Image Name: C:\WINDOWS\system32\kernel32.dll Symbol Type: PDB
> Base address: 0x77e40000 Time Stamp: Wed Apr 18 10:25:36 2007
> Checksum: 0x001083fc Comments:
> COM DLL: False Company Name: Microsoft Corporation
> ISAPIExtension: False File Description: Windows NT BASE API Client DLL
> ISAPIFilter: False File Version: 5.2.3790.4062
> (srv03_sp2_gdr.070417-0203)
> Managed DLL: False Internal Name: kernel32
> VB DLL: False Legal Copyright: © Microsoft Corporation. All rights
> reserved.
> Loaded Image Name: kernel32.dll Legal Trademarks:
> Mapped Image Name: Original filename: kernel32
> Module name: kernel32 Private Build:
> Single Threaded: False Product Name: Microsoft® Windows® Operating
> System
> Module Size: 1.01 MBytes Product Version: 5.2.3790.4062
> Symbol File Name:
> c:\symcache\kernel32.pdb\7FD4C98964054C24B2C472948D829DF52\k ernel32.pdb
> Special Build: &
>
>
>
>
>
>
>
>
> Script Summary
> Script Name Status Error Code Error Source Error Description Source Line
> IISAnalysis.asp Completed
>
>
>

Re: IIS Crash on Microsoft ASP page (.NET 2.0)

Downloading the debugging tools and the symbol package. I did create a dump
file so I'll take a look at it and post what I find back here.

"Pat [MSFT]" wrote:

> The exception happened in managed code - so we can't see what the problem
> is. If you had a dump created, you can take a look using WinDBG.
>
>
> Pat
>
> "Rob" wrote in message
> news:8314FEFB-D8A2-49E7-A589-2043AD6A2A28@microsoft.com...
> > We are running Microsoft Small Business Server R2. We have many of these
> > servers installed and are only experiencing this issue on one. The
> > problem
> > is that when going to the Remote Web Workplace we get a .NET unhandled
> > exception. I've run IIS Debug Diag and received the following dump and am
> > looking for some help.
> >
> >
> > Analysis Summary
> > Type Description Recommendation
> > Error In
> > w3wp__PID__7652__Date__06_19_2007__Time_11_40_10AM__80__Seco nd_Chance_Exception_E0434F4D.dmp
> > the assembly instruction at kernel32!RaiseException+53 in
> > C:\WINDOWS\system32\kernel32.dll from Microsoft Corporation has caused an
> > unknown exception (0xe0434f4d) on thread 14
> >
> >
> >
> > This exception originated from mscorwks!RaiseTheExceptionInternalOnly+226.
> > Review the faulting call stack for thread 14 to determine root cause for
> > the
> > exception.
> >
> >
> >
> >
> >
> > Please follow up with vendor Microsoft Corporation for problem resolution
> > concerning the following file:
> > C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll.
> > Information DebugDiag determined that this dump file
> > (w3wp__PID__7652__Date__06_19_2007__Time_11_40_10AM__80__Sec ond_Chance_Exception_E0434F4D.dmp)
> > is a crash dump and did not perform any hang analysis. If you wish to
> > enable
> > combined crash and hang analysis for crash dumps, edit the IISAnalysis.asp
> > script (located in the DebugDiag\Scripts folder) and set the
> > g_DoCombinedAnalysis constant to True.
> >
> >
> >
> >
> >
> > Analysis Details
> > Table Of Contents
> > w3wp__PID__7652__Date__06_19_2007__Time_11_40_10AM__80__Seco nd_Chance_Exception_E0434F4D.dmp
> >
> > Faulting Thread
> >
> > Faulting Module Information
> >
> >
> >
> >
> > Report for
> > w3wp__PID__7652__Date__06_19_2007__Time_11_40_10AM__80__Seco nd_Chance_Exception_E0434F4D.dmp
> > Type of Analysis Performed Crash Analysis
> > Machine Name SERVER
> > Operating System Windows Server 2003 Service Pack 2
> > Number Of Processors 2
> > Process ID 7652
> > Process Image c:\WINDOWS\system32\inetsrv\w3wp.exe
> > System Up-Time 0 day(s) 09:20:12
> > Process Up-Time 0 day(s) 00:00:45
> >
> >
> > Thread 14 - System ID 7176
> > Entry point mscorwks!ThreadpoolMgr::intermediateThreadProc
> > Create time 6/19/2007 11:39:26 AM
> > Time spent in user mode 0 Days 0:0:0.0
> > Time spent in kernel mode 0 Days 0:0:0.15
> >
> >
> >
> >
> >
> >
> > Function Arg 1 Arg 2 Arg 3 Source
> > kernel32!RaiseException+53 e0434f4d 00000001 00000001
> > mscorwks!RaiseTheExceptionInternalOnly+226 01f09290 00000000
> > 00000000
> > mscorwks!RaiseTheException+4c 01f09290 00000000 01cffbf8
> > mscorwks!RaiseTheException+be 00000000 0ec309e0 9695272b
> > mscorwks!RealCOMPlusThrow+37 01f09290 00000000 7a0e0701
> > mscorwks!RealCOMPlusThrow+a 01f09290 955af301 7a36a7d0
> > mscorwks!Thread::RaiseCrossContextException+63 00000000 01cffca8
> > 01cffd18
> > mscorwks!Thread::DoADCallBack+26c 00000002 79f3a0a1 01cffe18
> > mscorwks!Thread::UserResumeThread+e1 01cffe18 01cffdc4
> > 79f93fe6
> >
> > mscorwks!Thread::DoADCallBack+355 01cffe18 955af109 0ec309e0
> > mscorwks!Thread::DoADCallBack+541 01cffe18 00000002 00000000
> > mscorwks!Thread::DoADCallBack+575 00000002 7a07bdfe 01cffe6c
> > mscorwks!ManagedThreadBase::ThreadPool+13 00000002 7a07bdfe
> > 01cffe6c
> > mscorwks!BindIoCompletionCallbackStubEx+8c 00000079 00000000
> > 01eec464
> > mscorwks!BindIoCompletionCallbackStub+13 00000079 00000000
> > 01eec464
> > mscorwks!ThreadpoolMgr::CompletionPortThreadStart+406 00000000
> > 00000000 b6da3d08
> > mscorwks!ThreadpoolMgr::intermediateThreadProc+49 000cd9a8
> > 00000000
> > 00000000
> > kernel32!BaseThreadStart+34 79f710dd 000cd9a8 00000000
> >
> >
> >
> >
> > In
> > w3wp__PID__7652__Date__06_19_2007__Time_11_40_10AM__80__Seco nd_Chance_Exception_E0434F4D.dmp
> > the assembly instruction at kernel32!RaiseException+53 in
> > C:\WINDOWS\system32\kernel32.dll from Microsoft Corporation has caused an
> > unknown exception (0xe0434f4d) on thread 14
> >
> >
> >
> > This exception originated from mscorwks!RaiseTheExceptionInternalOnly+226.
> > Module Information
> > Image Name: C:\WINDOWS\system32\kernel32.dll Symbol Type: PDB
> > Base address: 0x77e40000 Time Stamp: Wed Apr 18 10:25:36 2007
> > Checksum: 0x001083fc Comments:
> > COM DLL: False Company Name: Microsoft Corporation
> > ISAPIExtension: False File Description: Windows NT BASE API Client DLL
> > ISAPIFilter: False File Version: 5.2.3790.4062
> > (srv03_sp2_gdr.070417-0203)
> > Managed DLL: False Internal Name: kernel32
> > VB DLL: False Legal Copyright: © Microsoft Corporation. All rights
> > reserved.
> > Loaded Image Name: kernel32.dll Legal Trademarks:
> > Mapped Image Name: Original filename: kernel32
> > Module name: kernel32 Private Build:
> > Single Threaded: False Product Name: Microsoft® Windows® Operating
> > System
> > Module Size: 1.01 MBytes Product Version: 5.2.3790.4062
> > Symbol File Name:
> > c:\symcache\kernel32.pdb\7FD4C98964054C24B2C472948D829DF52\k ernel32.pdb
> > Special Build: &
> >
> >
> >
> >
> >
> >
> >
> >
> > Script Summary
> > Script Name Status Error Code Error Source Error Description Source Line
> > IISAnalysis.asp Completed
> >
> >
> >
>

Re: IIS Crash on Microsoft ASP page (.NET 2.0)

Here is what the debugger reported:


Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\iPremise\IIS
Debugger\w3wp__PID__7652__Date__06_19_2007__Time_11_40_10AM_ _80__Second_Chance_Exception_E0434F4D.dmp]
User Mini Dump File with Full Memory: Only application data is available

Comment: 'Dump created by DbgHost. Second_Chance_Exception_E0434F4D'
Windows Server 2003 Version 3790 (Service Pack 2) MP (2 procs) Free x86
compatible
Product: LanManNt, suite: SmallBusiness TerminalServer
SmallBusinessRestricted SingleUserTS
Debug session time: Tue Jun 19 11:40:10.000 2007 (GMT-6)
System Uptime: 0 days 9:20:12.375
Process Uptime: 0 days 0:00:45.000
Symbol search path is:
srv*e:\ipremise\symbols*http://msdl.microsoft.com/download/s ymbols
Executable search path is:
............................................................ .........................................
Loading unloaded module list
........
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(1de4.1c08): CLR exception - code e0434f4d (first/second chance not available)
eax=01cffa1c ebx=0ec309e0 ecx=00000000 edx=00000025 esi=01cffaa8 edi=e0434f4d
eip=77e4bee7 esp=01cffa18 ebp=01cffa6c iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
kernel32!RaiseException+0x53:
77e4bee7 5e pop esi


Is there something else I need to run from within the debugger to get more
information?

Re: IIS Crash on Microsoft ASP page (.NET 2.0)

I ran the analyze -v command and the following was reported:


Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\iPremise\IIS
Debugger\w3wp__PID__6300__Date__06_19_2007__Time_10_51_29AM_ _708__Second_Chance_Exception_C0000005.dmp]
User Mini Dump File with Full Memory: Only application data is available

Comment: 'Dump created by DbgHost. Second_Chance_Exception_C0000005'
Windows Server 2003 Version 3790 (Service Pack 2) MP (2 procs) Free x86
compatible
Product: LanManNt, suite: SmallBusiness TerminalServer
SmallBusinessRestricted SingleUserTS
Debug session time: Tue Jun 19 10:51:31.000 2007 (GMT-6)
System Uptime: 0 days 8:31:41.030
Process Uptime: 0 days 0:53:56.000
Symbol search path is:
srv*e:\ipremise\symbols*http://msdl.microsoft.com/download/s ymbols
Executable search path is:
............................................................ ...................................
Loading unloaded module list
.................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(189c.19c): Access violation - code c0000005 (first/second chance not
available)
eax=800703e3 ebx=00000001 ecx=01c02710 edx=01c02ae0 esi=01c050d0 edi=000003e3
eip=001f0001 esp=0156f81c ebp=000e9bc0 iopl=0 nv up ei ng nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010282
001f0001 005800 add byte ptr [eax],bl
ds:0023:800703e3=??
0:023> !analyze -v
************************************************************ *******************
*
*
* Exception Analysis
*
*
*
************************************************************ *******************

*** ERROR: Symbol file could not be found. Defaulted to export symbols for
mscorwks.dll -

FAULTING_IP:
+1f0001
001f0001 005800 add byte ptr [eax],bl

EXCEPTION_RECORD: ffffffff -- (.exr ffffffffffffffff)
ExceptionAddress: 001f0001
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 800703e3
Attempt to write to address 800703e3

DEFAULT_BUCKET_ID: CODE_RUNNING_ON_HEAP

PROCESS_NAME: w3wp.exe

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced
memory at "0x%08lx". The memory could not be "%s".

WRITE_ADDRESS: 800703e3

BUGCHECK_STR: ACCESS_VIOLATION

IP_ON_HEAP: 001f0001

MANAGED_STACK: !dumpstack -EE
OS Thread Id: 0x19c (23)
Current frame:
ChildEBP RetAddr Caller,Callee

LAST_CONTROL_TRANSFER: from 6a2a2fef to 001f0001

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
0156f818 6a2a2fef 01c02710 800703e3 00000000 0x1f0001
0156f830 79f2f3b0 000003e3 00000000 01c02ae0
webengine!CorThreadPoolCompletionCallback+0x35
0156f894 79ecb00b 00000000 00000000 00000000
mscorwks!CreateAssemblyCache+0x21302
0156f8e0 7c82b02a 0156f9ac 7c81f1d0 0156f9ae
mscorwks!CreateApplicationContext+0xc4a7
0156f91c 7c82a124 0e940a18 0156fb50 7c82a0b8 ntdll!RtlImageNtHeaderEx+0xee
0e940000 00000000 eeffeeff 00001002 00000000
ntdll!RtlpAllocateFromHeapLookaside+0x13


FAULTING_THREAD: 0000019c

FOLLOWUP_IP:
webengine!CorThreadPoolCompletionCallback+35
6a2a2fef 5e pop esi

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: webengine!CorThreadPoolCompletionCallback+35

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: webengine

IMAGE_NAME: webengine.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 4333eca4

STACK_COMMAND: ~23s; .ecxr ; kb

FAILURE_BUCKET_ID:
ACCESS_VIOLATION_webengine!CorThreadPoolCompletionCallback+3 5

BUCKET_ID: ACCESS_VIOLATION_webengine!CorThreadPoolCompletionCallback+3 5

Followup: MachineOwner
---------

Re: IIS Crash on Microsoft ASP page (.NET 2.0)

I believe this issue is related to a problem with the machine being a domain
controller prior to the installation of SBS (non-SBS domain controller). The
Network Service account is not in the IIS_WPG security group and I think this
is contributing to the error.

The workaround is to disable access to Application Sharing servers in the
Remote Web Workplace. I have no idea what this section of Microsoft code in
the RWW is doing but it is the culprit is causing the service to crash.

I changed the registry key of
HKLM\Software\Microsoft\SmallBusinessServer\RemoteUserPortal \KWLinks\AppTS to
0 and all went fine.

Not a permanent resolution but workable for now.

Re: IIS Crash on Microsoft ASP page (.NET 2.0)

The issue is in the code - it may be that the change in roles is creating an
error state - but that is not the root cause of the failure.

Pat

"Rob" wrote in message
news:C16D7082-DD2A-4113-B968-58CF910D6E4B@microsoft.com...
>I believe this issue is related to a problem with the machine being a
>domain
> controller prior to the installation of SBS (non-SBS domain controller).
> The
> Network Service account is not in the IIS_WPG security group and I think
> this
> is contributing to the error.
>
> The workaround is to disable access to Application Sharing servers in the
> Remote Web Workplace. I have no idea what this section of Microsoft code
> in
> the RWW is doing but it is the culprit is causing the service to crash.
>
> I changed the registry key of
> HKLM\Software\Microsoft\SmallBusinessServer\RemoteUserPortal \KWLinks\AppTS
> to
> 0 and all went fine.
>
> Not a permanent resolution but workable for now.
>
>

Re: IIS Crash on Microsoft ASP page (.NET 2.0)

You need to get the managed stack. From the prompt in the debugger type:

!clrstack


Pat

"Rob" wrote in message
news:86D18AA3-D922-4340-8390-B6B7A79C4CF0@microsoft.com...
> Here is what the debugger reported:
>
>
> Microsoft (R) Windows Debugger Version 6.6.0007.5
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
> Loading Dump File [E:\iPremise\IIS
> Debugger\w3wp__PID__7652__Date__06_19_2007__Time_11_40_10AM_ _80__Second_Chance_Exception_E0434F4D.dmp]
> User Mini Dump File with Full Memory: Only application data is available
>
> Comment: 'Dump created by DbgHost. Second_Chance_Exception_E0434F4D'
> Windows Server 2003 Version 3790 (Service Pack 2) MP (2 procs) Free x86
> compatible
> Product: LanManNt, suite: SmallBusiness TerminalServer
> SmallBusinessRestricted SingleUserTS
> Debug session time: Tue Jun 19 11:40:10.000 2007 (GMT-6)
> System Uptime: 0 days 9:20:12.375
> Process Uptime: 0 days 0:00:45.000
> Symbol search path is:
> srv*e:\ipremise\symbols*http://msdl.microsoft.com/download/s ymbols
> Executable search path is:
> ............................................................ .......................................
> Loading unloaded module list
> .......
> This dump file has an exception of interest stored in it.
> The stored exception information can be accessed via .ecxr.
> (1de4.1c08): CLR exception - code e0434f4d (first/second chance not
> available)
> eax=01cffa1c ebx=0ec309e0 ecx=00000000 edx=00000025 esi=01cffaa8
> edi=e0434f4d
> eip=77e4bee7 esp=01cffa18 ebp=01cffa6c iopl=0 nv up ei pl nz na po
> nc
> cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000
> efl=00000202
> kernel32!RaiseException+0x53:
> 77e4bee7 5e pop esi
>
>
> Is there something else I need to run from within the debugger to get more
> information?

Re: IIS Crash on Microsoft ASP page (.NET 2.0)

I'm pretty sure the SBS has some special permissions on the AD OU to find the
terminal servers to determine if the item should be listed in the main menu.
Since the server was a domain controller already I think the permission did
not get applied in the setup. Disabling the feature in the aspx page works
around the problem. I wish I could find the permission problem easily but
I'm not sure how to do that. The issue, however, is clearly in the
client.aspx code segment.

Re: IIS Crash on Microsoft ASP page (.NET 2.0)

Hi Guys,
I am new to this DebugDiag analysis stuff, but looks like I have the
same problem as what you have been talking about.
IIS crash happens one every day at didfferent times during the day. The
crash dump analysis say :

Analysis Summary   class=mycustomText>In w3wp__PID__24264__Date__06_26_2007__Time_12_54_19PM__699__Se cond_Chance_ Exception_E0434F4D.dmp the assembly instruction at kernel32!RaiseException+53 in C:\WINDOWS\system32\kernel32.dll from Microsoft Corporation has caused a CLR Exception) on thread This exception originated from mscorsvr!RaiseTheException+a0. class=mycustomText>Review the faulting call stack for thread href='#24264:3607Thread30984'>53 to determine root cause for the exception. Please follow up with vendor Microsoft Corporation for problem resolution concerning the following file: C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorsvr.dll. tr> class=mycustomText>  Type Description Recommendation border=0 src=res/error.png width=16 height=16>  Error border=0 src=res/information.png width=16 height=16>  Information DebugDiag determined that this dump file (w3wp__PID__24264__Date__06_26_2007__Time_12_54_19PM__699__S econd_Chance _Exception_E0434F4D.dmp) is a crash dump and did not perform any hang analysis. If you wish to enable combined crash and hang analysis for crash dumps, edit the CrashHangAnalysis.asp script (located in the DebugDiag\Scripts folder) and set the g_DoCombinedAnalysis constant to True.

Analysis Details   class='ToggleStartCollapsed' style='cursor:hand; '> id='ScriptOff-s' style='DISPLAY: block'> src='res/information.png'> Your browser settings are currently prohibiting this report's scripts from running. This is preventing some features of this analysis report from displaying properly. To enable scripts to run, right-click the security warning above and choose "Allow Blocked Content..." or enable the "Allow active content to run in files on My Computer*" setting on the Advanced tab of your "Internet Options" dialog to avoid being prompted in the future Table Of Contents href='#Dump24264:3607-t'>w3wp__PID__24264__Date__06_26_2007__Time_12_ 54_19PM__699__Second_Chance_Exception_E0434F4D.dmp  &nbs p; Faulting Thread     href='#24264:3607Module'>Faulting Module Information style='cursor:hand; '> src='res/up.png' id='Dump24264:3607-i'> Report for w3wp__PID__24264__Date__06_26_2007__Time_12_54_19PM__699__Se cond_Chance_ Exception_E0434F4D.dmp style='DISPLAY: block'> Report for w3wp__PID__24264__Date__06_26_2007__Time_12_54_19PM__699__Se cond_Chance_ Exception_E0434F4D.dmp class=myCustomText ID="Table1"> Type of Analysis Performed   Crash Analysis Machine Name   WIC016CX Operating System   Windows Server 2003 Service Pack 1 Number Of Processors   4 Process ID   24264 Process Image   c:\WINDOWS\system32\inetsrv\w3wp.exe d> System Up-Time   243 day(s) 14:16:07 Process Up-Time   01:00:07 Thread 53 - System ID 30984 class=myCustomText> Entry point   mscorsvr!ThreadpoolMgr::intermediateThreadP roc Create time   26/06/2007 12:49:11 PM Time spent in user mode   0 Days 0:0:6.78 Time spent in kernel mode   0 Days 0:0:0.546 nowrap>mscorsvr!RegisterWaitForSingleObjectCallback_Worker+9 b nowrap>mscorsvr!RegisterWaitForSingleObjectCallback+ab nowrap>mscorsvr!ThreadpoolMgr::AsyncCallbackCompletion+16 nowrap>mscorsvr!ThreadpoolMgr::ExecuteWorkRequest+19 nowrap>mscorsvr!ThreadpoolMgr::WorkerThreadStart+129 nowrap>mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 Function     Arg 1     Arg 2     Arg 3   Source kernel32!RaiseException+53      = "courier new">e0434f4d      = "courier new">00000001      = "courier new">00000000    mscorsvr!RaiseTheException+a0      = "courier new">3e3e7c18      = "courier new">00000000      = "courier new">094cf848    mscorsvr!RealCOMPlusThrow+48      = "courier new">3e3e7c18      = "courier new">00000000      = "courier new">094cf034    mscorsvr!RealCOMPlusThrow+d      = "courier new">3e3e7c18      = "courier new">0405ec38      = "courier new">094cf12c    mscorsvr!ComToManagedExceptHandler+1ec      = "courier new">00000000      = "courier new">00000000      = "courier new">00000000    mscorsvr!ContextTransitionFrameHandler+a4      = "courier new">094cf12c      = "courier new">094cf7b0      = "courier new">094cf140    ntdll!ExecuteHandler2+26      = "courier new">094cf12c      = "courier new">094cf7b0      = "courier new">094cf140    ntdll!ExecuteHandler+24      = "courier new">094cc000      = "courier new">094cf140      = "courier new">094cf12c    ntdll!KiUserExceptionDispatcher+e      = "courier new">094cc000      = "courier new">094cf140      = "courier new">094cf12c    kernel32!RaiseException+53      = "courier new">e0434f4d      = "courier new">00000001      = "courier new">00000000    mscorsvr!RaiseTheException+a0      = "courier new">3926d810      = "courier new">00000000      = "courier new">3926d810    mscorsvr!JIT_Throw+4d      = "courier new">00000004      = "courier new">094cf58c      = "courier new">094cf5b0    0x02ae9ac5      = "courier new">00000000      = "courier new">094cf688      = "courier new">791b3ad7    mscorsvr!CallDescrWorker+30      = "courier new">094cf5c4      = "courier new">00000001      = "courier new">094cf598    mscorsvr!MethodDesc::CallDescr+1b8      = "courier new">00c0e02b      = "courier new">79b7c000      = "courier new">00000001    mscorsvr!MethodDesc::CallDescr+4f      = "courier new">79c0e02b      = "courier new">79b7c000      = "courier new">79c0e070    mscorsvr!MethodDesc::Call+97      = "courier new">094cf784      = "courier new">00154fd0      = "courier new">0405ec38         = "courier new">094cf804      = "courier new">791b3d64      = "courier new">ffffffff    mscorsvr!Thread::DoADCallBack+5c      = "courier new">00154fd0      = "courier new">79313894      = "courier new">094cf804         = "courier new">04160178      = "courier new">00000000      = "courier new">02c0d7e8         = "courier new">02c0d7e8      = "courier new">04151fd8      = "courier new">793ecec8         = "courier new">04151fd8      = "courier new">00000000      = "courier new">791d3fe5         = "courier new">00000000      = "courier new">094cf8c0      = "courier new">00090000         = "courier new">04053940      = "courier new">00000000      = "courier new">00000000    kernel32!BaseThreadStart+34      = "courier new">791fda8b      = "courier new">04053940      = "courier new">00000000    In w3wp__PID__24264__Date__06_26_2007__Time_12_54_19PM__699__Se cond_Chance_ Exception_E0434F4D.dmp the assembly instruction at kernel32!RaiseException+53 in C:\WINDOWS\system32\kernel32.dll from Microsoft Corporation has caused a CLR Exception) on thread This exception originated from mscorsvr!RaiseTheException+a0. ID="Table2"> Module Information Image Name: C:\WINDOWS\system32\kernel32.dll   Symbol Type: PDB Base address: 0x77e40000   Time Stamp: Fri Mar 25 12:30:42 2005 Checksum: 0x0010c135   Comments: COM DLL: False   Company Name: Microsoft Corporation ISAPIExtension: False   File Description: Windows NT BASE API Client DLL ISAPIFilter: False   File Version: 5.2.3790.1830 (srv03_sp1_rtm.050324-1447) Managed DLL: False   Internal Name: kernel32 VB DLL: False   Legal Copyright: © Microsoft Corporation. All rights reserved. Loaded Image Name: kernel32.dll   Legal Trademarks: Mapped Image Name:   Original filename: kernel32 Module name: kernel32   Private Build: Single Threaded: False   Product Name: Microsoft® Windows® Operating System Module Size: 1.01 MBytes   Product Version: 5.2.3790.1830 Symbol File Name: c:\symcache\kernel32.pdb\75CFE96517E5450DA600C870E95399FF2\k ernel32. pdb   Special Build: &

Script Summary   class=mycustomText>CrashHangAnalysis.asp class=mycustomText>Completed Script Name Status Error Code Error Source Error Description Source Line colspan='4'>  I do not know what it means, can you please help.\ Thanks *** Sent via Developersdex http://www.developersdex.com *** Re: IIS Crash on Microsoft ASP page (.NET 2.0) am 27.06.2007 01:21:54 von Ronny Se I have the same problem as well : the dump is here , I do not understand what it means. Please help. Analysis Summary Type Description Recommendation Error In w3wp__PID__24264__Date__06_26_2007__Time_12_54_19PM__699__Se cond_Chance_ Exception_E0434F4D.dmp the assembly instruction at kernel32!RaiseException+53 in C:\WINDOWS\system32\kernel32.dll from Microsoft Corporation has caused a CLR Exception) on thread 53 This exception originated from mscorsvr!RaiseTheException+a0. Review the faulting call stack for thread 53 to determine root cause for the exception. Please follow up with vendor Microsoft Corporation for problem resolution concerning the following file: C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorsvr.dll. Information DebugDiag determined that this dump file (w3wp__PID__24264__Date__06_26_2007__Time_12_54_19PM__699__S econd_Chance _Exception_E0434F4D.dmp) is a crash dump and did not perform any hang analysis. If you wish to enable combined crash and hang analysis for crash dumps, edit the CrashHangAnalysis.asp script (located in the DebugDiag\Scripts folder) and set the g_DoCombinedAnalysis constant to True. Analysis Details Your browser settings are currently prohibiting this report's scripts from running. This is preventing some features of this analysis report from displaying properly. To enable scripts to run, right-click the security warning above and choose "Allow Blocked Content..." or enable the "Allow active content to run in files on My Computer*" setting on the Advanced tab of your "Internet Options" dialog to avoid being prompted in the future Table Of Contents w3wp__PID__24264__Date__06_26_2007__Time_12_54_19PM__699__Se cond_Chance_ Exception_E0434F4D.dmp Faulting Thread Faulting Module Information Report for w3wp__PID__24264__Date__06_26_2007__Time_12_54_19PM__699__Se cond_Chance_ Exception_E0434F4D.dmp Report for w3wp__PID__24264__Date__06_26_2007__Time_12_54_19PM__699__Se cond_Chance_ Exception_E0434F4D.dmp Type of Analysis Performed Crash Analysis Machine Name WIC016CX Operating System Windows Server 2003 Service Pack 1 Number Of Processors 4 Process ID 24264 Process Image c:\WINDOWS\system32\inetsrv\w3wp.exe System Up-Time 243 day(s) 14:16:07 Process Up-Time 01:00:07 Thread 53 - System ID 30984 Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc Create time 26/06/2007 12:49:11 PM Time spent in user mode 0 Days 0:0:6.78 Time spent in kernel mode 0 Days 0:0:0.546 Function Arg 1 Arg 2 Arg 3 Source kernel32!RaiseException+53 e0434f4d 00000001 00000000 mscorsvr!RaiseTheException+a0 3e3e7c18 00000000 094cf848 mscorsvr!RealCOMPlusThrow+48 3e3e7c18 00000000 094cf034 mscorsvr!RealCOMPlusThrow+d 3e3e7c18 0405ec38 094cf12c mscorsvr!ComToManagedExceptHandler+1ec 00000000 00000000 00000000 mscorsvr!ContextTransitionFrameHandler+a4 094cf12c 094cf7b0 094cf140 ntdll!ExecuteHandler2+26 094cf12c 094cf7b0 094cf140 ntdll!ExecuteHandler+24 094cc000 094cf140 094cf12c ntdll!KiUserExceptionDispatcher+e 094cc000 094cf140 094cf12c kernel32!RaiseException+53 e0434f4d 00000001 00000000 mscorsvr!RaiseTheException+a0 3926d810 00000000 3926d810 mscorsvr!JIT_Throw+4d 00000004 094cf58c 094cf5b0 0x02ae9ac5 00000000 094cf688 791b3ad7 mscorsvr!CallDescrWorker+30 094cf5c4 00000001 094cf598 mscorsvr!MethodDesc::CallDescr+1b8 00c0e02b 79b7c000 00000001 mscorsvr!MethodDesc::CallDescr+4f 79c0e02b 79b7c000 79c0e070 mscorsvr!MethodDesc::Call+97 094cf784 00154fd0 0405ec38 mscorsvr!RegisterWaitForSingleObjectCallback_Worker+9b 094cf804 791b3d64 ffffffff mscorsvr!Thread::DoADCallBack+5c 00154fd0 79313894 094cf804 mscorsvr!RegisterWaitForSingleObjectCallback+ab 04160178 00000000 02c0d7e8 mscorsvr!ThreadpoolMgr::AsyncCallbackCompletion+16 02c0d7e8 04151fd8 793ecec8 mscorsvr!ThreadpoolMgr::ExecuteWorkRequest+19 04151fd8 00000000 791d3fe5 mscorsvr!ThreadpoolMgr::WorkerThreadStart+129 00000000 094cf8c0 00090000 mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 04053940 00000000 00000000 kernel32!BaseThreadStart+34 791fda8b 04053940 00000000 In w3wp__PID__24264__Date__06_26_2007__Time_12_54_19PM__699__Se cond_Chance_ Exception_E0434F4D.dmp the assembly instruction at kernel32!RaiseException+53 in C:\WINDOWS\system32\kernel32.dll from Microsoft Corporation has caused a CLR Exception) on thread 53 This exception originated from mscorsvr!RaiseTheException+a0. Module Information Image Name: C:\WINDOWS\system32\kernel32.dll Symbol Type: PDB Base address: 0x77e40000 Time Stamp: Fri Mar 25 12:30:42 2005 Checksum: 0x0010c135 Comments: COM DLL: False Company Name: Microsoft Corporation ISAPIExtension: False File Description: Windows NT BASE API Client DLL ISAPIFilter: False File Version: 5.2.3790.1830 (srv03_sp1_rtm.050324-1447) Managed DLL: False Internal Name: kernel32 VB DLL: False Legal Copyright: © Microsoft Corporation. All rights reserved. Loaded Image Name: kernel32.dll Legal Trademarks: Mapped Image Name: Original filename: kernel32 Module name: kernel32 Private Build: Single Threaded: False Product Name: Microsoft® Windows® Operating System Module Size: 1.01 MBytes Product Version: 5.2.3790.1830 Symbol File Name: c:\symcache\kernel32.pdb\75CFE96517E5450DA600C870E95399FF2\k ernel32.pdb Special Build: & Script Summary Script Name Status Error Code Error Source Error Description Source Line CrashHangAnalysis.asp Completed *** Sent via Developersdex http://www.developersdex.com *** Re: IIS Crash on Microsoft ASP page (.NET 2.0) am 27.06.2007 20:14:47 von patfilot You have a managed code exception. To find out what is actually happening you have to open the .dmp file with WinDBG and type !clrstack . Pat "Ronny Se" wrote in message news:eHZzJjEuHHA.1052@TK2MSFTNGP05.phx.gbl... >I have the same problem as well : > the dump is here , I do not understand what it means. > Please help. > > > Analysis Summary > Type Description Recommendation > Error In > w3wp__PID__24264__Date__06_26_2007__Time_12_54_19PM__699__Se cond_Chance_ > Exception_E0434F4D.dmp the assembly instruction at > kernel32!RaiseException+53 in C:\WINDOWS\system32\kernel32.dll from > Microsoft Corporation has caused a CLR Exception) on thread 53 > > > > This exception originated from mscorsvr!RaiseTheException+a0. Review > the faulting call stack for thread 53 to determine root cause for the > exception. > > > > > > Please follow up with vendor Microsoft Corporation for problem > resolution concerning the following file: > C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorsvr.dll. > Information DebugDiag determined that this dump file > (w3wp__PID__24264__Date__06_26_2007__Time_12_54_19PM__699__S econd_Chance > _Exception_E0434F4D.dmp) is a crash dump and did not perform any hang > analysis. If you wish to enable combined crash and hang analysis for > crash dumps, edit the CrashHangAnalysis.asp script (located in the > DebugDiag\Scripts folder) and set the g_DoCombinedAnalysis constant to > True. > > > > > > Analysis Details > > > > Your browser settings are currently prohibiting this report's scripts > from running. > > This is preventing some features of this analysis report from displaying > properly. To enable scripts to run, right-click the security warning > above and choose "Allow Blocked Content..." or enable the "Allow active > content to run in files on My Computer*" setting on the Advanced tab of > your "Internet Options" dialog to avoid being prompted in the future > > > > > > Table Of Contents > w3wp__PID__24264__Date__06_26_2007__Time_12_54_19PM__699__Se cond_Chance_ > Exception_E0434F4D.dmp > > Faulting Thread > > Faulting Module Information > > > > Report for > w3wp__PID__24264__Date__06_26_2007__Time_12_54_19PM__699__Se cond_Chance_ > Exception_E0434F4D.dmp > > > > > Report for > w3wp__PID__24264__Date__06_26_2007__Time_12_54_19PM__699__Se cond_Chance_ > Exception_E0434F4D.dmp > Type of Analysis Performed Crash Analysis > Machine Name WIC016CX > Operating System Windows Server 2003 Service Pack 1 > Number Of Processors 4 > Process ID 24264 > Process Image c:\WINDOWS\system32\inetsrv\w3wp.exe > System Up-Time 243 day(s) 14:16:07 > Process Up-Time 01:00:07 > > > Thread 53 - System ID 30984 > Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc > Create time 26/06/2007 12:49:11 PM > Time spent in user mode 0 Days 0:0:6.78 > Time spent in kernel mode 0 Days 0:0:0.546 > > > > > > > Function Arg 1 Arg 2 Arg 3 Source > kernel32!RaiseException+53 e0434f4d 00000001 00000000 > mscorsvr!RaiseTheException+a0 3e3e7c18 00000000 094cf848 > mscorsvr!RealCOMPlusThrow+48 3e3e7c18 00000000 094cf034 > mscorsvr!RealCOMPlusThrow+d 3e3e7c18 0405ec38 094cf12c > mscorsvr!ComToManagedExceptHandler+1ec 00000000 00000000 > 00000000 > mscorsvr!ContextTransitionFrameHandler+a4 094cf12c 094cf7b0 > 094cf140 > ntdll!ExecuteHandler2+26 094cf12c 094cf7b0 094cf140 > ntdll!ExecuteHandler+24 094cc000 094cf140 094cf12c > ntdll!KiUserExceptionDispatcher+e 094cc000 094cf140 094cf12c > kernel32!RaiseException+53 e0434f4d 00000001 00000000 > mscorsvr!RaiseTheException+a0 3926d810 00000000 3926d810 > mscorsvr!JIT_Throw+4d 00000004 094cf58c 094cf5b0 > 0x02ae9ac5 00000000 094cf688 791b3ad7 > mscorsvr!CallDescrWorker+30 094cf5c4 00000001 094cf598 > mscorsvr!MethodDesc::CallDescr+1b8 00c0e02b 79b7c000 > 00000001 > mscorsvr!MethodDesc::CallDescr+4f 79c0e02b 79b7c000 79c0e070 > mscorsvr!MethodDesc::Call+97 094cf784 00154fd0 0405ec38 > mscorsvr!RegisterWaitForSingleObjectCallback_Worker+9b 094cf804 > 791b3d64 ffffffff > mscorsvr!Thread::DoADCallBack+5c 00154fd0 79313894 094cf804 > mscorsvr!RegisterWaitForSingleObjectCallback+ab 04160178 > 00000000 02c0d7e8 > mscorsvr!ThreadpoolMgr::AsyncCallbackCompletion+16 02c0d7e8 > 04151fd8 793ecec8 > mscorsvr!ThreadpoolMgr::ExecuteWorkRequest+19 04151fd8 00000000 > 791d3fe5 > mscorsvr!ThreadpoolMgr::WorkerThreadStart+129 00000000 094cf8c0 > 00090000 > mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 04053940 > 00000000 00000000 > kernel32!BaseThreadStart+34 791fda8b 04053940 00000000 > > > > > In > w3wp__PID__24264__Date__06_26_2007__Time_12_54_19PM__699__Se cond_Chance_ > Exception_E0434F4D.dmp the assembly instruction at > kernel32!RaiseException+53 in C:\WINDOWS\system32\kernel32.dll from > Microsoft Corporation has caused a CLR Exception) on thread 53 > > > > This exception originated from mscorsvr!RaiseTheException+a0. Module > Information > Image Name: C:\WINDOWS\system32\kernel32.dll Symbol Type: PDB > Base address: 0x77e40000 Time Stamp: Fri Mar 25 12:30:42 2005 > Checksum: 0x0010c135 Comments: > COM DLL: False Company Name: Microsoft Corporation > ISAPIExtension: False File Description: Windows NT BASE API Client > DLL > ISAPIFilter: False File Version: 5.2.3790.1830 > (srv03_sp1_rtm.050324-1447) > Managed DLL: False Internal Name: kernel32 > VB DLL: False Legal Copyright: © Microsoft Corporation. All rights > reserved. > Loaded Image Name: kernel32.dll Legal Trademarks: > Mapped Image Name: Original filename: kernel32 > Module name: kernel32 Private Build: > Single Threaded: False Product Name: Microsoft® Windows® Operating > System > Module Size: 1.01 MBytes Product Version: 5.2.3790.1830 > Symbol File Name: > c:\symcache\kernel32.pdb\75CFE96517E5450DA600C870E95399FF2\k ernel32.pdb > Special Build: & > > > > > > > > > > Script Summary > Script Name Status Error Code Error Source Error Description Source > Line > CrashHangAnalysis.asp Completed > > > > > *** Sent via Developersdex http://www.developersdex.com *** Re: IIS Crash on Microsoft ASP page (.NET 2.0) am 27.06.2007 23:52:01 von Rob The problem when I had it was directly related to the client.aspx code used by Small Business Server and the permissions required to determine if a terminal server exists in the domain. When upgrading from an existing domain the user accounts did not have the permissions to get the information from the domain controller although I'm not sure what permissions are required. For a workaround in this case I disabled the feature by changing the registry key HKLM\SOFTWARE\Microsoft\SmallBusinessServer\RemoteUserPortal \KWLinks\AppTS to 0 rather than 1. This disables accessing the terminal server through the Remote Web Workplace.