|
Home > Archive > IIS Server > January 2005 > IIS 6.0: How to add isapi filter?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
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
| |
| Wade A. Hilmo [MS] 2005-01-27, 5:52 pm |
| 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@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
>
>
| |
|
| If the process is same as in IIS 5.0, then:
A. I should be able to add a filter via the web site property page under the
Isapi Filter Tab and there is no need to setup anything for this filter
under the Web service Extensions, True? Why then I don't see the GREEN up
arrow under the status in ISM same as in IIS 5.0?
B. How is "Web Services Extensions" used, when do you add a filter there? I
see it has ASP.NET and ASP Pages in there with status allowed.
Thanks for your help.
Paul
"Wade A. Hilmo [MS]" <wadeh@microsoft.com> wrote in message
news:%23DOutuLBFHA.3820@TK2MSFTNGP11.phx.gbl...
> 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@apsc.com> wrote in message
> news:uL0gfOKBFHA.2076@TK2MSFTNGP15.phx.gbl...
tool[vbcol=seagreen]
> get
> and
isapi[vbcol=seagreen]
> effect.
> related
a[vbcol=seagreen]
>
>
| |
| Wade A. Hilmo [MS] 2005-01-28, 5:54 pm |
| Hi Paul,
A. As I explained in my previous post, the worker process (which is where
your filter is loaded) is not started until it's needed. You have to make a
request.
B. "Web Services Extensions" has nothing to do with filters. The entries
that you see for ASP.NET and ASP are for extensions.
Thank you,
-Wade A. Hilmo,
-Microsoft
PS: The MMC snap-in is not a very good way to determine the status of your
filter in IIS 6. The issue is that IIS 6 can have many worker processes and
it's possible that the filter may load in some, but not others - yet the UI
has no way to convey this information. All the UI does is check a single
flag in the metabase for the filter state. Again, as I posted, if a worker
process is unable to load a filter, then it will fail to start and an event
will be written to the event log.
"PaulT" <pthakur@apsc.com> wrote in message
news:#6i6VQMBFHA.3588@TK2MSFTNGP11.phx.gbl...
> If the process is same as in IIS 5.0, then:
> A. I should be able to add a filter via the web site property page under
the
> Isapi Filter Tab and there is no need to setup anything for this filter
> under the Web service Extensions, True? Why then I don't see the GREEN up
> arrow under the status in ISM same as in IIS 5.0?
>
> B. How is "Web Services Extensions" used, when do you add a filter there?
I
> see it has ASP.NET and ASP Pages in there with status allowed.
>
> Thanks for your help.
> Paul
>
>
>
>
> "Wade A. Hilmo [MS]" <wadeh@microsoft.com> wrote in message
> news:%23DOutuLBFHA.3820@TK2MSFTNGP11.phx.gbl...
> There
be[vbcol=seagreen]
> installing
> I've
user[vbcol=seagreen]
> will
> must
> tool
can't[vbcol=seagreen]
setup/configured[vbcol=seagreen]
extension"[vbcol=seagreen]
> isapi
than[vbcol=seagreen]
a[vbcol=seagreen]
made[vbcol=seagreen]
> a
>
>
| |
|
| Thanks!!!
I figured out the problem, didn't have required permissions on the default
web site where I was tried to add the isapi filter, should have known
better.
>Paul
"Wade A. Hilmo [MS]" <wadeh@microsoft.com> wrote in message
news:uyTGCFVBFHA.3824@TK2MSFTNGP10.phx.gbl...
> Hi Paul,
>
> A. As I explained in my previous post, the worker process (which is where
> your filter is loaded) is not started until it's needed. You have to make
a
> request.
>
> B. "Web Services Extensions" has nothing to do with filters. The entries
> that you see for ASP.NET and ASP are for extensions.
>
> Thank you,
> -Wade A. Hilmo,
> -Microsoft
>
> PS: The MMC snap-in is not a very good way to determine the status of your
> filter in IIS 6. The issue is that IIS 6 can have many worker processes
and
> it's possible that the filter may load in some, but not others - yet the
UI
> has no way to convey this information. All the UI does is check a single
> flag in the metabase for the filter state. Again, as I posted, if a
worker
> process is unable to load a filter, then it will fail to start and an
event
> will be written to the event log.
>
> "PaulT" <pthakur@apsc.com> wrote in message
> news:#6i6VQMBFHA.3588@TK2MSFTNGP11.phx.gbl...
> the
up[vbcol=seagreen]
there?[vbcol=seagreen]
> I
may[vbcol=seagreen]
> be
the[vbcol=seagreen]
snapin[vbcol=seagreen]
the[vbcol=seagreen]
> user
that[vbcol=seagreen]
worker[vbcol=seagreen]
Admin[vbcol=seagreen]
> can't
> setup/configured
> extension"
> than
relate[vbcol=seagreen]
> a
> made
>
>
|
|
|
|
|