IIS 6.0: How to add isapi filter?

In IIS 5.0, adding an isapi filter was straight forward via ISM Admin tool
using property pages. I tried the same steps in IIS 6.0, however I can't get
the filter to load. Is there something that needs to be setup/configured
else where:

1. Web Service Extensions?
I even changed the status to "Allowed" for "All unknown isapi extension" and
CGI extensions, didn't help.

2. Do I need to setup a Web Service Extension first and then add the isapi
filter on a web site via web site property page. I did try that, no effect.
I am not sure how the Web Service Extensions as setup in IIS 6.0 get related
to the isapi filter entry in the property page of a web site other than
pointing to the same physical path for the executable. How do I relate a
specific Web Service Extension to selected web sites?

I don't want this filter to apply to all sites.

I did restart IIS multiple times after each change just incase taht made a
difference.

Any help will be appreciated.
Thanks,
Paul

Hi Paul,

How are you determining that the filter is not loading?

The process of installing a filter in IIS 6 is exactly the same as 5. There
are two differences, though. First off, IIS 6 does not start a worker
process until it's needed to handle a request. Because of that, it may be
necessary to actually make a request to the site in which you are installing
the filter so that the process starts. Second, it is possible that the
worker process may not have sufficient rights to the metabase key that
stores the flag that the filter is loaded. In this case, the MMC snapin
might report the filter as unloaded when it's really there. Note that I've
only seen this happen when someone has applied either custom ACLs to the
metabase, or when they are running the worker process with a customer user
account.

The filter is configured to load, and fails. There are two things that will
happen. First, IIS will write and event to the log. Second, the worker
process will fail to start (a new feature in IIS 6 is that all filters must
load, in order for process initialization to succeed.)

Thank you,
-Wade A. Hilmo,
-Microsoft

"PaulT" <pthakur.TakeThisOut@apsc.com> wrote in message
news:uL0gfOKBFHA.2076@TK2MSFTNGP15.phx.gbl...
 > In IIS 5.0, adding an isapi filter was straight forward via ISM Admin tool
 > using property pages. I tried the same steps in IIS 6.0, however I can't
get
 > the filter to load. Is there something that needs to be setup/configured
 > else where:
 >
 > 1. Web Service Extensions?
 > I even changed the status to "Allowed" for "All unknown isapi extension"
and
 > CGI extensions, didn't help.
 >
 > 2. Do I need to setup a Web Service Extension first and then add the isapi
 > filter on a web site via web site property page. I did try that, no
effect.
 > I am not sure how the Web Service Extensions as setup in IIS 6.0 get
related
 > to the isapi filter entry in the property page of a web site other than
 > pointing to the same physical path for the executable. How do I relate a
 > specific Web Service Extension to selected web sites?
 >
 > I don't want this filter to apply to all sites.
 >
 > I did restart IIS multiple times after each change just incase taht made a
 > difference.
 >
 > Any help will be appreciated.
 > Thanks,
 > Paul
 >
 ><!-- ~MESSAGE_AFTER~ -->