Re: ISAP filter in IIS 5 and IIS6, error message

From: David Wang [Msft] (someone_at_online.microsoft.com)
Date: 11/05/04 

Date: Thu, 4 Nov 2004 23:50:53 -0800

I do not see a crash -- only DLLs loading.

Can you get a stack trace of the crash when you trigger it? You will get a
debugger prompt and after setting up symbols (use Symbols Server -- the URL
I gave you has instructions on how to do this), so please enter ~*k

And post the output. 

-- 
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Lucas Albers" <LucasAlbers@discussions.microsoft.com> wrote in message
news:E44CAAE3-12CA-407E-BC75-17090130DFE7@microsoft.com...
"David Wang [Msft]" wrote:
> Do you have 3rd party server components installed?
>
> Some of them may have extensions in the IIS UI which are crashing (for
> whatever reason).
>
> The fastest way to troubleshoot this is to attach a debugger (see
> http://www.microsoft.com/ddk/debugging ) onto mmc.exe after you launch the
> IIS Manager UI, then click on the ISAPI Filter tab to cause the crash, and
> see what DLL crashed inside the debugger.  Then follow up for support with
> the owner of that DLL.
I did that, and appears that this dll crashed:
cnfgprts.ocx
windbg output:
ModLoad: 6e2b0000 6e2b8000   c:\winnt\system32\INETSLOC.dll
(66c.658): C++ EH exception - code e06d7363 (first chance)
(66c.658): C++ EH exception - code e06d7363 (first chance)
(66c.658): C++ EH exception - code e06d7363 (first chance)
(66c.658): C++ EH exception - code e06d7363 (first chance)
ModLoad: 64e40000 64e60000   C:\WINNT\system32\inetsrv\cnfgprts.ocx
ModLoad: 695e0000 69609000   c:\winnt\system32\OLEPRO32.DLL
ModLoad: 777f0000 777f5000   c:\winnt\system32\rasadhlp.dll
(66c.658): C++ EH exception - code e06d7363 (first chance)
(66c.658): C++ EH exception - code e06d7363 (first chance)
ModLoad: 64e40000 64e60000   C:\WINNT\system32\inetsrv\cnfgprts.ocx

Relevant Pages

  • Re: dll debugging techniques (ATL/directshow)
    ... >use the DLL from my application for a while, ... >This doesn't happen when I run the application within the debugger. ... >consistent - it will sometimes crash quickly, ... >I've run some checks for memory leaks and corrupted strings, ...
    (microsoft.public.multimedia.directx.dshow.programming)
  • IISstate issues...
    ... Symbol search path is: ... The debugger does not have a current process or thread ... ModLoad: 77f40000 77ffa000 C:\WINDOWS\system32\ntdll.dll ...
    (microsoft.public.inetserver.iis)
  • RE: Application crashing in ntdll.dll with message dll not found
    ... windbg and dependency walker outputs pasted below: ... ModLoad: 7c800000 7c8c0000 ntdll.dll ... Successfully hooked module. ... DLL required by the OS to run. ...
    (microsoft.public.vsnet.debugging)
  • Re: JNI EXCEPTION_ACCESS_VIOLATION
    ... I am not experienced in coding a dll and access it via ... Java, but, I would say to you that, if you do not mind, try to use the ... The code will crash when running under XP Service Pack 2 ... The code will NOT crash when running under Windows 2000 Service Pack 4 ...
    (comp.lang.java.programmer)
  • Re: Exporting global data from a DLL to an EXE
    ... like everyone else you use the obscure and meaningless word "crash" without ... Avoid making variables in a DLL visible. ... > - In the EXE I have used the keyword DLLIMPORT ... MVP Tips: http://www.flounder.com/mvp_tips.htm ...
    (microsoft.public.vc.mfc)