« Previous Next »

Thread: Can't get around ISAPI filter error

Last post 01-07-2009 2:15 PM by zdenek. 1 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (2 items)

Sort Posts:

  • 11-13-2008, 4:27 PM

    • e1ny
    • Top 50 Contributor
    • Joined on 12-10-2007, 9:50 PM
    • Posts 188

    Can't get around ISAPI filter error

    Hi All: I'm still trying to figure out what's causing

    Could not load all ISAPI filters for site 'mysite'. Therefore site startup aborted.

    This is on a server with the FastCGI processor running with PHP 5.2.5 installed. The main site on the server runs fine with PHP, so I'm not sure if that's where the problem lies, but it's the only ISAPI-like thing on the server.

    If I create a new website from scratch, in a blank subdirectory in InetPub, and browse the site, I will see "403 Access Forbidden". If I drag a simple PHP page into the website, with:

    <?php

    echo 'working!';

    ?>

    and try to browse the page, I still get a "403 - Forbidden: Access is denied." error. If I turn on FREQ, I immediately get a "500" error, and the error message in the Application log. Turning on FREQ creates a web.config file with:

    <?xml version="1.0" encoding="UTF-8"?>
    <configuration>
        <system.webServer>
            <tracing>
                <traceFailedRequests>
                    <add path="*">
                        <traceAreas>
                            <add provider="ASP" verbosity="Verbose" />
                            <add provider="ASPNET" areas="Infrastructure,Module,Page,AppServices" verbosity="Verbose" />
                            <add provider="ISAPI Extension" verbosity="Verbose" />
                            <add provider="WWW Server" areas="Authentication,Security,Filter,StaticFile,CGI,Compression,Cache,RequestNotifications,Module" verbosity="Verbose" />
                        </traceAreas>
                        <failureDefinitions statusCodes="400-999" />
                    </add>
                </traceFailedRequests>
            </tracing>
        </system.webServer>
    </configuration>

    If I turn off FREQ and delete the web.config file, I'm back to "403" errors.

    If I create a simple HTM page in that directory and attempt to browse it, I get:

    "401 - Unauthorized: Access is denied due to invalid credentials" 

    If I look at the permissions on this folder, neither NETWORK SERVICE nor IIS_IUSRS have explicit permissions on the directory. If I add them...things seem to start working!

    Question is...How can this be so FUBAR?  Shouldn't creating a new website in IIS set the permissions on the directory properly? I feel like I'm back in the NT4 option pack days :(

  • 01-07-2009, 2:15 PM In reply to

    • zdenek
    • Top 200 Contributor
    • Joined on 09-08-2008, 6:25 PM
    • miami
    • Posts 31

    Re: Can't get around ISAPI filter error

    how about adding something like:

    <?xml version="1.0" encoding="UTF-8"?>
    <configuration>
      <system.webServer>
        <handlers accessPolicy="Read, Script" />
      </system.webServer>
    </configuration>

    Chances are you do not have permission set to access files and script them. You may need to also include possibly Execute for the isapi to work
Page 1 of 1 (2 items)
Microsoft Communities