Re: IIS-5.1 ISAPI dll - "The page cannot be displayed" after XP - SP2 install

From: David Wang [Msft] (someone_at_online.microsoft.com)
Date: 09/08/04

  • Next message: Joe: "Re: IIS cert denied" 
    Date: Wed, 8 Sep 2004 14:33:54 -0700

    The vendor is still responsible for supporting their product.

    I see no indication that IS2WCGI.DLL is a Microsoft supported product -- it
    looks like sample code to me, source code and all. Thus, this is NOT like
    redistributing msvcrt.dll, which is supported code. Thus, the vendor is
    solely responsible for it, especially since they have the source code to the
    sample.

    If this ISAPI merely invokes another CGI EXE from the Vendor to do the work,
    then clearly the vendor will have to investigate that interaction. My gut
    feeling remains -- there is probably some Security-related issue in here,
    and the Vendor will have to figure out what there support policy is, what
    the actual issue is, and what they have to do to fix it.

    Bottom line -- All you need to ask the vendor is:
    "Do you support product X on XPSP2".

    If they do not support XPSP2, then your choices are to either move to
    another product, or ask when they will support it. 

    -- 
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Phil Borod" <miamipab1@(nospam)aol.com> wrote in message
news:udqwPdblEHA.2380@TK2MSFTNGP14.phx.gbl...
David,
    Received a response from the vendor.  The DLL we are using has been
renamed, but it is actually IS2WCGI.DLL.  The vendor believes that this is a
Microsoft written DLL. There is a writeup of it on the Microsoft Developer's
Network at http://www.microsoft.com/mind/0396/ISAPI/ISAPI.asp about 2/3 of
the way down the page.
   Hope this helps.
Phil Borod - TICI
"Phil Borod" <miamipab1@(nospam)aol.com> wrote in message
news:OjGhCaGlEHA.3392@TK2MSFTNGP15.phx.gbl...
> David,
>    Good advice.  Am going that way.  Thanks much.
> Phil
> "David Wang [Msft]" <someone@online.microsoft.com> wrote in message
> news:ennIhMGlEHA.596@TK2MSFTNGP11.phx.gbl...
>>I think you should contact support for your purchased software.
>>
>> Random ISAPI configuration is unlikely to help.  You really need
>> expertise
>> with what the software requires.
>>
>> -- 
>> //David
>> IIS
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> //
>> "Phil Borod" <miamipab1@(nospam)aol.com> wrote in message
>> news:uSuIrFFlEHA.3104@TK2MSFTNGP14.phx.gbl...
>> David,
>>   Your gut feeling coincides with mine.  This dll was written before the
>> concept of ISAPI Extensions.  It functioned as an ISAPI filter.  I have
>> not
>> dealt with or configured ISAPI extensions at all.  Should I give that a
>> try?
>> Phil
>>
>> "David Wang [Msft]" <someone@online.microsoft.com> wrote in message
>> news:ejtsCwElEHA.2868@TK2MSFTNGP11.phx.gbl...
>>>I think you need to contact the support for your purchased software.
>>>
>>> When you clicked submit:
>>> 1. the browser's URL bar showed the URL
>>> http://localhost/carib/cgi-win/clogin.dll -- showing the browser parsed
>>> the
>>> HTML and made the request
>>> 2. the Web server log shows requests for /carib/cgi-win/clogin.dll -- 
>>> showing IIS successfully received the request, passed execution into the
>>> ISAPI Extension DLL itself, and received a response from it that was
>>> sent
>>> back to the client. The content of the response depends completely on
>>> the
>>> ISAPI
>>> 3. The response shown in the browser indicate that either something
>>> between
>>> IIS and the browser closed the connection, or the ISAPI DLL itself
>>> closed
>>> the connection.
>>>
>>> So, I have to ask you:
>>> 1. what else is running on this machine, and whether you have any ISAPI
>>> Filters loaded and configured properly
>>> 2. how can you verify that your ISAPI Extension is correctly configured?
>>>
>>> My gut feeling (unsubstantiated) is that your ISAPI Extension relies on
>>> some
>>> COM component with greater privileges than it now has with XPSP2's
>>> security
>>> tightening, and on COM component failure, the ISAPI Extension aborted
>>> the
>>> connection.  You must contact your software's support and verify that it
>>> should function on XPSP2, and if so, what its configuration should be.
>>>
>>> FYI: Technical point -- the ISAPI DLL clogin.dll is at least an ISAPI
>>> Extension.
>>>
>>> -- 
>>> //David
>>> IIS
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>> //
>>> "Phil Borod" <miamipab1@(nospam)aol.com> wrote in message
>>> news:ePH1whAlEHA.896@TK2MSFTNGP12.phx.gbl...
>>> David,
>>>   The deeper I look, the more interesting & perplexing.  Here's some
>>> more
>>> info :
>>>   System event log shows W3SVC error with user "N/A", yet
>>>   the http: web server logs look normal:
>>> #Software: Microsoft Internet Information Services 5.1
>>> #Version: 1.0
>>> #Date: 2004-09-06 09:11:26
>>> #Fields: time c-ip cs-method cs-uri-stem sc-status
>>> 09:11:26 127.0.0.1 GET /carib/htdocs/Catalog.htm 200
>>> 09:11:26 127.0.0.1 GET /carib/htdocs/CSlogo.gif 200
>>> 09:11:26 127.0.0.1 GET /carib/htdocs/CSlogo.jpg 200
>>> 09:11:26 127.0.0.1 GET /carib/htdocs/qs_chlk.jpg 200
>>> 09:11:36 127.0.0.1 POST /carib/CGI-WIN/clogin.dll 200
>>> 09:11:37 127.0.0.1 POST /carib/CGI-WIN/clogin.dll 200
>>> 09:11:39 127.0.0.1 POST /carib/CGI-WIN/clogin.dll 200
>>>
>>> Thanks in advance for your input.
>>> Phil
>>>
>>> "David Wang [Msft]" <someone@online.microsoft.com> wrote in message
>>> news:ui%23rSi6kEHA.3496@TK2MSFTNGP12.phx.gbl...
>>>> Please turn off the "Show Friendly HTTP Errors" option of IE and post
>>>> the
>>>> actual error response you get.
>>>>
>>>> XPSP2 installs and enables a firewall which blocks all unsolicited
>>>> incoming
>>>> traffic for security purposes. This will block IIS from functioning.
>>>> The
>>>> secure way to re-enable IIS is to leave the firewall running and set up
>>>> a
>>>> port exception for IIS.  The following command opens up port 80 on the
>>>> firewall to allow IIS to function -- we use this command all the time
>>>> during
>>>> our testing of IIS on XPSP2.
>>>>
>>>> NETSH firewall set portopening mode=ENABLE profile=ALL scope=ALL
>>>> protocol=TCP port=80 name="HTTP"
>>>>
>>>> -- 
>>>> //David
>>>> IIS
>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>> rights.
>>>> //
>>>> "Phil Borod" <miamipab1@(nospam)aol.com> wrote in message
>>>> news:eTO1l93kEHA.3428@TK2MSFTNGP11.phx.gbl...
>>>> IIS-5.1 ISAPI dll - "The page cannot be displayed" after XP - SP2
>>>> install
>>>>
>>>> On my XP-Pro localhost, this worked fine before SP2 install:
>>>>
>>>>  Clicking the Submit button on a localhost web page would execute the
>>>> clogin.dll.
>>>>
>>>> <form name="CSLogin" method="POST" action="../CGI-WIN/clogin.dll">
>>>>
>>>> Installed SP2, and try the same button and the same localhost web page
>>>> and
>>>> receives:
>>>> "The page cannot be displayed"
>>>> The page you are looking for is currently unavailable.
>>>>
>>>> I thought I found a very similar issue in
>>>> MS KB # 842005 - How to enable the ISAPI component on SQLXML on Windows
>>>> XP
>>>> Service Pack 2.
>>>> Since they addressed the tweaking of the SP2 firewall, I disabled it
>>>> completely to see if that would work.
>>>> No luck.
>>>>
>>>> Remember that the IIS-5.1 web permissions were working before the SP2
>>>> install.  I didn't write the dll; it is part of a purchased software
>>>> package
>>>> and the vendor is not sure what the problem is either.
>>>>
>>>> Any ideas appreciated.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
  • Next message: Joe: "Re: IIS cert denied"