How to debug InProc COM components inside IIS using WINDBG
Article ID: 192754 - View products that this article applies to.
This article was previously published under Q192754
This article explains how to use WinDbg in case of an Active Server Pages (ASP) 'ASP0115 Access Violation' error during the execution of a custom component that is written in Visual C++ or Visual Basic.
You can use WinDbg to further debug the component to find the actual line of code that the component is failing on.
Install WinDbg from the Microsoft Platform SDK.
Follow the instructions below for running it. Turn off Code Optimization in your compiler and compile the debug version with the .pdb files. The debug symbols (.pdb files) for your custom component should be placed in the same folder as the .dll file, and when you use WinDbg make sure the source files for your component are available on the server. To use WinDbg, follow these steps:
For more information on remote debugging with WindDbg, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/121543/ )Setting up for remote debugging
(http://support.microsoft.com/kb/148954/ )How to set up a remote debug session using a modem
(http://support.microsoft.com/kb/151981/ )How to set up a remote debug session using a null modem cable
148659For more information on debugging components, see the following Knowledge Base articles:
(http://support.microsoft.com/kb/148659/ )How to set up Windows NT Debug Symbols
(http://support.microsoft.com/kb/166275/ )How to debug a native code Visual Basic component in VC++
(http://support.microsoft.com/kb/183480/ )How to debug ISAPI DLLs under IIS 4.0 and IIS 5.0
Article ID: 192754 - Last Review: May 29, 2006 - Revision: 4.0