Article ID: 931208 - Last Review: February 22, 2007 - Revision: 1.2

How to create a log file that can help troubleshoot IIS Admin Base Objects (ABO) Mapper errors in Microsoft Internet Information Services 7.0

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Important This article contains information about how to modify the registry. Make sure that you 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://support.microsoft.com/kb/256986/ ) Description of the Microsoft Windows registry
Expand all | Collapse all

INTRODUCTION

This article discusses how to create a log file that can help troubleshoot Microsoft Internet Information Services (IIS) Admin Base Object (ABO) Mapper errors in IIS 7.0.

MORE INFORMATION

IIS 7.0 includes a compatibility feature that enables scripts and programs that used ABO in earlier versions of IIS to work with IIS 7.0. This compatibility feature is known as the ABO Mapper.

Changes that are made by the legacy scripts and code that use ABO are written to the ApplicationHost.config file in IIS 7.0. The ABO Mapper subcomponent maps the legacy metabase configuration settings to the new distributed configuration system in IIS 7.0. In some cases, this subcomponent may encounter problems.

To help troubleshoot these problems, you can configure the computer that is running IIS 7.0 to create an error log file for the ABO Mapper feature. To do this, 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 the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
  1. Click Start, type regedit in the Start Search box, and then press ENTER.

    If you are prompted for an administrator password or confirmation, type the password or click Continue.
  2. In Registry Editor, locate the following registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IISADMIN
  3. Right-click IISADMIN, point to New, and then click Key.
  4. Type Parameters for the new key name, and then press ENTER.
  5. Right-click Parameters, point to New, and then click DWORD (32-bit) Value.
  6. Type EnableABOMapperLog for the DWORD Value name, and then press ENTER.
  7. Right-click EnableABOMapperLog, and then click Modify.
  8. Set the Value data value to 1 to enable the log file. A value of 0 turns off ABOMapper logging.
  9. Close the registry.
  10. Click Start, type Services in the Start Search box, and then click Services.

    If you are prompted for an administrator password or confirmation, type the password or click Continue.
  11. In Services, right-click IIS Admin Service, and then click Restart.
By default, all errors that occur during the ABOMapper process are written to the Abomapper.log file. This log file is located in the %windir%\System32\ folder. Only members of the Administrators group can access the Abomapper.log file.
APPLIES TO
  • Microsoft Internet Information Services 7.0
Back to the top
Keywords: 
kbhowto kbinfo kbexpertiseinter KB931208