Server Error in ‘/’ Application.
——————————————————————————–

Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: 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.

Source Error:
Line 35:         –>
Line 36:     <globalization requestEncoding=”GB2312″ responseEncoding=”GB2312″ fileEncoding=”GB2312″ culture=”zh-CN” uiCulture=”zh-CN”/>
Line 37:     <sessionState timeout=”30″ cookieless=”false” stateConnectionString=”tcpip=127.0.0.1:42424″ mode=”InProc” >
Line 38:     </sessionState>
Line 39:     <compilation debug=”true”>
 

Source File: D:\client\website\web.config    Line: 37

Show Additional Configuration Errors:
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. (D:\client\website\web.config line 61)
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. (D:\client\website\web.config line 91)
                     
 
——————————————————————————–
Version Information: Microsoft .NET Framework Version:2.0.50727.3623; ASP.NET Version:2.0.50727.3618

检查你的网站根目录路径是否配置正确！

网络资料：

This error can be caused by a virtual directory not being configured as an application in IIS

这个报错一般是由于两种原因引起的。

1 是由于您没有为目录创建一个Application

如果你用的是空间商提供的虚拟空间，出现这样的问题很可能是你的空间配置问题，一般虚拟空间都会提供给你一个增加虚拟文件夹的功能。

2 是由于您在站点的子目录中的web.config中加入了只能在根目录中配置的信息。如Session或是权限。

具体的解决方法如下：

You may get this error when trying to browse an asp.net application.

The debug information shows that “This error can be caused by a virtual directory not being configured as an application in IIS.”

However, this error occurs primarily out of 2 scenarios.

1. When you create an new web application using visual studio.net, it automatically creates the virtual directory and configures it as an application. However, if you manually create the virtual directory and it is not configured as an application, then you will not be able to browse the application and may get the above error. The debug information you get as mentioned above, is applicable to this scenario.

To resolve it, Right Click on the virtual directory – select properties and then click on
“Create” next to the “Application” Label and the textbox. It will automatically create the “application” using the virtual directory’s name. Now the application can be accessed.

2. When you have sub-directories in your application, you can have web.config file for the sub-directory. However, there are certain properties which cannot be set in the web.config of the sub-directory such as authentication, session state (you may see that the error message shows the line number where the authentication or sessionstate is declared in the web.config of the sub-directory). The reason is, these settings cannot be overridden at the sub-directory level unless the sub-directory is also configured as an application (as mentioned in the above point).

Mostly we have the practice of adding web.config in the sub-directory if we want to protect access to the sub-directory files (say, the directory is admin and we wish to protect the admin pages from unathorized users).

But actually, this can be achieved in the web.config at the application’s root level itself, by specifing the location path tags and authorization, as follows:-

<location path=”Admin”>

      <system.web>

        <authorization>

<allow roles=”administrators” />

<deny users=”*” />

        </authorization>

      </system.web>

</location>

However, if you wish to have a web.config at the sub-directory level and protect the sub-directory, you can just specify the Authorization mode as follows:-

<configuration>
<system.web>
<authorization>
       <allow roles=”administrators” />
       <deny users=”*” />
</authorization>
</system.web>
</configuration>