Server Error in '/' Application. The problem

Last night, after a night of publishing this issue, we found that many solutions on the Internet were not reliable:

Server Error in '/' Application.

Runtime Error
Description:an Application error occurred on the server. The current custom error settings-application prevent the details of the application error from being viewed Remo Tely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details:to enable the details of this specific error message to being viewable on remote machines, please create a <custo Merrors> tag within a "Web. config" configuration file located in the root directory of the current Web application. This <customErrors> tag should then has its ' mode ' attribute set to "Off".


<!--Web. config Configuration File--

<configuration>
<system.web>
<customerrors mode= "Off"/>
</system.web>
</configuration>


Notes:the Current error page seeing can is replaced by a custom error page by modifying the "defaultredirect" att Ribute of the application ' s <customErrors> configuration tag to point to a custom error page URL.


<!--Web. config Configuration File--

<configuration>
<system.web>
<customerrors mode= "RemoteOnly" defaultredirect= "mycustompage.htm"/>
</system.web>
</configuration>

Translate the results:

Run-time error
DescriptionAn application error occurred on the server. The current custom error settings for this application prohibit remote viewing of application error details (for security reasons).   However, it can be viewed by a browser running on the local server computer.

More information: To enable others to view the details of this specific error message on a remote computer, create a <customErrors> tag in the "Web. config" configuration file located at the root of the current WEB application. The "mode" property of this <customErrors> tag should then be set to "Off".


<!--the Web. config configuration file--

<configuration>
<system.web>
<customerrors mode= "Off"/>
</system.web>
</configuration>


Note: You can replace the current error page you see with a custom error page by modifying the "defaultredirect" property of the application's <customErrors> configuration tag to point to the URL of the custom error page.


<!--the Web. config configuration file--

<configuration>
<system.web>
<customerrors mode= "RemoteOnly" defaultredirect= "mycustompage.htm"/>
</system.web>
</configuration>

It is clear in the description that an application error has occurred on the server. The current custom error settings for this application prohibit remote viewing of application error details (for security reasons). However, it can be viewed by a browser running on the local server computer.

Is the program has an exception, in security reasons no output exception of the specific content, need to be viewed on the server, according to do.

The solution is to go directly to the server, open the program on the server, you can see the contents of the exception.