Re: Cant't download "exe" file because of IIS version

From: Peter McLaren (PeterMcLaren_at_discussions.microsoft.com)
Date: 11/15/04

  • Next message: WenJun Zhang[msft]: "Re: IIS on Workstation limitations" 
    Date: Mon, 15 Nov 2004 00:13:03 -0800

    This solution may not be "correct", but it is the ONLY solution that worked.
    I have verified every setting in IIS6 until I am blue in the face and no
    matter what I did, under no circumstances whatsoever, could I download this
    executable file from my IIS6 server. Perhaps it was a function of running
    Project Server on this box and running a tomcat application as well, but
    regardless, those applications are mission critical while this downloading an
    executable was not.

    Fortunately, it is an intranet site and the task was to download a
    relatively small exe file. Based on what I have learned after installing this
    executable, the appropriate solution for my company is to have me create an
    msi based on the installation of this application and push it out using AD,
    so this particular problem is no longer an issue.

    You mention an official fix. May I enquire as to what it is? I have searched
    the registry and looked at all levels of Web directories in IIS6 to verify
    that executables were NOT mapped to any application for the MIME type. (Right
    now ASP.Net is handling executables for this directory)

    "David Wang [Msft]" wrote:

    > Wait. Your resolution is not correct. It may "work" but it's not right and
    > will fail under load since ASP.Net static file handler is not as robust as
    > IIS's.
    >
    > What you did was assign ASP.Net to handle the .exe extension, and ASP.Net
    > will send the resource as-is since it doesn't understand .exe files. This
    > means that ASP.Net settings for static files will apply to the response,
    > which has its own configuration in the various machine.config/web.config
    > files applicable.
    >
    > This is one way to "work", but it is a poor choice because ASP.Net static
    > file handler is known to not perform well under load nor for large files
    > (i.e. large Office documents can cause it to choke) -- so you really do NOT
    > want to do this. The official "fix" for this issue is to NOT use ASP.Net
    > for static files, so if you run into problems, you will have to do what I'm
    > telling you anyway -- so let's just avoid the run-around and do it correctly
    > the first time.
    >
    >
    > You want to make sure that .EXE is NOT scriptmapped to anything, so that the
    > IIS6 static file handler sends the content in accordance to the MIME Type
    > settings you make in IIS.
    >
    > --
    > //David
    > IIS
    > This posting is provided "AS IS" with no warranties, and confers no rights.
    > //
    > "Peter McLaren" <PeterMcLaren@discussions.microsoft.com> wrote in message
    > news:AFBD908E-8C32-4F3F-B159-862960497CE6@microsoft.com...
    > I am absolutely 100% positive that permissions was set to Scritps only.
    > The final way that this issue was resolved was by following the instructions
    > below:
    > In IIS Manager, right click the virtual folder and select
    > "Properties/Directory". Click "Configuration" button, and then add an
    > application extension: executable:
    > C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll extension
    > ..exe.
    > Restart IIS
    >
    > "Yogita Manghnani [MSFT]" wrote:
    >
    > > Hello,
    > > Are you sure that the setting Executable permissions for that site in IIS
    > > is set to Scripts only and not Scripts and Executables? I'm not sure how
    > > Firefox works, but if you specify Executable permissions to Scripts only
    > > then IE should prompt you to open/save the exe on the client end.
    > > http://support.microsoft.com/default.aspx?scid=kb;en-us;313075
    > >
    > > Good luck,
    > > Yogita Manghnani
    > > Microsoft Developer Support
    > > Internet Information Server
    > >
    > > *********************************************************************
    > > >>Please do not send email directly to this alias. This is an online
    > > account name for newsgroup participation only.<<
    > >
    > > This posting is provided "AS IS" with no warranties, and confers no
    > rights.
    > > You assume all risk for your use.
    > >
    > > © 2003 Microsoft Corporation. All rights reserved.
    > > *********************************************************************
    > >
    > >
    >
    >
    >

  • Next message: WenJun Zhang[msft]: "Re: IIS on Workstation limitations"