It is an error to use a section registered as allowDefinition=’MachineToApplication’ beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.

Today a friend of mine started getting this error while he tried to deploy his solution to a server. This only started when ‘Precompiling during publishing’ option is selected.

“Error 20 It is an error to use a section registered as allowDefinition=’MachineToApplication’ beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.”

After having a look, I identified this was caused by a temporary copy of a Web.Config file. Earlier developer created a copy of the Web.Config and placed it inside a folder named Backup within the solution. This backup config file had authentication tag (<authentication>), which is a tag that can be only used in global Web.Config file or the Web.Config file in applications root. Due to the presence of authentication tag, compiler started complaining that there is a virtual directory not configured as a application in IIS.

The solution for my friend’s issue was to simply exclude the copy of the Web.Config file from project by right clicking the file. Then the project started deploying happily.

Advertisement

HTTP Error 404.13 – Not Found – The request filtering module is configured to deny a request that exceeds the request content length.

I recently got this error in one of my applications. When troubleshooting, I found my application is configured to have the default value of 30000000 Bytes for the content length, which was not sufficient for me in some of the file uploading functionalities.

Simply adding / increasing the number in the configuration file corrected this error.

Request Content Length in Bytes.

Default Value – 30000000 Bytes (~28MB)

Maximum Value – 4284229877 Bytes (3.99GB)

1. <system.webServer>
2.   <security>
3.     <requestFiltering>
4.       <requestLimits maxAllowedContentLength=“100000000“></requestLimits>
5.     </requestFiltering>
6.   </security>
7.   …
8. </system.webServer>

 

To obtain more information read this article.

HTTP Error 500.19 – Internal Server Error

Recently in one of my machines I got the above HTTP error when running an application hosted on IIS 7. The detailed error was as below.

“This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false".”

After doing some troubleshooting I was managed to get this error fixed by reinstalling ASP.Net by running the aspnet_regiis –ir command.

For more information on running the command please refer to my old article Unable to start debugging on the web server.

Changing the IIS Connection Timeout

For many reasons you might need to increase the IIS connection timeout.

The many reasons can be many time consuming processes, large transactions, slower connections, etc.

As a result if your application is timing out, one thing you can do is to increase the connection timeout.

• To change the timeout value you need to open Internet Information Services (IIS) manager. Either type InetMgr in the Run window or click on Start -> All Programs -> Administrative Tools -> Internet Information Services (IIS) Manager.
• In the IIS Manager expand the main node and right click on the Web Sites and click on Properties.
• In the Web Sites Properties page give the appropriate value in the Connection timeout field under Connections section in Web Site tab and press Ok.
• Now to make the setting take effect restart the IIS by either typing IISReset in the Run window or right clicking on the machine name and going to All Tasks and clicking on Restart IIS… in the IIS Manager.