Iis – Shared hosting on IIS7. Not able to access resources with ‘StaticFileModule’ handlers

iisiis-7

I have directories for images and styles, with a Web.config file (using Orchard). In that Web.config there is a line causing a problem on my shared hosting (running fine in WebMatrix):

  <system.webServer>
    <handlers accessPolicy="Script,Read">
      <!--
      iis7 - for any request to a file exists on disk, return it via native http module.
      accessPolicy 'Script' is to allow for a managed 404 page.
      -->
      <add name="StaticFile" path="*" verb="*" modules="StaticFileModule" preCondition="integratedMode" resourceType="File" requireAccess="Read" />
    </handlers>
  </system.webServer>

When I try to access any files from that directory I get a 500 page:

500 – Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.

When I delete the line

<add name="StaticFile" path="*" verb="*" modules="StaticFileModule" preCondition="integratedMode" resourceType="File" requireAccess="Read" />

it displays the resources.

How can I fix this problem without altering the Web.config file located in each directory containing files which are intended to be accessed directly?

Best Answer

I do not think you can (on Shared hosting, I mean).

The error clearly says: "Cannot add duplicate collection entry of type 'add' with unique key attribute 'name' set to 'StaticFile". This means that there is already an entry with name="StaticFile" somewhere above in config hierarchy (in another web.config in a parent folder .. or, most likely, global web server config.

To solve it, you have to remove existing config line first. You have to add <remove name="StaticFile" /> line into your <handlers> section before adding your own handler, for example:

<system.webServer>
    <handlers accessPolicy="Script,Read">
        <remove name="StaticFile" />
        <!--
        iis7 - for any request to a file exists on disk, return it via native http module.
        accessPolicy 'Script' is to allow for a managed 404 page.
        -->
        <add name="StaticFile" path="*" verb="*" modules="StaticFileModule" preCondition="integratedMode" resourceType="File" requireAccess="Read"/>
    </handlers>
</system.webServer>

If you would have full control over your server (which you do not, since you are on shared hosting) you could remove StaticFile handler from global IIS config ... but is it wise?? Adding the <remove...> line is a correct approach for both scenarios.

Related Solutions

IIS7 – Lock Violation error, HTTP handlers, modules, and the element

That's by design. The <modules> section of system.webServer essentially defines IIS itself. If you <clear />, you won't be left with anything. In applicationHost.config, you should have something like this:

        <modules>
            <add name="HttpCacheModule" lockItem="true" />
            <add name="DynamicCompressionModule" lockItem="true" />
            <add name="StaticCompressionModule" lockItem="true" />
            <add name="DefaultDocumentModule" lockItem="true" />
            <add name="DirectoryListingModule" lockItem="true" />
            <add name="IsapiFilterModule" lockItem="true" />
            <add name="ProtocolSupportModule" lockItem="true" />
            <add name="HttpRedirectionModule" lockItem="true" />
            <add name="StaticFileModule" lockItem="true" />
            ...

Notice the lockItem properties. Because there are 1 or more lock items, will throw a lock violation.

So, you either need to specifically remove just the items that you don't want from web.config, or if you really need to clear them all and add back your own, then in applicationHost.config remove the lockItem="true" on each of those elements, and make sure to add enough of them back so that your web server will actually work.

Edit

(Appended further information from Daniel, per his request. (Scott))

Here is what I did based on what Scott said:

Opened applicationHost.config in %windir%\system32\inetsrv\config. Note that in 64 bit Windows Server 2008, you'll need to edit the file with a 64 bit editor (the native Notepad will do, but Notepad++ won't be able to find the file). See here for more information about this.

In the <system.webServer> element, change the lockItem attribute on all modules to false.

In my web application's web.config file, was then able to do the following:

<system.webServer>
   <modules>
      <clear />
   </modules>
</system.webServer>

Of course, as Scott points out, this means there's no web server left, so here is the minimum set of modules I needed to get my stuff running again (YMMV):

<add name="HttpRedirectionModule" lockItem="false" />

<add name="StaticFileModule" lockItem="false" />

<add name="CustomLoggingModule" lockItem="false" />

<add name="CustomErrorModule" lockItem="false" />

<add name="IsapiModule" lockItem="false" />

<add name="AnonymousAuthenticationModule" lockItem="false" />

Also, for anyone interested, here's the backstory as to why I'm doing this.

IIS Permissions – Resolving Permissions Issue with Virtual Directory to UNC Path

The fact that it's an ASP.net app is probably exactly what the issue is here. Your application pool identity has to have rights (not necessarily the IIS identity; by default, the app pool identity is the local Network Service account.) You also probably need to run caspol.exe on your IIS machine.

http://msdn.microsoft.com/en-us/library/cb6t8dtz%28v=vs.80%29.aspx

http://learn.iis.net/page.aspx/50/aspnet-20-35-shared-hosting-configuration/

%windir%\Microsoft.NET\Framework\v2.0.50727\caspol -m -ag 1.  -url "file://\\remotefileserver\content$\*" FullTrust

Best Answer

Related Solutions

IIS7 – Lock Violation error, HTTP handlers, modules, and the element

IIS Permissions – Resolving Permissions Issue with Virtual Directory to UNC Path

Related Topic