Server Error in '/' Application. ASP.NET
I developed a website using ASP.Net 3.5 and C#. It is working good with Visual Stdio 2010. I uploaded my website to my domain under the public folder.
First time I lunched my website for testing (http://wecoders.com/Habib_cuizine/Gallery.aspx) I would revive (Server Error in ‘/’ Application.)
Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (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 be viewable on remote machines, please create a tag within a «web.config» configuration file located in the root directory of the current web application. This tag should then have its «mode» attribute set to «Off».
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the «defaultRedirect» attribute of the application’s configuration tag to point to a custom error page URL.
To fix this error I added to the webConfig file inside tag:
After that when I lunch the website I would receive a new error as listed bellow:
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.
Line 35: ASP.NET to identify an incoming user.
Line 39: The section enables configuration
Source File: \10.0.40.35\wecoders.com\public\habib_cuizine\web.config Line: 37
Please advice how to fix this error and how configure my website which developed using Visual Stdio 2010 to be published in the internet.
Не могу открыть сайт появляется Server Error in ‘/’ Application. что делать?
Server Error in ‘/’ Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (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 be viewable on remote machines, please create a <customerrors> tag within a «web.config» configuration file located in the root directory of the current web application. This <customerrors> tag should then have its «mode» attribute set to «Off».
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the «defaultRedirect» attribute of the application’s <customerrors> configuration tag to point to a custom error page URL.
Посоветуйте умные люди че сделать, чтоб зайти на сайт, если это возможно, очень надо.
Server Error in ‘/’ Application.
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (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 be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application’s <customErrors> configuration tag to point to a custom error page URL.
An admin and a regular user can attempt to access SharePoint on the same workstation, and, still, only the admin can view it.
I have read through forums regarding this message and they all say that it is an IIS issue. We installed IIS on 1 server this morning, which is when people started to report the issue. I stopped IIS on the server, but the issue remains. But, since we aren’t hosting SharePoint ourselves and accessing it through a 365 subscription, I don’t think this should matter anyway.