Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 909888 - Last Review: December 3, 2007 - Revision: 1.2
How to generate debug information for ISAPI extensions in IIS 6.0
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986Â
(http://kbalertz.com/Feedback.aspx?kbNumber=256986/
)
Description of the Microsoft Windows registry
The source code for Microsoft Internet Information Services (IIS) 6.0 contains debug statements to report debug information for ISAPI extensions. This article describes how to configure a computer to generate debug information for ISAPI extensions in IIS 6.0.
To configure a computer to generate debug information for ISAPI extensions, follow these steps.
Create a registry key
To create the required registry key, follow these steps:
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
- Click Start, click Run, type Regedit.exe, and then click OK.
- Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters
- Right-click Parameters, point to New, and then click Key.
- Type W3ISAPI, and then press ENTER.
- Right-click W3ISAPI, point to New, and then click DWORD Value.
- Type debugflags, and then press ENTER.
- Right-click debugflags, and then click Modify.
- In the Value data box, type the flag value that you want, and then click OK. The valid flag values appear in the following table.
Collapse this tableExpand this table
| Flag value | Statement |
|---|
| 0x80000000 | Print a debug line when an attempt is made to load an ISAPI extension. |
| 0x10000000 | Print a debug line when the HttpExtensionProc function for an ISAPI extension is called. |
| 0x01000000 | Print a debug line when an ISAPI extension calls the GetServerVariable function. |
| 0x02000000 | Print a debug line when an ISAPI extension calls the ServerSupportFunction function. |
| 0x04000000 | Print a debug line specific to the ServerSupportFunction function command that is called by an ISAPI extension. |
| 0x08000000 | Do not print the first part of the buffer when printing debug output of functions that use non-string buffers. Examples of functions that use non-string buffers are the ReadClient and WriteClient functions. |
| 0x00100000 | Print a debug line when an ISAPI function fails. |
| 0x00200000 | Print a debug line when an ISAPI function succeeds. |
| 0x00400000 | Print a debug line when an ISAPI extension calls the ReadClient function. |
| 0x00800000 | Print a debug line when an ISAPI extension calls the WriteClient function. |
| 0xffffffff | Print all debug lines. |
Use the WinDbg debugger (Windbg.exe) to view the debug output
To use Windbg.exe to view the debug output, follow these steps:
- Download and then install the Debugging Tools for Windows. To download the Debugging Tools for Windows, visit the following Microsoft Web site:
- Run Windbg.exe. By default, the Windbg.exe file is located in the following folder:
Drive:\Program Files\Debugging Tools for Windows
Note Drive represents the hard disk on which Windows is installed. - On the File menu, click Attach to a Process.
- In the Attach to Process box, click the inetinfo.exe node, and then click OK.
- In the Workspace 'base' dialog box, click Yes.
APPLIES TO
- Microsoft Internet Information Services 6.0
| kbhowto kbinetdev kbdebug kbisapiext KB909888 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate