ISAPI Filters

David,

thanks for the reply. The ASAPI Filter is the jk 1.2 dll
for bridging to Tomcat 4.x. The filetr config was and is
fine. Some changes were made to the Web ServerService
configuration (I don't know what changes were made).

Fortunately, we had a backup of the configuration which we
have been able to roll back to, and that has fixed the
problem. It would still be nice to know why IIS was trying
to load the DLL in protected mode and where this is turned
on/off!

Thanks,

J


 >-----Original Message-----
 >In general, you have to know EXACTLY what you are doing
when configuring an
 >ISAPI Filter, ISAPI Extension, or CGI, as any
misconfiguration will likely
 >cause either server malfunction or whatever you were
doing won't work
 >correctly. Plus, it's quite difficult to troubleshoot
this sort of issue
 >with second-hand information, so you must be patient,
provide the right
 >information using consistent terminology, and be very
observant.
 >
 >Please give:
 >- the filename and path of the "ISAPI Filter" you are
referring to.
 >- where this "configuration change" is happening -- is it
in the ISAPI
 >Filters tab (if so, is it at the website level or global
level), the
 >Application Mappings tab (if so, for what extensions, and
what is the
 >checked-status of the Script Engine and "Check if file
exists" options), or
 >somewhere else (describe the tab).
 >- what event log entries are associated with
the "problem" you are observing
 >- what do you mean by "executed in DOS mode" -- default
IIS configuration
 >does not show execution on the screen at all, so it seems
like you have some
 >other system modifications in play that you must describe.
 >- are requests actually failing, or are you just
concerned about something
 >executing in a "DOS mode".
 >
 >--
 >//David
 >IIS
 >This posting is provided "AS IS" with no warranties, and
confers no rights.
 >//
 >"Jay" <jbrister.RemoveThis@redfig.com> wrote in message
 >news:4fe101c3e4c6$a911cf00$a401280a@phx.gbl...
 >Hi,
 >
 >please can someone shed some light on a problem I am
 >having with IIS 4.0 on NT 4? I have an ISAPI Filter which
 >was working correctly. Recently some changes were made to
 >the IIS configuration which has resulted in the DLL being
 >loaded and executed in DOS mode.
 >
 >Does anyone know what I need to do to stop this from
 >happening? The DLL will not execute in DOS mode, and I
 >cannot find out why IIS is trying to load it in this way.
 >
 >Many thanks,
 >
 >J
 >
 >
 >.
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: ISAPI Filters 

To be blunt, IIS is not intentionally trying to load the DLL in protected
mode in a random fashion just to spite you -- the problem is that someone
screwed up the configuration of IIS. IIS is being a good program in
following your instructions -- whether it's good or bad -- because it's
trusting that the administrator can make the right decisions.

The holy grail of Artificial Intelligence has not been reached in Software
engineering, so programs aren't going to try and make decisions for you to
intentionally annoy you (despite what appearances may suggest) -- the human
is still in control.

I have no idea what you are describing, so I cannot offer any advice on what
to turn on/off -- but I can tell you that when IIS is executing there should
be no "DOS mode" windows visible and that there's no IIS configuration to
turn these windows on/off -- so your problem is probably not with IIS
configuration.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Jay" <jbrister.RemoveThis@redfig.com> wrote in message
news:544101c3e4da$5ab83150$a601280a@phx.gbl...
David,

thanks for the reply. The ASAPI Filter is the jk 1.2 dll
for bridging to Tomcat 4.x. The filetr config was and is
fine. Some changes were made to the Web ServerService
configuration (I don't know what changes were made).

Fortunately, we had a backup of the configuration which we
have been able to roll back to, and that has fixed the
problem. It would still be nice to know why IIS was trying
to load the DLL in protected mode and where this is turned
on/off!

Thanks,

J


 >-----Original Message-----
 >In general, you have to know EXACTLY what you are doing
when configuring an
 >ISAPI Filter, ISAPI Extension, or CGI, as any
misconfiguration will likely
 >cause either server malfunction or whatever you were
doing won't work
 >correctly. Plus, it's quite difficult to troubleshoot
this sort of issue
 >with second-hand information, so you must be patient,
provide the right
 >information using consistent terminology, and be very
observant.
 >
 >Please give:
 >- the filename and path of the "ISAPI Filter" you are
referring to.
 >- where this "configuration change" is happening -- is it
in the ISAPI
 >Filters tab (if so, is it at the website level or global
level), the
 >Application Mappings tab (if so, for what extensions, and
what is the
 >checked-status of the Script Engine and "Check if file
exists" options), or
 >somewhere else (describe the tab).
 >- what event log entries are associated with
the "problem" you are observing
 >- what do you mean by "executed in DOS mode" -- default
IIS configuration
 >does not show execution on the screen at all, so it seems
like you have some
 >other system modifications in play that you must describe.
 >- are requests actually failing, or are you just
concerned about something
 >executing in a "DOS mode".
 >
 >--
 >//David
 >IIS
 >This posting is provided "AS IS" with no warranties, and
confers no rights.
 >//
 >"Jay" <jbrister.RemoveThis@redfig.com> wrote in message
 >news:4fe101c3e4c6$a911cf00$a401280a@phx.gbl...
 >Hi,
 >
 >please can someone shed some light on a problem I am
 >having with IIS 4.0 on NT 4? I have an ISAPI Filter which
 >was working correctly. Recently some changes were made to
 >the IIS configuration which has resulted in the DLL being
 >loaded and executed in DOS mode.
 >
 >Does anyone know what I need to do to stop this from
 >happening? The DLL will not execute in DOS mode, and I
 >cannot find out why IIS is trying to load it in this way.
 >
 >Many thanks,
 >
 >J
 >
 >
 >.
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: ISAPI Filters