Wade
Wed Aug 25 17:27:52 CDT 2004
Hi Rob,
It sounds like there was some problem with the metabase settings on the new
machines. Specifically, the web server did not find the registered filter,
so it never tried to load it (and never wrote an event, since it didn't know
that it was supposed to load a filter.)
As such, this is probably a metabase issue, and not an ISAPI filter issue.
Also, I don't believe that it's supported to copy the XML around from
machine to machine. There is a tool (I think it's called the migration
wizard) that can be used to do this.
Thank you,
-Wade A. Hilmo,
-Microsoft
"Robert Sutter" <sutter@magnet.fsu.edu> wrote in message
news:OE3surqiEHA.4092@TK2MSFTNGP10.phx.gbl...
> While these solutions didn't apply to my particular problem, I did stumble
> across a solution that may help Mark and others.
>
> As I mentioned, we are using NLB on 2K3, three identically configured
> machines (excepting IP's of course). To keep the configurations as
> identical as possible, we created all of the sites on one machine (the one
> on which the filter worked), exported the configuration to an XML file,
and
> imported the configuration to the other two machines. Everything appeared
> to work fine, as you would expect, except for the Filter loading.
>
> Solution: Create a new site on machines 2 and 3 ("Site 2") and install the
> filter into these new sites. Filter loads and works immediately.
>
> Wade - I don't know whether or not this officially qualifies as a bug with
> IIS 6, but I believe it should be forwarded along. The problem does not
> resolve itself with removal/reinstallation of the filter DLL. If you
would
> like any more information from me, including Filter code, MetaBase
> configuration, etc., please contact me by email. Thanks for your help.
>
> Rob Sutter
>
>
> "Wade A. Hilmo [MS]" <wadeh@microsoft.com> wrote in message
> news:%23vS3AovhEHA.2624@TK2MSFTNGP12.phx.gbl...
> > Hi Mark and Robert,
> >
> > If IIS is unable to load a filter, it will create an event log entry
that
> > explains what happened. I made a post some time ago in another group
> > outlining the ways that a filter can fail to load. Here is a link to
it:
> >
> >
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=ew1XCpUsCHA.868%40TK2MSFTNGP12&rnum=2&prev=/groups%3Fq%3Disapi%2Bfilter%2Bdata%2Berror%2Bcode%2Bwadeh%2Bevent%26ie%3DUTF-8%26hl%3Den
> >
> > I hope that this helps,
> > -Wade A. Hilmo,
> > -Microsoft
> >
> > "Mark Bedser" <mar.bedser@madgex.com> wrote in message
> > news:eSr$jJqhEHA.556@tk2msftngp13.phx.gbl...
> >> I am having exactly the same issue except I have yet to get the filter
to
> >> work on Windows Server 2003...
> >>
> >> "Robert Sutter" <sutter@magnet.fsu.edu> wrote in message
> >> news:uCTkw9VhEHA.904@TK2MSFTNGP09.phx.gbl...
> >> > Greeting all,
> >> >
> >> > I'm receiving inconsistent behavior when I try to load an in-house
> > written
> >> > ISAPI filter under IIS 6. We have three identical machines running
> >> Windows
> >> > Server 2003 Standard Edition and IIS 6; the only difference between
the
> >> > machines from hardware to software to configuration is the IP
address.
> > At
> >> > least, that's the only _intentional_ difference. The first machine
> > loads
> >> > the filter fine, and it works perfectly. The other two machines
> > "pretend"
> >> > to load the filter (it's listed on the ISAPI tab under IIS Manager)
but
> >> > never actually open the file. I know this is the case from using
file
> >> > handle monitoring tools to watch both the DLL and the configuration
> >> > file
> >> it
> >> > should open. The filter loads consistently and functions correctly
> > under
> >> > IIS 5 and 5.1; this problem behavior only occurs under IIS 6. Is
there
> >> any
> >> > reason why the filter won't even attempt to load on Windows Server
2003
> > on
> >> > some machines, but not others? I've googled this to death, can't
seem
> > to
> >> > get anywhere on my own. Extra information below.
> >> >
> >> >
> >> > Thanks,
> >> > Robert Sutter
> >> >
> >> > Operating System: Windows Server 2003, Standard Edition
> >> > IIS Version: 6.0
> >> > Filter Exports (from .def file) DllMain, HttpFilterProc,
> >> GetFilterVersion
> >> > HTTP_FILTER_VERSION * pVer
> >> > pVer->dwFilterVersion = HTTP_FILTER_REVISION;
> >> > pVer->dwFlags = SF_NOTIFY_ORDER_LOW |
> >> > SF_NOTIFY_SECURE_PORT |
> >> > SF_NOTIFY_NONSECURE_PORT |
> >> > SF_NOTIFY_PREPROC_HEADERS |
> >> > 0;
> >> >
> >> >
> >>
> >>
> >
> >
>
>