The status of the ISAPI filter appears as "Unknown" in the MMC when you load multiple ISAPI filters (280107)



The information in this article applies to:

  • Microsoft Internet Information Server 4.0
  • Microsoft Internet Information Services 5.0

This article was previously published under Q280107
We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 6.0 running on Microsoft Windows Server 2003. IIS 6.0 significantly increases Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site:

SYMPTOMS

A global Internet Server API (ISAPI) filter is loaded at the server level in the Internet Information Server (IIS) Snap-in. Although a global ISAPI filter can only be loaded one time, it performs its intended function on every site that the server hosts.

Alternatively, ISAPI filters can be loaded for each site individually. Although this method is discouraged, you can use this method, and it will work as expected. However, the IIS 4.0 Snap-in will not display the correct status in the Microsoft Management Console (MMC). After the ISAPI filter is loaded for the first Web site, the status of the ISAPI filter appears as "Unknown" for each later load, even though the filter functions for every site for which the filter is loaded.

WORKAROUND

To work around this issue in Microsoft Internet Information Services 5.0, modify the FilterFlags key in the IIS metabase for the sites that have an "Unknown" status. To do this, follow these steps:
  1. Click Start, click Run, type Cmd, and then click OK.
  2. Use the CD command to change to the Inetpub\Adminscripts folder.
  3. At the command prompt, type the following command, and then press ENTER:

    adsutil.vbs get W3svc/siteid/Filters/filtername/FilterFlags

    Note siteid is the site number and filtername is the name of the filter.
  4. Note the numeric value that is returned in the enumeration.
  5. At the command prompt, type the following command, and then press ENTER:

    adsutil.vbs set W3svc/siteid/Filters/filtername/FilterFlags "number"

    Note siteid is the site number, filtername is the name of the filter, and number is the numeric value that you noted in step 4.
  6. Repeat step 5 for each site where the "Unknown" status appears.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

Modification Type:MinorLast Reviewed:6/23/2005
Keywords:kbbug kbpending KB280107