Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

Proget in IIS fails



  • On a vanilla install of Proget, where it should be hosted in IIS 7.5
    the site fails immediately with the following error:

    Handler "Wildcard64" has a bad module "IsapiModule" in its module list

    Which relates to the following entry in the config:

    <handlers>
          <add name="Wildcard32" path="*" verb="*" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="None" preCondition="classicMode,runtimeVersionv4.0,bitness32" />
          <add name="Wildcard64" path="*" verb="*" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="None" preCondition="classicMode,runtimeVersionv4.0,bitness64" />
        </handlers>
    

    I have confirmed that the dll's defined in the handlers section does exist.
    How can this issue be solved?

    Product: ProGet
    Version: 2.2.13



  • It sounds like there is an ISAPI restriction that's preventing this from loading; perhaps the easiest is to change the app pool to "Classic" mode.



  • The App pool is actually set to Classic mode, so that does, unfortunately, not have any influence on the issue.



  • Tod's answer gave me something to look for.

    The IIS 7.5 did not have ISAPI enabled so after doing that the proget site worked as a charm.
    Definitely something that is missing in the documentation!

    For further reference see below:

    To enable ISAPI in the IIS look here: http://www.iis.net/configreference/system.webserver/security/isapicgirestriction
    at the part

    Setup

    The <isapiCgiRestriction> collection is available only after you install the CGI or ISAPI Extensions modules on your IIS 7 server. You cannot install it independent of those features.

    WINDOWS SERVER 2008 OR WINDOWS SERVER 2008 R2

    On the taskbar, click Start, point to Administrative Tools, and then click Server Manager.
    In the Server Manager hierarchy pane, expand Roles, and then click Web Server (IIS).
    In the Web Server (IIS) pane, scroll to the Role Services section, and then click Add Role Services.
    On the Select Role Services page of the Add Role Services Wizard, select CGI or ISAPI Extensions.

    If the Add role services dialog appears, click Add Required Role Services. (This page appears only if you have not already installed any prerequisite role services on your server.)
    On the Select Role Services page, click Next.
    On the Confirm Installation Selections page, click Install.
    On the Results page, click Close.

    After doing that i restarted and did not have to any further setup. Loading the site just worked.

    Inedo should make it much clearer in the documentation that this must be installed in the IIS for proget to work. Just setting the App Pool to Classic is not enough.

    Thomas



Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation